Our main focus in v0.13 is paving the way for a v1.0 release of Crossplane. Over the course of this release we have honed our core Composition and Package Manager APIs. With the help of the community we’ve arrived at APIs that we feel confident will reach v1beta1 imminently without significant breaking changes.
We are very pleased to announce that Crossplane has been accepted into the Cloud Native Computing Foundation (CNCF) as a Sandbox project! The team of contributors has worked incredibly hard to grow the community and mature the project, so this is a great validation that Crossplane has reached a new
A collaboration between Upbound and Red Hat Emerging Technologies explores the Crossplane project and its recent optimization with Red Hat OpenShift Container Platform as an alternative to Open Service Broker API for provisioning, managing, and consuming external services by cloud native applications. In this blog post, we will build a
The v0.11.0 release officially introduces Crossplane as the Kubernetes runtime for the Open Application Model. Improved documentation and expanded support for infrastructure composition serve to clearly establish the core features of Crossplane and the separation of concern it provides for different personas within a team or organization. Rounding out the release are improved security measures, support for new managed resources, and the convergence on Packages as the installation unit for Crossplane extensions.
Experimental support for resource composition unlocks the ability for everyone to author and publish their own infrastructure recipes in a low/no-code way. More cloud services and Velero backup and restore compatibility round out this release!
This PR updates the Crossplane project governance to meet the following goals:
Increase diversity of maintainers, enable more organizations to collaborate and have ownership
Allow varying permissions and access across multiple repos and multiple maintainers
Improve change velocity by expanding number of maintainers that can approve and merge pull requests
Formalize responsibilities at the top level for the purpose of project stewardship, adoption, growth and health of the community, and strategic direction