Add more print columns to ClusterResourceSet/Bindings for better tracking

[sp-yduck]

What would you like to be added (User Story)?

Currently ClusterResourceSet and ClusterResourceSetBinding does not show their stats and It's hard to debug.
So I would like to add more useful status fields for CRSB. (I belive we can somehow improve CRS as well but this PR is targetting CRSB for now)

as is

# kubectl get clusterresourcesetbinding
NAME               AGE
capi-test-crsb-0   43m

I'm thinking something like

# kubectl get clusterresourcesetbinding
NAME               CLUSTER     PHASE     AGE
capi-test-crsb-0   cluster-0   Pending   43m

sorry for very abstract request but it would be nice if we can have these better visibility.

Detailed Description

• Define what kind of status should be added in ClusterResourceSetBindings.status
• implement some new field for ClusterResourceSetBindings.status

Anything else you would like to add?

at least CLUSTER is verry easy to add to the columns of kubectl get

Label(s) to be applied

/kind feature
/area clusterresourceset

[killianmuldoon]

Is this about the status of the object, or just the output of a command like kubectl get?

[sp-yduck]

both status of the object and output of the kubectl

[killianmuldoon]

The ClusterName is currently in the ClusterResourceSetBinding .spec - do you mean to also add it to status? Currently there is no status associated with a ClusterResourceSetBinding.

It would be good to get an idea of what you'd like to see in the status and what you'd like to see in the output of kubectl get to understand this issue better.

/triage accepted

[sp-yduck]

ah sorry for lack of explanation. I would like to

1. Introduce new field for describing current status/condition of CRSB
2. Show both these newly added field and existing field (e.g. .spec.clusterName) in the output of kubectl get

Scenario:
Users deployed CRS/CRSB and then would like to know wether the resources are applied to workload cluster as expected or not. For this case, users would like to check the briefly status by using kubectl get command. This is what I want to achieve for 2.
After checking kubectl get, users might see something unexpected status in the output of kubectl get like Pending, Failed whatever something signal for unexpected status. Then users would like to know more detailed status by using kubectl get -oyaml or kubectl describe for further debugging. Users can check more detailed status in the status field for example CRSB has correctly bound the CRS ?, Workload cluster is Ready ? Resources are properly applied to workload cluster ? etc. and some Reason or LastTransitionTime etc. for these statuses like other k8s objects. This is what I want to achieve for 1.

[sp-yduck]

After some thinking, maybe just improve the output of kubectl get clusterresourceset is fine. Since ClusterResourceSet has already status.conditions field. It's easier than changing api of CRSB.

As of now, the output is

# kubectl get clusterresourceset
NAME              AGE
capi-test-crs-0   43m

Then if we could have some additional fields like

# kubectl get clusterresrouceset
NAME              APPLIED    CLUSTER-SELECTOR   AGE
capi-test-crs-0   false      label=value        43m

it helps people to understnd the situation of CRS/CRSB easily.
Firstly we can check whether the resources are applied of not. And also we can try kubectl get cluster -l label=value to see if CRS is properly configured with expected clusters.

[fabriziopandini]

/priority important-longterm