Crossplane Concepts TODEPLETE: Difference between revisions
| Line 8: | Line 8: | ||
* https://blog.crossplane.io/crossplane-vs-terraform/ | * https://blog.crossplane.io/crossplane-vs-terraform/ | ||
=Control Plane= | =Control Plane= | ||
<font color=darkkhaki>What is a control plane?</font> | <font color=darkkhaki>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. | |||
</font> | |||
Revision as of 21:07, 30 July 2022
Internal
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.
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/
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.
Provider
A provider extends Crossplane to orchestrate new kinds of applications and infrastructure.
Configuration
A configuration extends Crossplane to expose new APIs.