Crossplane V2.4.1 Reaches CNCF Graduation and 100 Million Downloads

Crossplane has achieved a significant milestone in its development lifecycle by reaching full CNCF Graduated status. This designation, granted on October 28, 2025, places the project in the same governance tier as established infrastructure tools like Kubernetes, Prometheus, and Helm. The move signals that the project has met strict criteria for maturity, security, and community health, reducing the adoption risk for enterprise teams.

According to Upbound, the project’s primary maintainer, over 1,000 organizations now rely on Crossplane in production environments. Notable users include Nike, Autodesk, and NASA’s Science Cloud. The company reports that cumulative downloads have surpassed 100 million, indicating widespread integration into modern cloud-native stacks. For teams currently managing AWS, Azure, and GCP resources through separate Terraform state files, this milestone offers a compelling alternative to fragmented infrastructure management.

Continuous reconciliation replaces scheduled runs

The fundamental architectural difference between Crossplane and traditional tools like Terraform lies in how they handle state. Terraform and similar tools operate on a plan-and-apply model, executing changes only when triggered by a human or a scheduled job. In contrast, Crossplane behaves like a standard Kubernetes controller. It continuously monitors the live state of cloud resources and automatically corrects any drift from the declared state without requiring manual intervention.

This continuous reconciliation loop means that cloud resources appear in standard kubectl output alongside Deployments and Services. Platform teams can use this to build internal developer platforms where engineers submit simple claims, such as a request for a Postgres database. Crossplane then translates that claim into the necessary underlying cloud resources, eliminating the need for developers to interact directly with cloud consoles or write complex HCL code.

Version 2.4.1 enables complex composition logic

Released in August 2025, Crossplane v2 introduced a major expansion of its capabilities. It allows Compositions to assemble any Kubernetes object, not just Crossplane-managed cloud resources. This means a single claim can now provision a mix of application-layer objects, like ConfigMaps and Deployments, alongside infrastructure resources like RDS instances. This unification simplifies the abstraction layer for developers, allowing them to request a complete environment in one API call.

The power of this feature comes from Composition Functions, which are small programs capable of implementing conditionals, loops, and templating logic. These functions calculate the desired state dynamically, offering flexibility that static YAML files cannot provide. While the architecture is powerful, it requires a deeper understanding of Kubernetes controllers and provider packages. Teams must manage the additional complexity of provider versioning and composition logic to avoid configuration errors.

Adoption metrics show strong industry interest

Industry surveys suggest a growing appetite for this approach. A 2025 report by Firefly indicated that while Terraform retains a 62% current usage share, Crossplane is gaining traction. Another survey cited by DevOps.com found that 40% of respondents were already using Crossplane, with 60% of the remaining group planning to adopt it. These figures are directional rather than precise market shares, but they highlight a clear shift toward Kubernetes-native infrastructure management.

The tech-insider.org tutorial for v2.4.1 details a 13-step setup process, covering everything from initial cluster creation to locking down access with namespace-scoped RBAC. The guide emphasizes that all commands were verified against current provider package versions as of September 2026. This ensures that users are working with the latest stable releases rather than outdated snapshots, providing a reliable foundation for building production-grade multi-cloud platforms.