ClusterClass reconcilation in tkg 2.1->2.3...

 ClusterClass Reconciliation in TKG:

• Within Tanzu Kubernetes Grid (TKG), there exists a default ClusterClass in the tkg-system namespace which acts as a blueprint.
• When a new cluster is created in a different namespace, for example, jayunit100, TKG makes a clone of this default ClusterClass into that namespace.

Behavior with Changes to ClusterClass:

• If modifications are made to the copied ClusterClass in the jayunit100 namespace, for example, changing a parameter from a=0 to a=1, these changes are overwritten and reverted back to the defaults of the original ClusterClass. This behavior appears to be controlled by the object-propagator-controller, which reconciles the default ClusterClass and its related objects based on the source objects located in the tkg-system namespace. The interval of this reconciliation seems to vary, with some users observing changes being reset at intervals of approximately 5 to 10 minutes.

This is worth knowing bc if you say, set machineHealthChecks in a machineDeployment, the ClusterClass will overwrite them.

BUT if you set them in ClusterClass the PARENT clusterclass will overwrite them.

So.... That means you cant customize machineHealthChecks ... after a cluster is created?????

will look into this....