Crossplane Concepts TODEPLETE: Difference between revisions
| Line 1: | Line 1: | ||
=Internal= | =Internal= | ||
* [[Crossplane#Subjects|Crossplane]] | * [[Crossplane#Subjects|Crossplane]] | ||
=Organizatorium= | |||
* https://blog.upbound.io/introducing-crossplane-open-source-multicloud-control-plane/ | |||
* https://docs.google.com/document/d/1whncqdUeU2cATGEJhHvzXWC9xdK29Er45NJeoemxebo/edit | |||
* https://blog.crossplane.io/crossplane-vs-terraform/ | |||
=Overview= | =Overview= | ||
Crossplane is an open source Kubernetes add-on that enables platform teams to assemble infrastructure from multiple vendors, and expose higher level self-service APIs for application teams to consume. | Crossplane is an open source Kubernetes add-on that enables platform teams to assemble infrastructure from multiple vendors, and expose higher level self-service APIs for application teams to consume. | ||
Revision as of 21:15, 30 July 2022
Internal
Organizatorium
- https://blog.upbound.io/introducing-crossplane-open-source-multicloud-control-plane/
- https://docs.google.com/document/d/1whncqdUeU2cATGEJhHvzXWC9xdK29Er45NJeoemxebo/edit
- https://blog.crossplane.io/crossplane-vs-terraform/
Overview
Crossplane is an open source Kubernetes add-on that enables platform teams to assemble infrastructure from multiple vendors, and expose higher level self-service APIs for application teams to consume.
Crossplane is a Kuberentes add-on that transforms the cluster into an universal control plane.
Crossplane enables applications and infrastructure configuration to co-exist in the same control plane.
Control planes built with Crossplane integrate with CI/CD pipelines, so team can create, track and approve changes using GitOps best practices.
Separation of concerns: allows implementing organizational concepts and policy at the API level.
Control Plane
What is a control plane?
Control planes are self-healing, they automatically correct drift.
Control planes offer a single point of control for policy and permissions.
Control planes integrate easily with other systems because they expose an API, not just a command line.
Crossplane can be used to design ad implement a control plane that expose declarative APIs tailored to your unique orchestration needs.
A control plane is made up of several controllers, which are responsible for the life cycle of a resource. Each resource is responsible for provisioning, health, scaling, failover and actively responding to external changes that deviate from the desired configuration.
Provider
A provider extends Crossplane to orchestrate new kinds of applications and infrastructure.
Configuration
A configuration extends Crossplane to expose new APIs.