Supervisor Exported Config Contains Incorrect Workload CIDR

Products

• VMware vSphere Kubernetes Service

Issue/Introduction

• The deployment succeeds with the expected CIDR value if run through the wizard.
• If you redeploy using the exported JSON config, the configuration will use the incorrect CIDR value.
• The exported file shows a block similar to:
    "nsxVpcNetworkInfo": {
    "nsxVpcProject": "####",
    "nsxVpcConnectivityProfile": "####",
    "workloadServiceCidr": "10.96.0.0/22",
    "nsxVpcPrivateCidrs": [
      "####"
    ]
  }
  
  

 

Environment

vSphere 8.x
VCF 9.x

Cause

This issue is caused by a bug in the vSphere UI/WCP service where the exported configuration does not correctly capture the user-defined Workload Service CIDR values during the Supervisor activation process.

Resolution

This issue is a known defect. A fix is targeted for a future release of VCF 9.x. To be notified when this article is updated with the fix status, please subscribe to the article.

 

Workaround
If you must redeploy using the exported configuration file, manually edit the JSON file before initiation:

1. Open the exported `.json` configuration file in a text editor.
2. Locate the `workloadServiceCidr` field within the `nsxVpcNetworkInfo` block.
3. Change the incorrect value (e.g., `10.96.0.0/22`) to the desired/correct CIDR for your environment.
4. Save the file and proceed with the deployment using the updated configuration.

Alternatively, proceed with the Supervisor deployment via the vSphere Client wizard directly, as the wizard-driven deployment uses the correct values input by the user.