rpk k8s multicluster status
Checks the health of the multicluster operators that run a Redpanda Stretch Cluster: each cluster’s operator pod health, raft consensus state, TLS certificate validity, and cross-cluster consistency.
Connects to each specified Kubernetes context, finds the multicluster operator pod, port-forwards to its gRPC transport, and queries raft status. Also inspects Deployment configuration and TLS secrets for correctness.
| This command was introduced in k8s version 26.2.1. |
Examples
This section provides examples of how to use rpk k8s multicluster status.
Check status across all clusters in a kubeconfig
rpk k8s multicluster status --kubeconfig /path/to/kubeconfig
Check specific clusters
rpk k8s multicluster status \
--context cluster-a --context cluster-b --context cluster-c
Override the TLS secret prefix per context (when helm release names differ from context names)
rpk k8s multicluster status \
--context cluster-a --context cluster-b \
--name-override cluster-a=redpanda-operator \
--name-override cluster-b=rp-operator
Flags
| Value | Type | Description |
|---|---|---|
|
strings |
Kubernetes contexts (repeatable; if omitted with |
|
string |
Path to a kubeconfig file (all contexts in the file are used unless |
|
stringArray |
Override the TLS secret prefix for a context in context=prefix format (repeatable; defaults to the context name). |
|
string |
Namespace for operator resources. |
|
string |
Operator deployment label selector value (app.kubernetes.io/name). |
Global flags
| Value | Type | Description |
|---|---|---|
|
string |
Redpanda or |
|
stringArray |
Override |
|
bool |
Ignore |
|
string |
|
|
bool |
Enable verbose logging. |