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.

Tenant Administrators Best Practices

• Ensure OVDC networks and gateways are set up correctly
  • To allow OVDCs to host clusters, it is necessary they have routed networks.
  • Use static IP ranges for the VMs. Do not use dynamic host configuration protocol (DHCP).
  • Ensure the DNS configuration is correctly configured on an OVDC network.
  • Ensure the source network address translation (SNAT) rule is set on the gateway to ensure outbound traffic for the organization network classless inter-domain routing (CIDR).
  • Ensure firewall rules do not prevent access to VMware Cloud Director endpoint, Network Time Protocol (NTP) servers, and DNS server IPs.
• Create a test virtual service on the tenant gateway to test the test the VMware NSX^® and VMware NSX^® Advanced Load Balancer™ configuration before letting tenant users begin cluster creation.
• Do not use NSX direct organization networks for cluster creations as it is not a supported configuration. NSX Advanced Load Balancer does not work with direct networks. As a result, you cannot create clusters with load balancers.
• If you want the nodes to be a different disk size than the template OVAs, that have a default disk size of 20GB, deactivate fast provisioning in organization virtual data center (OVDC).

Tenant Users Best Practices

• If you attempt to create clusters for the first time, or are learning how to use VMware Cloud Director Container Service Extension, deactivate Autorepair on Errors in the cluster creation workflow. This helps to troubleshoot, and properly capture the logs from the Bootstrap VM.
• Certain actions that you perform, such as resizing a cluster, may not appear in the Nodepools tab in the UI immediately. However, you can view the latest status in the the Events tab in the Cluster Information page.
• When you delete and force delete clusters in the Kubernetes Container Clusters UI, there may be a delay in the actions taking effect. However, you can view the latest status in the the Events tab in the Cluster Information page.