→ Back to Home
Crossplane

Crossplane v2.5.0-rc.1 Introduces Function-Controlled Deletion for Enhanced Infrastructure Lifecycle Management

Crossplane has announced the release candidate v2.5.0-rc.1, introducing several key enhancements, most notably the alpha feature of function-controlled deletion. This new capability allows composition functions to dictate the deletion order and timing of an eXtended Resource (XR)'s composed resources. Additionally, this release enables referencing functions by OCI digest, enhancing security and immutability in function pipelines. This development is crucial for platform engineers and DevOps teams who manage complex infrastructure lifecycles. Previously, Crossplane primarily offered background deletion, which might not be sufficient for scenarios requiring specific resource teardown sequences or pre-deletion hooks. Function-controlled deletion directly addresses these operational challenges, providing a powerful mechanism to prevent data loss, manage inter-service dependencies during decommissioning, and ensure compliance with specific operational procedures. It empowers platform teams to build more resilient and intelligent self-service platforms. This enhancement aligns with the broader trend in cloud-native environments towards more programmable and declarative infrastructure. As organizations increasingly adopt platform engineering principles, the demand for fine-grained control over every aspect of the infrastructure lifecycle grows. Crossplane, by extending Kubernetes' control plane capabilities to manage external resources, has been at the forefront of this movement. The introduction of function-controlled deletion further solidifies its position as a robust framework for building sophisticated internal developer platforms, allowing for complex operational logic to be embedded directly into the infrastructure definitions. In practice, this means platform engineers can now design compositions that, for example, ensure a database backup completes before the database instance is terminated, or that dependent services are gracefully shut down before their underlying infrastructure is removed. Practitioners should explore the new `spec.deletionPolicy` field in Compositions, particularly the `Pipeline` option, to leverage this feature. While currently in alpha, it's a strong indicator of Crossplane's evolving maturity in handling complex, real-world operational requirements. Teams should begin experimenting with this in non-production environments to understand its implications for their custom compositions and deletion strategies, preparing for its eventual stable release.
#crossplane#platform engineering#infrastructure as code#devops#kubernetes#control plane
Read original source