Crossplane v2.5 Release Bolsters Stability and Extends EOL for v1.20 Users

The Crossplane project has announced the release of version 2.5, a quarterly update that brings further enhancements to its Kubernetes-native control plane capabilities. Concurrently, this release signals the end-of-life (EOL) for Crossplane v1.20, urging users to plan their migration to newer, supported versions. This development is significant for practitioners leveraging Crossplane to manage their cloud infrastructure. The consistent quarterly release cadence, with each release maintained for approximately nine months, emphasizes the project's commitment to continuous improvement and stability. For those still operating on v1.20, the EOL announcement means a cessation of support and maintenance, making an upgrade imperative to ensure continued security and access to bug fixes. The move to v2.x, which began with Crossplane v2.0 in August 2025, introduced substantial architectural changes, including namespaced resources and enhanced composition functions, making it a more mature and capable platform for building internal developer platforms. This aligns with the broader trend in cloud-native environments towards declarative infrastructure management and GitOps principles. Crossplane, by extending the Kubernetes API to orchestrate external resources, provides a unified control plane that treats infrastructure as code within the familiar Kubernetes ecosystem. This approach contrasts with traditional Infrastructure as Code (IaC) tools like Terraform by offering continuous reconciliation and a single source of truth within Kubernetes' etcd. The project's graduation to a CNCF project in November 2025 further solidified its position as a production-ready and widely adopted solution for platform engineering. In practice, this means that platform teams should immediately assess their current Crossplane versions. If still on v1.20, a migration strategy to at least v2.x should be a high priority. This upgrade will not only ensure ongoing support but also unlock advanced features like improved multi-tenancy through namespaced resources and more flexible composition functions. Furthermore, practitioners should actively engage with the Crossplane community and documentation to understand the nuances of the v2.x architecture and plan for potential breaking changes. The continuous evolution of Crossplane reinforces the need for platform teams to adopt agile practices for infrastructure management, regularly evaluating and integrating updates to maintain a secure, efficient, and scalable cloud environment.