fix(crd): remove omitempty tag from CSPI status fields #63
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 PR does the following changes:
If
omitempty
tag is provided then default values arenot shown in the output of
kubectl get cspi <cspi_name> -o yaml
.ALLOCATED and TYPE
printer columns.Without this PR output of cspi:
With changes in this PR:
kubectl get cspi -n openebs NAME HOSTNAME FREE CAPACITY READONLY PROVISIONEDREPLICAS HEALTHYREPLICAS STATUS AGE cstor-sparse-cspc-bwtn centos-worker-1 9630M 9630084500 false 0 0 ONLINE 24m
For more information about the pool:
kubectl get cspi -n openebs -o wide kubectl get cspi -n openebs -o wide NAME HOSTNAME ALLOCATED FREE CAPACITY READONLY PROVISIONEDREPLICAS HEALTHYREPLICAS TYPE STATUS AGE sparse-based-pool-n5q7 centos-worker-1 89k 9630M 9630089k false 0 0 stripe ONLINE 28m
Note to reviewers:
Observation: No errors were shown on the logs and able to create CSPI without status.
Signed-off-by: mittachaitu sai.chaithanya@mayadata.io