Crossplane 2026: Kubernetes-Native Infrastructure as Code as a Platform Engine

When platform teams talk about Internal Developer Platforms (IDPs) today, names like Backstage, Argo CD, and Kubernetes often come up. One project frequently remains in the background, even though it forms the crucial layer beneath them: Crossplane. The CNCF-graduated framework turns cloud infrastructure into Kubernetes resources – and in 2026, with a series of releases and the new Modelplane project, it has definitively established itself as a central platform engine.

From Control Plane Framework to Platform Engine

Crossplane was open-sourced by Upbound in 2018 and joined the CNCF in 2020. What began as a specialized tool for “control planes” is now a graduated CNCF project – on the same governance level as Kubernetes, Prometheus, and Helm. More than 3,000 contributors from over 450 organizations have contributed over 100 releases to date, with cumulative downloads exceeding 100 million. Productive users include Nike, SAP, IBM, Elastic, Autodesk, and the NASA Science Cloud.

The decisive paradigm shift: Crossplane does not model cloud resources as external state files (like Terraform or OpenTofu), but as native Kubernetes objects. An S3 bucket, a PostgreSQL database, or an IAM role becomes a YAML manifest that kubectl apply expects and that Argo CD or Flux synchronize via GitOps. Kubernetes etcd handles state management and locking – no separate state backend configuration, no manual terraform plan.

Crossplane v2: The Architectural Leap

Crossplane v2.0 was released in August 2025 – the biggest architectural change since the project’s inception. Three changes were particularly consequential:

Namespaced Resources: Managed Resources live in namespaces by default and thus inherit Kubernetes RBAC. Multi-tenancy becomes an inherent property, not an option configured later.

Composition Functions: Instead of static patch-and-transform templates, platform teams can now write Composition Functions in Go, Python, or CEL since v2.0. These functions compute the desired infrastructure state at runtime – with loops, conditions, and logic that pure YAML templates could never represent.

Every Kubernetes resource is composable: A single Composition can not only create cloud resources like RDS instances, but also create Deployments, Services, ConfigMaps, and monitoring rules in the same cluster at the same time. What previously required multiple tools and pipelines becomes a single declarative object.

Since then, Crossplane has continued to grow at a three-month cadence: v2.2 (March