Connect a cluster
Open Settings → Configuration clusters, choose Add cluster, and follow the generated instructions.1
Save the credential
KAOP displays the cluster credential once. Store it securely before leaving the screen.
2
Create the Kubernetes Secret
Use the generated command to place the credential in a Kubernetes Secret. The credential is not
embedded in the Helm command or stored as a Helm value.
3
Install the operator
Run the generated Helm command. It includes the KAOP URL, namespace, and Secret name required by
the operator.
4
Confirm the first sync
Return to the configuration-clusters list and verify that the cluster reports a recent sync.
Read cluster status
Each cluster reports its namespace, operator version, declared-resource count, and last sync.Understand the Cluster-managed badge
Resources declared by an operator carry a Cluster-managed badge. The effect of a console or API edit depends on the cluster’s state and ownership enforcement:
Treat the manifest as the source of truth whenever a resource is cluster-managed.
Pause, resume, or remove a cluster
- Pause stops reconciliation while preserving the cluster and ownership records.
- Resume reconciles the manifests again and can overwrite changes made while paused.
- Remove revokes the cluster credential and stops managing its resources. It does not delete the declared resources from KAOP, and the removal cannot be resumed.
Next steps
Audit log
Review cluster connection and lifecycle changes.
Roles & permissions
Control who can view or manage configuration clusters.
Credentials & secrets
Manage one of the resource types a cluster can declare.
MCP Gateway
Configure governed access to MCP servers.