Supervisor Services Installation Fails: Cannot Reach VCF Software Depot

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

Supervisor Services installation fails because it cannot reach the VMware Cloud Foundation (VCF) Software Depot. This prevents the provisioning of required container images and their signatures for verification.

Supervisor encountered an error while trying to reach the container image registry hosting Service Version 0.4.1 and its signatures cannot be verified: Connectivity to image depot.kube-system.svc/vcf/supervisor-service-supervisor-management-proxy/ga/0.4.1/supervisor-management-proxy-bundle:0.4.1 cannot be verified: Get "https://depot.kube-system.svc/v2/": dial tcp: lookup depot.kube-system.svc on 127.0.0.53:53: no such host

Environment

VCF 9.x

Cause

The Regional Harbor registry is missing or not properly provisioned. The internal Software Depot service on the Supervisor is functionally dependent on the Regional Harbor registry being successfully provisioned and associated via VCF Automation (VCFA).

If Harbor is missing, not associated with the Supervisor's region, or if the installation in VCFA is stuck, the Supervisor reconciliation loop will skip the creation of the depot service in the kube-system namespace.

Resolution

To resolve this issue, ensure that Regional Harbor is correctly installed and associated with the Supervisor region.

• Install Regional Harbor: Follow the standard documentation to install Regional Harbor through VCF Automation.
• Verify Association: Ensure the registry is correctly associated with the Supervisor's region in VCFA.
• Validate Installation: Once Harbor is provisioned, the Supervisor reconciliation loop should successfully deploy the Supervisor Services and the internal depot service.