Crossplane v2.5 Release Solidifies Kubernetes as the Universal Control Plane, Ending v1.20 Support
The Crossplane project is set to release version 2.5 in November 2026, a pivotal update that will also mark the end-of-life (EOL) for the v1.20 branch. This release continues to build on the architectural changes introduced in Crossplane v2.0 (August 2025), which brought significant enhancements like namespaced resources, Composition Functions, and the ability to compose any Kubernetes resource.
This release is highly significant for platform engineers and DevOps practitioners. The EOL of v1.20 means that users still on that version must plan their migration to the v2 series to continue receiving support and updates. The v2 architecture, with its focus on Kubernetes-native principles, offers a more robust and flexible foundation for building internal developer platforms. The shift to namespaced resources by default inherently improves multi-tenancy and simplifies RBAC, while Composition Functions provide far greater power and flexibility than the static patch-and-transform templates of earlier versions.
This development fits squarely within the broader trend of platform engineering and the increasing adoption of Kubernetes as a universal control plane. Crossplane's core paradigm—treating cloud infrastructure as native Kubernetes objects—aligns perfectly with GitOps methodologies, allowing infrastructure to be managed with the same declarative principles and tooling as applications. This approach contrasts with traditional infrastructure-as-code tools like Terraform, which rely on external state files. The evolution of Crossplane, from a specialized control plane framework to a comprehensive platform engine, reflects the industry's demand for unified, API-driven infrastructure management.
In practice, this means organizations leveraging Crossplane should prioritize their upgrade path to the v2 series, ideally to v2.5 or later, to benefit from the latest features, security updates, and continued support. Practitioners should explore Composition Functions written in Go, Python, or CEL to build more dynamic and powerful infrastructure abstractions. The enhanced multi-tenancy capabilities in v2 can simplify the management of shared infrastructure across different teams or environments. Furthermore, the ability to compose any Kubernetes resource alongside cloud resources allows for a truly unified control plane, enabling platform teams to offer a single API for both application and infrastructure provisioning. This transition reinforces the strategic importance of Kubernetes as the central nervous system for modern cloud-native operations.
Read original source