rpk cluster health
Queries health overview.
Health overview is created based on the health reports collected periodically from all nodes in the cluster. A cluster is considered healthy when the following conditions are met:
-
all cluster nodes are responding
-
all partitions have leaders
-
the cluster controller is present
Flags
Value | Type | Description |
---|---|---|
|
string |
The certificate to be used for TLS authentication with the Admin API. |
|
- |
Enable TLS for the Admin API (not necessary if specifying custom certs). |
|
string |
The certificate key to be used for TLS authentication with the Admin API. |
|
string |
The truststore to be used for TLS communication with the Admin API. |
|
string |
Comma-separated list of admin API addresses (<ip>:<port> |
|
- |
When used with watch, exits after cluster is back in healthy state. |
|
- |
Help for health |
|
- |
Blocks and writes out all cluster health changes. |
|
strings |
Comma-separated list of broker <ip>:<port> pairs
(for example,
|
|
string |
Redpanda config file, if not set the file will be searched for in the default. locations |
|
string |
SASL password to be used for authentication. |
|
string |
The authentication mechanism to use. Supported values: SCRAM-SHA-256, SCRAM-SHA-512. |
|
string |
The certificate to be used for TLS authentication with the broker. |
|
- |
Enable TLS for the Kafka API (not necessary if specifying custom certs). |
|
string |
The certificate key to be used for TLS authentication with the broker. |
|
string |
The truststore to be used for TLS communication with the broker. |
|
string |
SASL user to be used for authentication. |
|
- |
Enable verbose logging (default |