→ Back to Home
Crossplane

Crossplane v1.20 Reaches End-of-Life, Urging Migration to v2 for Enhanced Control Plane Capabilities

Crossplane v1.20 is officially reaching its end-of-life in November 2026, coinciding with the release of Crossplane v2.5. This marks a pivotal moment for organizations that have adopted Crossplane for their cloud-native control planes. The v1.x line will no longer receive support or maintenance from the Crossplane project, making an upgrade to v2 imperative for continued stability and security. This development is highly significant for platform engineers and DevOps teams. Crossplane v2 introduces substantial architectural changes, moving away from the monolithic provider model towards more granular provider functions. This allows for greater flexibility and reusability in defining and managing infrastructure. Furthermore, v2 enhances the ability to compose any Kubernetes resource, broadening the scope of what Crossplane can manage beyond just cloud infrastructure to include applications as first-class citizens. The shift also strongly aligns with GitOps principles, where the desired state of infrastructure is declared in Git and continuously reconciled by Crossplane, offering a more consistent and auditable approach to infrastructure as code. The move to Crossplane v2 fits within the broader trend of platform engineering and the increasing adoption of declarative, API-driven infrastructure. As organizations strive to build internal developer platforms that offer self-service capabilities, Crossplane's evolution provides a more powerful and flexible foundation. The ability to manage both infrastructure and applications through a unified Kubernetes API aligns with the goal of reducing operational overhead and empowering development teams. This also resonates with the growing need for API-first platforms to enable AI agents, as highlighted by Crossplane's own discussions on AI and API-first infrastructure. In practice, practitioners should prioritize planning their migration from v1.20 to v2. This involves understanding the removed features, such as native patch and transform composition and the ControllerConfig type, and adapting their existing configurations. The migration is designed to be gradual, with legacy providers and managed resources continuing to function in v2, but the long-term benefits are realized by fully embracing the new v2 features like namespaced XRs and composition functions. Teams should leverage the Crossplane CLI's `upgrade check` command to identify resources needing attention before the upgrade. The transition, while requiring effort, will ultimately lead to more robust, scalable, and maintainable cloud infrastructure platforms.
#crossplane#end-of-life#v2 upgrade#platform engineering#gitops#kubernetes
Read original source