With Crossplane, operators can manage cloud resources like anything else inside Kubernetes. More than that, operators can build custom APIs and complete cloud deployments. Operators can mix resources across cloud providers, provide state enforcement and simplify deployments. »
Crossplane goes beyond the capabilities of Kubernetes to control infrastructure outside of the traditional scope of Kubernetes. »
A lack of API compatibility can lead to dangerous and unpredictable behavior, but Crossplane packages make it possible to present a consistent programming interface across multiple clusters. »
Over the past few months Crossplane has pushed the boundaries of Kubernetes with the number of Custom Resources it supports. In this post we’ll explore the limitations Upbound engineers have discovered and how we’ve helped to overcome them. »
Composing infrastructure is difficult. We alleviate this pain by moving Crossplane package authoring from plain YAML to IDE aided development. »
OverviewToday, we're announcing the Azure Reference Platform for Kubernetes + Data Services configuration package release in Upbound Registry. The Upbound Platform Reference Architectures (AWS, GCP, Azure, Cloud-Native, »
Crossplane now has 100% coverage for major cloud services with the new providers: provider-jet-aws, provider-jet-azure, and provider-jet-gcp. To create new providers like these, we are introducing Terrajet, a code generation pipeline for creating Crossplane providers. »
Today the CNCF announced that the open source Crossplane project, created by Upbound and with a broad community of contributors, has reached incubation level at the »
Terraform is a widely deployed and popular technology that is used to enable an Infrastructure-as-Code (IaC) approach. While Terraform can be extremely useful, it does have »
Continuous Integration and Continuous Deployment, better known by the acronym CI/CD is the foundation of modern DevOps. At the Crossplane Community Day Europe virtual event, »