FAQs

This section details frequently asked questions about VMware Cloud Director Container Service Extension 4.1.

As a previous Kubernetes Container Clusters UI user, how does this new release affect me?

With this Kubernetes Container Clusters UI plug-in, users can create, manage, and upgrade Tanzu Kubernetes Grid clusters. The clusters are created with Cluster APIs of VMware Cloud Director, behind the scenes. All of your previously created clusters of types such as native, vSphere with Tanzu, and Tanzu Kubernetes Grid legacy are still available.

What is Tanzu Kubernetes Grid Clusters Legacy?

All Tanzu Kubernetes Grid clusters created using VMware Cloud Director Container Service Extension server 3.1.x are now referred to as Tanzu Kubernetes Grid Legacy clusters in 4.0 and newer versions.

As a first time user of Kubernetes Container Clusters 4.x, what do I need to know?

To allow tenant users to create, manage, and upgrade Tanzu Kubernetes Grid clusters, you must install VMware Cloud Director Container Service Extension server 4.0 or newer versions. To allow tenant users to create and manage native, vSphere with Tanzu, or Tanzu Kubernetes Grid Legacy clusters, you must separately install VMware Cloud Director Container Service Extension server 3.1.x.

What is the difference between VMware Cloud Director Container Service Extension Server 3.1.x and 4.x?

VMware Cloud Director Container Service Extension server 3.1.x powers native and Tanzu Kubernetes Grid Legacy cluster functionality, whereas VMware Cloud Director Container Service Extension server 4.0 and newer versions, power Tanzu Kubernetes Grid cluster functionality. Tenant users can create, view, and manage these different cluster types in the Kubernetes Container Clusters UI plug-in.