Make it easier to understand if a ClusterClass is ready

[sbueringer]

Today ClusterClass has a VariablesReconciled and a RefVersionsUpToDate condition
observedGeneration is (as usual) only set if a ClusterClass is reconciled without any errors.

Goal of this issue is to make it easier for users to see if a ClusterClass is ready, one way to to this would be to introduce a Ready condition which summarizes the state of the other conditions.

Then users only have to check for the Ready condition and not all conditions.

/area topology
/kind feature

[sbueringer]

cc @killianmuldoon @fabriziopandini

[oscr]

I think encoding the requirements for a CC to be ready is a clear improvement for users. Great suggestion

/triage accepted

[vincepri]

Is this readiness in the context of initialization?

[sbueringer]

What do you mean with "initialization"?

The idea was to make it easier to understand if a ClusterClass is reconciled so a Cluster can be reconciled.

This is relevant after initial deployment of the ClusterClass, but also later if a ClusterClass is updated.

[vincepri]

Got it, so Ready might change over time if there are changes on the ClusterClass itself that needs to be reconciled. I meant initialization as a first sync, somewhat like when a control plane gets initialized (which might fall into a different condition), just wanted to clarify

[sbueringer]

Ah got it. Yup, Ready can flicker back and forth.

[fabriziopandini]

/priority important-longterm

[fabriziopandini]

/kind api-change