VMware Cloud Director Container Service Extension 3.1.x and VMware Cloud Director Container Service Extension 4.x are two different technical stacks. It is not possible to upgrade between the two versions. To serve VMware Cloud Director Container Service Extension 3.1.x cluster requirements, a server co-existence model exists and is supported through the Kubernetes Container Clusters UI plug-in 4.x.
If tenant users have Tanzu Kubernetes Grid clusters that were created in VMware Cloud Director Container Service Extension 3.1.x and they want to adopt the Tanzu Kubernetes Grid feature set of VMware Cloud Director Container Service Extension 4.x, it is necessary to install VMware Cloud Director Container Service Extension 4.x server. If a tenant user wants to keep VMware Cloud Director Container Service Extension 3.1.x clusters, both Tanzu Kubernetes Grid and native, they can use a co-existence model in the same VMware Cloud Director environment, where the servers exist side by side.
When a tenant user wants to create a new cluster, they can only create Tanzu Kubernetes Grid clusters, and can only create them in VMware Cloud Director Container Service Extension 4.x through the Kubernetes Container Clusters UI plug-in 4.x.
The aim of the server co-existence model is that eventually tenant users will migrate Kubernetes workloads from VMware Cloud Director Container Service Extension 3.1.x Tanzu Kubernetes Grid clusters to VMware Cloud Director Container Service Extension 4.x Tanzu Kubernetes Grid, and remove VMware Cloud Director Container Service Extension 3.1.x from VMware Cloud Director.
Frequently Asked Questions
| Question | Answer |
|---|---|
| Do I need the VMware Cloud Director Container Service Extension 3.1.x server? | It necessary to keep the VMware Cloud Director Container Service Extension 3.1.x only if you want to continue to manage VMware Cloud Director Container Service Extension 3.1.x clusters |
| Do I need two Kubernetes Container Clusters UI plug-ins to support the co-existence model? | No. You can manage both VMware Cloud Director Container Service Extension 3.1.x and VMware Cloud Director Container Service Extension 4.x clusters through the Kubernetes Container Clusters UI plug-in 4.x. |
| When can I remove VMware Cloud Director Container Service Extension 3.1.x server and keep only the VMware Cloud Director Container Service Extension 4.x server? | Once you delete all clusters managed by VMware Cloud Director Container Service Extension 3.1.x, you can unregister and remove VMware Cloud Director Container Service Extension 3.1.x server |
| Can I migrate VMware Cloud Director Container Service Extension 3.1.x clusters and manage them through the VMware Cloud Director Container Service Extension 4.x server? | No. It is necessary to create a new VMware Cloud Director Container Service Extension 4.x cluster, manually migrate apps over from VMware Cloud Director Container Service Extension 3.1.x cluster to VMware Cloud Director Container Service Extension 4.x cluster, and then delete VMware Cloud Director Container Service Extension 3.1.x cluster. |
| Can I migrate native Kubernetes clusters from VMware Cloud Director Container Service Extension 3.1.x server to VMware Cloud Director Container Service Extension 4.x server? | No, VMware Cloud Director Container Service Extension 4.x server does not support native Kubernetes clusters. To support this type of cluster, it is necessary to use the co-existence server model with the support of Kubernetes Container Clusters UI plug-in 4.x. |
