Add additional printing columns #729
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This closes #647
Note to reviewers: remember to look at the commits in this PR and consider if they can be squashed
Summary Of Changes
This adds two columns to the output of
kubectl getforRabbitmqClusters:These correspond to the equivalent fields in the Status of the object in question.
Additional Context
For example, when creating a 3-node cluster:

Once the deployment is complete:

After applying an update to the cluster:

After applying an update that fails to reconcile (in this case, some override config that was incorrect):

I considered adding system tests for this feature, however decided against it as I believe these tests would be too brittle to changes to kubectl itself, and feels outside the remit of testing for this repo.
Local Testing
Please ensure you run the unit, integration and system tests before approving the PR.
To run the unit and integration tests:
You will need to target a k8s cluster and have the operator deployed for running the system tests.
For example, for a Kubernetes context named
dev-bunny: