This month marks the two year birthday of Crossplane, and it's major 1.0 release which is now available to use on Upbound Cloud. Crossplane 1.0 brings many improvements to Upbound Cloud, including automatic dependency which makes installing Configurations from Upbound Registry easier, as well as v1 status to the composition API which makes defining your own cloud API easier.
Try it yourself today on Upbound Cloud, and continue reading to learn more about how the Crossplane community is celebrating this milestone!
Crossplane Turns 2
Two years ago Upbound created Crossplane realizing Kubernetes could let any organization, team, or individual operate their infrastructure and application development like the major cloud vendors do - with their own custom cloud API that hides infrastructure complexity from developers and gives operators a uniform point of control across environments.
Crossplane installs into any Kubernetes cluster where it adds CRDs representing resources available in any cloud or on-premises environment. Operators can manage infrastructure using these CRDs directly, or build their own "Composite Resource Definitions" (XRDs) on top of the CRDs which encapsulate organization policy guardrails behind the API line. XRDs define the custom cloud API provided by Crossplane. Application developers can then self-service these XRDs using
kubectl or a UI interface from products like Upbound Cloud.
This API-centric approach to infrastructure and modernization is quickly becoming mainstream in the cloud-native community. The project has 10M DockerHub pulls, 2,800+ GitHub stars, and a vibrant Slack community. It's also being run in production at some of the world's best companies.
Join the Celebration
To celebrate the project's two year birthday, we're hosting Crossplane Community Day where we're highlighting the amazing work done by community members, and talking about why the cloud native community is rapidly converging on Crossplane as an API-centric approach to modernization.
Register to view the replay and see how community members are using the project.