Go Beyond Infrastructure as Code with Control Planes
The Cloud Native movement has largely been defined in recent years with the rise of Kubernetes and its broad adoption as a container orchestration platform. Kubernetes’ true “superpower” is that it can become the control plane for any kind of resource, not just containers.
What is a Control Plane?
Peeking behind the scenes of the three major cloud providers will reveal that each one runs their business using a key piece of technology they call a control plane. We are democratizing this technology with our open source, Kubernetes inspired, Crossplane project. Upbound enables you to run your business like the cloud providers run theirs.
Kubernetes resources are managed around API’s and not templates. The API runs continuously in an automation loop to reconcile changes and adjust for drift.
Better Policy Adherence
A control plane model ensures that operation and development teams adhere to an organization’s security, compliance or governance policies defined in the APIs provided by the control plane.
Easily Capture Automation
A universal control plane like the one Crossplane enables, enables teams to have a single location where they can easily capture automation.
We didn't set out to build a control plane just as a piece of infrastructure, we set out to build a container platform and the control plane was kind of an important design consideration, but it was not a primary focus.
Distinguished Engineer at Google
Brian Grant is a Distinguished Engineer at Google
Modern Infrastructure Utilizes Strong Separation of Concerns
The separation of concerns is at the core of Crossplane’s approach to infrastructure and application management. This empowers team members to deliver value by focusing on what they know best.
Administrators have detailed control of their infrastructure and can define environment specifics and policies with the help of Crossplanes strong separation of concerns. Empowering Admins to focus on what they do best.
SREs and DevOps engineers compose cloud APIs using Crossplane’s Composition feature. Policies, permissions, and quotas for resources are encapsulated behind an API and continuously reconciled by the control plane.
App teams can self-service infrastructure safely by consuming APIs built by platform teams and provided by Crossplane. This workflow was designed with GitOps best practices in mind and is easily integrated into existing pipelines.
Still need more information? We’ve curated some related resources that may help you learn more on the topic.