Tag - CSP-Cloud Builder
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 22.214.171.124 NSX ALB (Avi) 22.1.2-9086 Based on the above, I don’t need to change a single thing for CSE 4.
Bill of Materials VMware vRealize Log Insight 8.10.2 VMware Cloud Director 10.4.1 VMware Cloud Director App Launchpad Extension 2.1.2 Photon OS 4.0 (for ALP) Have you deployed the Application Launchpad (ALP) extension into VMware Cloud Director in your Cloud Platform? You’re probably wondering how you can get those pesky logs out from your ALP servers. I found a great post by Vysakh Nair detailing how to use the vRLI Agent to forward logs from Cloud Director appliances.
- Restore of a Wordpress deployment is stuck redirecting the port
- Backups and Restores using Velero in TKGm 1.6.1
- Unable to upgrade the database: org.postgresql.util.PSQLException: ERROR: could not open shared memory segment: No such file or directory
- Upgrading Cloud Director 10.4.1 to 10.5
- Installing and Configuring Velero in TKGm 1.6.1 on vSphere