rpk cluster config status
Get configuration status of redpanda nodes.
For each node, indicate whether a restart is required for settings to take effect, and any settings that the node has identified as invalid or unknown properties.
Additionally show the version of cluster configuration that each node has applied: under normal circumstances these should all be equal, a lower number shows that a node is out of sync, perhaps because it is offline.
Flags
| Value | Type | Description |
|---|---|---|
|
- |
Help for status. |
|
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. |
|
- |
Include all properties, including tunables. |
|
string |
Comma-separated list of admin API addresses (<ip>:<port> |
|
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 |