# rpk k8s multicluster status

> For the complete documentation index, see [llms.txt](https://docs.redpanda.com/llms.txt). Component-specific: [streaming-full.txt](https://docs.redpanda.com/streaming-full.txt)

---
title: rpk k8s multicluster status
latest-redpanda-tag: v26.2.1
latest-console-tag: v3.10.0
latest-operator-version: v26.2.1
# EOL = End-of-Life (support lifecycle status)
page-is-nearing-eol: "false"
page-is-past-eol: "false"
page-eol-date: July 28, 2027
latest-connect-version: 4.105.0
docname: rpk/rpk-k8s/rpk-k8s-multicluster-status
page-component-name: streaming
page-version: "26.2"
page-component-version: "26.2"
page-component-title: Streaming
page-relative-src-path: rpk/rpk-k8s/rpk-k8s-multicluster-status.adoc
page-edit-url: https://github.com/redpanda-data/docs/edit/main/modules/reference/pages/rpk/rpk-k8s/rpk-k8s-multicluster-status.adoc
description: "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."
page-git-created-date: "2026-07-22"
page-git-modified-date: "2026-08-03"
support-status: supported
---

<!-- Source: https://docs.redpanda.com/streaming/current/reference/rpk/rpk-k8s/rpk-k8s-multicluster-status.md -->

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.

> 📝 **NOTE**
>
> This command was introduced in k8s version 26.2.1.

## [](#usage)Usage

```bash
rpk k8s multicluster status [flags]
```

## [](#examples)Examples

This section provides examples of how to use `rpk k8s multicluster status`.

Check status across all clusters in a kubeconfig

```bash
rpk k8s multicluster status --kubeconfig /path/to/kubeconfig
```

Check specific clusters

```bash
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)

```bash
rpk k8s multicluster status \
  --context cluster-a --context cluster-b \
  --name-override cluster-a=redpanda-operator \
  --name-override cluster-b=rp-operator
```

## [](#flags)Flags

| Value | Type | Description |
| --- | --- | --- |
| --context | strings | Kubernetes contexts (repeatable; if omitted with --kubeconfig, all contexts in the file are used). |
| --kubeconfig | string | Path to a kubeconfig file (all contexts in the file are used unless --context is also specified). |
| --name-override | stringArray | Override the TLS secret prefix for a context in context=prefix format (repeatable; defaults to the context name). |
| --namespace | string | Namespace for operator resources. |
| --service-name | string | Operator deployment label selector value (app.kubernetes.io/name). |

## [](#global-flags)Global flags

| Value | Type | Description |
| --- | --- | --- |
| --config | string | Redpanda or rpk config file; default search paths are ~/.config/rpk/rpk.yaml, $PWD/redpanda.yaml, and /etc/redpanda/redpanda.yaml. |
| -X, --config-opt | stringArray | Override rpk configuration settings; -X help for detail or -X list for terser detail. |
| --ignore-profile | bool | Ignore rpk.yaml and redpanda.yaml; use default settings. |
| --profile | string | rpk profile to use. |
| -v, --verbose | bool | Enable verbose logging. |