Crossplane v2.5 Release Solidifies Control Plane Capabilities and Marks v1.20 EOL

Crossplane has announced the release of version 2.5, a quarterly update that continues to mature its capabilities as a framework for building cloud-native control planes. This release, arriving in November 2026, brings with it a host of refinements aimed at improving stability, usability, and operational insight. A key aspect of this announcement is the concurrent End-of-Life (EOL) for Crossplane v1.20, meaning users on that version will no longer receive support or maintenance. This development is crucial for platform engineers and DevOps teams who leverage Crossplane to manage their infrastructure through Kubernetes. The continuous evolution of Crossplane, particularly with its v2 series, emphasizes a shift towards more robust and production-ready control planes. The deprecation of older versions underscores the project's commitment to advancing its core APIs, such as real-time compositions and managed resource activation policies, to enhance performance and reliability across diverse environments. This aligns with the broader trend in cloud-native development where infrastructure is increasingly treated as code and managed declaratively. Crossplane, having achieved CNCF Graduation in November 2025, has firmly established itself as a mature and battle-tested project alongside Kubernetes, Prometheus, and Helm. Its paradigm of modeling cloud resources as native Kubernetes objects, rather than external state files, offers continuous drift detection and remediation, a significant advantage over traditional Infrastructure as Code (IaC) tools like Terraform. The project's growth, with over 3,000 contributors from 450 companies, demonstrates its widespread adoption and the community's investment in its future. For practitioners, the immediate implication is the need to plan upgrades if they are still operating on Crossplane v1.20. The v2 series, starting with v2.0 in August 2025, introduced significant architectural changes, including namespaced composite resources and enhanced composition functions, making Crossplane more suitable for building application-centric control planes. While v2 offers backward compatibility for many v1 features, migrating to the newer, namespaced resource model is recommended to fully leverage the benefits of improved multi-tenancy, simplified RBAC, and a cleaner resource model. Teams should review the release notes for v2.5 and the broader v2 series to understand the new features and necessary upgrade paths, ensuring their internal developer platforms remain robust, secure, and efficient.