TKG service 3.2.0 introduces a new builtin-generic-v3.2.0
ClusterClass.
You can create new TKG service clusters using the new builtin-generic-v3.2.0
cluster class by setting builtin-generic-v3.2.0
as a value to the spec.toppology.class
field on the Cluster CR.
Existing TKG service clusters that use the v1beta1 API can leverage the builtin-generic-v3.2.0
cluster class if you remove the kubernetes.vmware.com/skip-auto-cc-rebase
annotation. Since the builtin-generic-v3.2.0
cluster class introduces a new variable schema, it is recommended to perform this operation when updating the Kubernetes version to automatically convert the existing Cluster variables to the new schema.
If you want to use the builtin-generic-v3.2.0
cluster class without upgrading the Kubernetes version, then you must convert the variables on the Cluster v1beta1 to follow the new variable schema. See ClusterClass Variables for Customizing a Cluster for more details.