Skip to main content
Version: v5.0 Stable

Manage Allowed Clusters

Allowed clusters control the clusters which project members are granted access.

Project and tenant allowlists follow different rules

In a tenant's project, a project member reaches only what both the project and the tenant allow. The two layers write "everything" and "nothing" differently.

LayerFieldTo allow everythingTo allow nothing
ProjectallowedClusters, a list of namesAdd an entry named "*"Leave the field unset or empty
Tenantallow.byLabels, a label selectorSet an empty selectorOmit the selector

An empty tenant selector matches every admin-owned control plane cluster. An omitted selector grants none by label, but the tenant still reaches any control plane cluster assigned to it or shared with every tenant. The tenant layer can also grant each control plane cluster by name with allow.byName. The tenant capability must also be enabled. A disabled capability withholds every control plane cluster, including ones assigned to the tenant.

A project allowlist can't add inventory the tenant was never granted. See Tenant boundary reference.

Add allowed clusters​

  1. Select the project you'd like to configure using the project selector dropdown. Click Project Config.

  2. Click on Control Plane Clusters.

  3. Click on the input and select the cluster names to allow. If you wish to change this manually, you may edit the YAML directly.

  4. Once all project options have been specified, click the .

All Clusters

Instead of selecting every cluster, a special selection named All Clusters can be used to give access to all clusters to the project. Use this option with caution.