What Crossplane is & the control-plane model
Kubernetes as a universal control plane.
Crossplane turns a Kubernetes cluster into a control plane for infrastructure. Instead of running a CLI that applies a plan and exits, you install Crossplane into a cluster, and it extends the Kubernetes API with new resource types for cloud things — an RDS database, an S3 bucket, a GCP network. You then create those with kubectl apply like any other Kubernetes object, and a controller continuously reconciles them against the real cloud, creating, updating, and healing them.
The shift is from imperative runs to a always-on control loop. Terraform or CloudFormation provision when you run them; Crossplane provisions and keeps provisioning, because the same reconciliation engine that makes Kubernetes self-heal pods now heals your cloud infrastructure. Delete a bucket out from under it and Crossplane recreates it, exactly as Kubernetes recreates a deleted pod — the declared spec is enforced forever, not just at apply time.
Why teams reach for it
Two big draws. First, it unifies app and infra under one API and one toolchain — the same kubectl, RBAC, GitOps, and admission control that governs workloads now governs databases and networks. Second, it is a platform-building tool: a platform team can define its own high-level APIs (a “PostgresInstance” that means something specific to your org) and let developers self-serve, which the later lessons build up to.