Container Services Extension(CSE) 4.2.2 When creating TKG Cluster, only one worker node and single control plane node are created even though during wizard there are defined more, as well as attempting to increase them after creation.
Container Services Extension 4.2.2
Component versions incorrect for Container Services Extension 4.2.2
| | 4.2.2 required | Environment|
|----------------------------------------|--------------------|------------------|
| capvcdVersion | v1.3.2 | v1.3.0 |
| cpiVersion | 1.6.1 | 1.6.0 |
| csiVersion | 1.6.0 | 1.6.0 |
| kindVersion | v0.24.0 | v0.20.0 |
| clusterctlVersion | v1.7.4 | v1.5.4 |
| coreCapiVersion | v1.7.4 | v1.5.4 |
| bootstrapProviderVersion | v1.7.4 | v1.5.4 |
| controlPlaneProviderVersion | v1.7.4 | v1.5.4 |
| kindestVersion | v1.31.0 | v1.27.3 |
| certManagerVersion | v1.15.1 | v1.13.2 |
| projectorVersion | 0.7.1 | 0.7.0 |
1. Use CSE UI plugin to update these values in the vcdkeconfig. As a provider user (sysadmin, etc), go to CSE UI plugin's Container Services Extension Management tab -> Server Details -> 'Update Server' button -> Patch version upgrade (More information - Patch version upgrade)
2. Patch version upgrade workflow will update these versions in the vcdkeconfig entity. Afterwards, check the vcdkeconfig entity to confirm that version values are updated, and confirm that any potential custom values such as registry are retained (please save a copy of this updated json so we can debug further)
3. Power Off and Power On all CSE server vapps. This will allow the CSE server to fetch/cache the updated vcdkeconfig.
4. For the kubernetes clusters, the component versions that they are using will now be outdated. Clusters must be updated manually using our cluster upgrade script. Upgrade Kubernetes Components in VMware Cloud Director Container Service Extension Clusters
Once these steps are done, confirm CSE server upgrade to 4.2.2 was successful. Create a new cluster, as well as upgrade an existing cluster (if needed).