-
Notifications
You must be signed in to change notification settings - Fork 307
Description
Is your feature request related to a problem?
The output of kubectl get rabbitmqcluster doesn't provide much information, other than the existence of the object itself and its age. We should expose relevant status information here, as this output is more concise and convenient than the verbose kubectl describe.
Describe the solution you'd like
Add printing columns to display the status conditions AllReplicasReady and ReconcileSuccess. These two conditions provide information as "are all RabbitMQ nodes ready?" and "does this cluster have up to date configuration?".
Describe alternatives you've considered
Exposing all status conditions as columns. I'm not sure it's interesting to expose ClusterAvailable because most of the time, as a user, one would want to have all nodes in a good state. The ClusterAvailable condition is set to true as long as there is one node ready.
Exposing NoWarnings would surface the presence of a not-recomended configuration e.g. memory requests mismatching memory limits. This might be interesting to surface, but at the moment it only checks for the mentioned memory mismatch, which doesn't happen often I believe. In the future, if we add more checks, it could be interesting to expose.
Additional context
Follow up from #646