VMware Cloud Foundation

Deploying vSphere Supervisor cluster for VKS with VDS (Foundation load balancer) VCF9.0.1 In this article I will discuss about deploying vSphere supervisor with the option of VDS with Foundation load balancer. If you use vSphere Distributed Switch (VDS) network, you must configure a load balancer to support the network connectivity to workloads from client networks and to load balance traffic between Kubernetes Clusters. The supported load balancer types are Avi Load Balancer, HAProxy and Foundation Load Balancer.VCF 9 introduces VDS ‑ based Supervisor networking with a built ‑ in Foundation LB for lightweight scenarios, reducing moving parts for a lab/POC. I have selected vSphere Distributed Switch (VDS) with the Foundation Load Balancer to minimize footprint while enabling Supervisor control ‑ plane and service VIPs. Overview of Foundation Load Balancer: Foundation LB is designed for baseline Supervisor use cases; it is not a feature ‑ parity replacement for NSX Advanced Load Bal...

Deploying an Offline Depot for VMware Cloud Foundation 9 for Lab Air ‑ gapped and bandwidth ‑ constrained environments need a local source of VCF binaries and metadata. In VCF 9, the Offline Depot lets you host (install + upgrade) required binaries for the VCF Installer (bootstrap) and for post ‑ deployment SDDC Manager/VCF Operations — using a simple HTTP/HTTPS server and a defined directory structure. Deployment methods in VCF9 VMware Cloud Foundation deployments rely on two methods to transfer binaries in the VCF installer one is online depot and other is offline depot. Online depot: It is one of the simplest methods where you configure online deport using Broadcom download token, Installer fetches VCF binaries, metadata and compatibility catalogs directly from portal which requires continuous internet access. Offline Depot: This is the primary method for air ‑ gapped or secure environments. VCF 9 consolidated the workflow to download and serve required components using an offline d...

After replacing the certificate of vCenter with Custom Certificates (which includes certificate(leaf) + sub CA + root CA) then adding compute manager on NSX-T gives error "  Certificate chain of Compute Manager is invalid. Please check Issuer and Subject in the chain.  (Error Code: 90204)"  and sync status between VC and NSX-T manager is down It is because certificate chain is invalid and Certificate chain is being duplicated in the vCenter.  Resolution: Correct the order  you need to follow the following chain              For Machine SSL Certificate Field: It must include  Certificate + subordinate CA + Root CA like this -----BEGIN CERTIFICATE----- MIIFrDCCBJSgAwIBAgITZgAAADAs1zlIBj9VFgABAAAAMDANBgkqhkiG9w0BAQsFADBjMRMwEQYKCZImiZPyLGQBGRYDY29tMRgwFgYKCZImiZPyLGQBGRYIZnB0Y2xvdWQxFjAUBgoJkiaJk/IsZAEZFgZpbnNpZGUxGjAYBgNVBAMTEUZQVENMT1VELVNVQi1DQTAxMB4XDTIxMDIyNDAyNTQyNVoXDTI0MDIyNDAyNTQyNVowKzEpMCcGA1UEAxMgc2duMDltMDF2...