Fresh deployments of Kubernetes v1.31.9+vmware.1 fail during the EPHEMERAL-TEMP-VM post-bootstrap package phase

Products

• VMware Cloud Director

Issue/Introduction

• After upgrading CSE to v4.2.4 the deployment of k8s v1.31.9 are failing.
• CSE 4.2.4 air-gapped fresh deploy of TKG v1.31.9+vmware.1 creates invalid tanzu-core PackageRepository.
• TKG product version: v2.5.4
• Upgrade from v1.30.13+vmware.1 to v1.31.9+vmware.1 works.

Environment

• VMware Cloud Director 10.6.1.x
• VMware Cloud Director Container Service Extension 4.2.4
• VMware Tanzu Kubernetes Grid v2.5.4

Cause

A string mapping mismatch inside the package bundle's tanzu_core_pkg.yaml. It mistakenly lists v1.31.9+vmware.2 instead of the expected v1.31.9+vmware.1. Because of this typo, the tanzu-core PackageRepository fails to reconcile.

Resolution

Broadcom Engineering is aware of this issue.

For an Air-gapped registry workaround. Please see steps below:

1. Copy the attached updated tanzu-core Image to a machine which has access to the Air-gapped registry and has docker installed .
2. Run the below steps to update the Image on the Air-gapped registry:

docker load -i tanzu-packages-airgapped-v2.5.4_424.tar


docker image ls
# verify the image
# [private registry root]/cse424/vmware-cloud-director/tanzu-packages-airgapped-v2.5.4:4.2.4

docker tag [private registry root]/cse424/vmware-cloud-director/tanzu-packages-airgapped-v2.5.4:4.2.4 [private registry root]/vmware-cloud-director/tanzu-packages-airgapped-v2.5.4:4.2.4


docker push [private registry root]/vmware-cloud-director/tanzu-packages-airgapped-v2.5.4:4.2.4

Following this, try to now create a cluster with v2.5.4 v1.31.9+vmware.1.

Additional Information

Set up a Local Container Registry in an Airgapped Environment