CSE cluster creations fail when the edge gateway used has more than 1 uplink

Products

• VMware Cloud Director

Issue/Introduction

• When creating a new Kubernetes cluster in Container Service Extension(CSE), this error is displayed:

  failed to create load balancer for the cluster [k8sclustername(urn:vcloud:entity:vmware:capvcdCluster:########-####-####-####-############)]: [unable to create load balancer. err [found invalid number of uplinks for gateway [t1-edge-##], expecting 1]

• CSE and VCD was upgraded before the issue happened.

Cloud director from 10.4.2 to 10.5.1.1
CSE from 4.1.1a to 4.2.1
AVI LB from 22.1.3 to 22.1.6

Environment

Cloud Director 10.5.1.1

Container Service Extension 4.2.1 

Cause

Newer version of CSE support IP Spaces and the validation for uplinks on an edge was added. The validation fails if more than 1 uplink exist on the edge used for cluster creation. Any actions taken directly from Cloud Director side doesn't show this issue.

Resolution

This issue is resolved in CAPVCD v1.3.1 and CPI 1.6.1 which have IP Spaces support with multiple uplinks on the edge.
To use these versions during cluster creation set them in the server configuration details as per the CSE documentation, Update Server Configuration.

Alternatively use one of the following workarounds:

Workaround 1: Use an edge which has only one uplink.

Workaround 2: Lower the CPI component version to 1.2.x which does not have the IP Spaces support and hence the issue is not present. Reference documentation here.