VMware Cloud Director Container Service Extension Best Practices

This section details the best practices to follow when you use VMware Cloud Director Container Service Extension 4.0 and newer versions.

Service Providers Best Practices

• Ensure that the VMware Cloud Director Container Service Extension server that resides in the solution organization can reach VMware Cloud Director load balancer endpoint.
• VMware NSX^® and VMware NSX^® Advanced Load Balancer™ configuration
  • Use the reference architecture to configure NSX and NSX Advanced Load Balancer correctly.
  • Deploy a test virtual service in a tenant organization to test the NSX and NSX Advanced Load Balancer configuration before you allow tenant users to begin cluster creation.
  • Ensure MTU (9000) values are correctly set on NSX, VMware ESX^® VMkernel, adapters, and NSX Advanced Load Balancer.
  • Ensure MTU (9000) configuration is set correctly for the VMware Cloud Director Container Service Extension server to communicate to VMware Cloud Director load balancer endpoint. For more information, see https://kb.vmware.com/s/article/90850?lang=en_US&queryTerm=90850.
  • Ensure enough NSX Advanced Load Balancer licenses are available.
• Log into the VMware Cloud Director Container Service Extension server, and use one of the following commands to check the server status: systemctl status cse.service or cse.log. This action verifies that the VMware Cloud Director Container Service Extension server has successfully started.
• Input Github personal access token to avoid github API rate limit errors during cluster creation. If you do not perform this action, cluster creation fails, particularly in concurrent attempts. It is not necessary for service providers to input a Github personal access token in the case of airgapped environments.
• If VMware Cloud Director has a multi-VC setup, ensure the Tanzu Kubernetes Grid OVA catalog syncs across VCs so that latency is not problematic during cluster operations.