rpk k8s multicluster status
Check the health of the multicluster operators that run a Stretch Cluster: 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.
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 |
|
string |
Namespace for operator resources (default |
|
string |
Operator deployment label selector value ( |
Global flags
| Value | Type | Description |
|---|---|---|
|
string |
Redpanda or |
|
stringArray |
Override |
|
bool |
Ignore |
|
string |
|
|
bool |
Enable verbose logging. |