You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the current behavior
At the moment generated resources don't indicate their provisioning state in tabular kubectl output, so you need to keep checking the yaml output to find out whether they're ready.
Describe the improvement
Adding kubebuilder:printcolumn comments to the generated code would make them much nicer to use:
(Although the name ProvisioningState's probably a bit long.)
At the moment there's not really an equivalent of the message field on the ASOv1 resources - once the condition work spec'd in #1614 is done it would make sense to use the status and message fields from the ready condition (presumably these will supplant the status.provisioningState).
The text was updated successfully, but these errors were encountered:
Describe the current behavior
At the moment generated resources don't indicate their provisioning state in tabular kubectl output, so you need to keep checking the yaml output to find out whether they're ready.
Describe the improvement
Adding
kubebuilder:printcolumn
comments to the generated code would make them much nicer to use:(Although the name
ProvisioningState
's probably a bit long.)At the moment there's not really an equivalent of the
message
field on the ASOv1 resources - once the condition work spec'd in #1614 is done it would make sense to use the status and message fields from the ready condition (presumably these will supplant thestatus.provisioningState
).The text was updated successfully, but these errors were encountered: