"The new major release intends to address limitations that platform teams have cited, specifically that whilst the tool excels at enabling infrastructure self-service, there is still a division between the infrastructure and applications which need to be dealt with seperately. Crossplane 2.0 adds application support, so platform teams can now provide a single YAML manifest to deploy an application and the infrastructure it needs."
"On top of adding support for applications in version 2, another substantial change enables compositions (a template for creating multiple Kubernetes resources as a single composite resource) to include any Kubernetes resource, not just infrastructure managed by Crossplane. This enhancement, documented in a page describing what's new in v2, allows platform teams to develop unified abstractions that provision databases, configure networking, deploy applications, and establish monitoring within a single composite resource definition."
"The Crossplane open-source project has announced the release of version 2.0, an upgrade that moves the project from managing only cloud infrastructure to more comprehensive application and infrastructure orchestration. Some architectural changes have also been made to simplify platform engineering workflows and expand the project's original scope. First created in 2018, Crossplane brings Kubernetes-style APIs to cloud resource management, so that engineers can manage public cloud infrastructure directly in Kubernetes, through Kubernetes CRDs (Custom Resource Definitions)."
Crossplane 2.0 expands the project's scope from cloud infrastructure management to combined application and infrastructure orchestration. Crossplane uses Kubernetes-style APIs and CRDs to let engineers manage public cloud resources directly within Kubernetes. Version 2.0 adds application support so teams can provide a single YAML manifest to deploy an application and its required infrastructure, such as databases, security groups, and ingress. Compositions can now include any Kubernetes resource, enabling unified abstractions for provisioning, networking, deployment, and monitoring. The release also shifts to a namespace-first model, namespacing composite and managed resources by default to improve multi-tenancy and align with Kubernetes conventions.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]