Tag - CSE
I recently posted how to upgrade VMware Cloud Director’s Container Service Extension from 4.0.1 to 4.0.3. The next step in the journey is to configure the new CAPVCD provider (1.0.1) on any existing Kubernetes clusters deployed by CSE, and then upgrade those clusters from TKG 1.5.4 images to TKG 1.6.1 images. Wait, what am I updating? Kubernetes clusters deployed by CSE include what’s called a Cluster API Provider (CAP) for VMware Cloud Director (VCD) which is where we get CAPVCD.
I’ve got VMware Cloud Director Container Service Extension (CSE) 4.0.1 running in my lab to test and demo Kubernetes Clusters as-a-service in Cloud Director. CSE 4.0.3 was released on the 20th of April 2023 and came with significant improvements. Let’s take a look at my current environment: VCD 10.4.1 CSE UI Plugin 4.0.1 CSE Server 4.0.1 vSphere 7.0U3 NSX-T 126.96.36.199 NSX ALB (Avi) 22.1.2-9086 Based on the above, I don’t need to change a single thing for CSE 4.
I’ve had some partners ask for a reference that maps VCD, CSE, TKG images and TKr versions in a single table. Behold! The Cloud Director column details the VCD version, CSE details the version of CSE compatible with the VCD builds. TKG Images column lists the versions of Tanzu Kubernetes Grid images that are supported by CSE, and the Tanzu Kubernetes Release (TKr) column details the Kubernetes releases available for the TKG Images version in the list.
- Upgrading CSE-deployed Kubernetes clusters from TKG 1.5.4 to TKG 1.6.1
- Upgrading VCD Container Service Extension from 4.0.1 to 4.0.3
- Understanding and Deploying TKGm 1.6 into vSphere
- Forwarding Cloud Director App LaunchPad logs to vRealize Log Insight using the vRLI Agent
- EFI shell missing from boot menu