Crossplane v2.5 Release Signals End-of-Life for v1.20, Urging Platform Teams to Modernize Control Planes

Crossplane has announced the release of v2.5, a significant milestone that also marks the end-of-life (EOL) for the v1.20 branch. This means that v1.20 will no longer receive official support or maintenance from the Crossplane project. This development is crucial for platform teams and DevOps engineers currently relying on Crossplane for their infrastructure management. The v2 series, particularly with its foundational changes introduced in v2.0, has shifted Crossplane towards a more application-centric and Kubernetes-native approach. Key enhancements include namespaced composite resources and managed resources, which enable finer-grained access control and multi-tenancy. The introduction of Composition Functions in v2.0 also moved beyond static YAML, allowing for more dynamic and programmable infrastructure definitions. This release aligns with the broader trend in cloud-native development towards platform engineering, where organizations strive to provide self-service infrastructure capabilities to developers through internal developer platforms (IDPs). Crossplane, by extending Kubernetes to manage external cloud resources, has become a pivotal component in this ecosystem. The v2 series further solidifies this role by offering more flexible and powerful abstractions, enabling platform teams to build custom APIs tailored to their organizational needs. In practice, this means that teams still on Crossplane v1.20 should immediately begin planning their migration to a v2.x release. While Crossplane v2 offers backward compatibility for existing v1 cluster-scoped resources, the long-term strategy should involve adopting the new namespaced resource model. Practitioners should leverage the `crossplane beta upgrade check` command available in the v1.20 CLI to identify any deprecated features in use before upgrading. The migration path should be incremental, upgrading one minor version at a time, starting from v1.20 to v2.0, then to subsequent v2.x versions. This transition will unlock improved security, better resource isolation, and access to advanced composition capabilities, ultimately leading to more robust and maintainable infrastructure platforms.