Multi-cluster

One dashboard, many clusters

Gameplane manages the local cluster plus any number of registered remote clusters from a single dashboard. Each target cluster runs its own operator instance reconciling its own GameServers; the control-plane API dispatches requests to the right cluster through a ?cluster=<name> selector, with the built-in local cluster targeting the same cluster the API runs on.

Registering a cluster

Two steps: a labeled Secret holding the remote kubeconfig, then a cluster-scoped Cluster CR that references it.

CLUSTER KUBECONFIG SECRET

apiVersion: v1
kind: Secret
metadata:
  name: my-cluster-kubeconfig
  namespace: gameplane-system
  labels:
    gameplane.local/cluster-kubeconfig: "true"
type: Opaque
data:
  kubeconfig: <base64-encoded kubeconfig for the target cluster>

CLUSTER CR

apiVersion: gameplane.local/v1alpha1
kind: Cluster
metadata:
  name: my-cluster
spec:
  displayName: My Cluster
  kubeconfigSecret:
    name: my-cluster-kubeconfig

The gameplane.local/cluster-kubeconfig label guard means a Cluster CR can only ever reference a Secret an admin has explicitly marked for this purpose, not an arbitrary Secret in the namespace. See the CRD catalog for the full Cluster spec.

Health and status

The operator health-checks every registered cluster and reconciles status.phase (Unknown / Healthy / Unhealthy) plus status.serverVersion, so connectivity shows up directly in the dashboard’s cluster selector — no separate ping needed. Namespaced operations (GameServers, Backups, and the rest) route to whichever cluster is selected, and RBAC role bindings are evaluated per cluster.

Boundaries

• Control-plane state stays local. Users, sessions, the audit log, config, and the database live only on the local cluster — remote clusters run game workloads, nothing else.
• No implicit RBAC. Registering a cluster grants no access to it; role bindings created before a cluster was registered stay pinned to local, and a new cluster needs its own bindings.
• Streams are local-cluster-scoped today. Console, log, and file WebSocket streams only work against the local cluster — remote clusters are registered and health-checked, but not yet streamed to.

New to Gameplane? Start with Getting Started to stand up the local cluster first. The full registration walkthrough and prerequisites live in the install docs on GitHub.