Multi-tenant control plane patterns
Typically, multiple product teams will have to access the control plane platform to take advantage of the composition recipes built by the platform engineers. The section covers different patterns that Crossplane supports to enable a multi-tenant control plane. The following are the key two patterns Crossplane users can choose from:
- Multi-tenancy with a single cluster
- Multi-tenancy with multiple clusters
Multi-tenancy with a single cluster
Multi-tenancy with a single cluster is a pattern where all the product teams use a single Crossplane control plane. The control plane is configured to enable multi-tenancy in the same cluster itself. The following facts describe what this setup will look like:
- The product teams are isolated with the namespace Kubernetes construct. Each product team should be assigned a namespace.
- As mentioned previously in an earlier discussion about the difference between XR and Claim, Claims...