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
When Crossplane generates CRDs for Claims and Composites it defines the additional printer columns "SYNCED" and "READY" in that order, which is logically read from left to right in the output. A resource cannot be READY before it is SYNCED, so it is easier to read the resource status in that order.
upjet generates CRDs for resources with the columns "READY SYNCED" which is inconsistent with the resources that Crossplane generates.
How can we reproduce it?
Observe the kubectl get output for Claims/Composites and generated upjet resources
The text was updated successfully, but these errors were encountered:
What happened?
When Crossplane generates CRDs for Claims and Composites it defines the additional printer columns "SYNCED" and "READY" in that order, which is logically read from left to right in the output. A resource cannot be READY before it is SYNCED, so it is easier to read the resource status in that order.
upjet generates CRDs for resources with the columns "READY SYNCED" which is inconsistent with the resources that Crossplane generates.
How can we reproduce it?
Observe the
kubectl get
output for Claims/Composites and generated upjet resourcesThe text was updated successfully, but these errors were encountered: