VCF component deployment fails during the Identity Broker (VIDB) installation phase

Products

• VMware Cloud Foundation

Issue/Introduction

The VCF 9.1 installation go smoothly until the stage of "Deploy and configure VCF Management Services", and it failed on the step 7: "Install identity broker using Fleet Lifecycle"

Deployment logs identified a failure in the Helm release for the `vidb-external/vidb` chart, for example:

kubectl describe helmreleases vidb -n vidb-external

"Helm install failed for release vidb-external/vidb with chart [email protected]: 3 errors occurred:\n\t* admission webhook \"vgatewayconfiguration.kb.io\" denied the request: GatewayConfiguration.networking.vmsp.vmware.com \"vidb-service-gateway\" is invalid: spec.hostnames[0]: Invalid value: \"xxx\": invalid hostname: [a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')]\n\t*

Environment

VMware Cloud Foundation 9.1

Resolution

1.  Clean up the current failed deployment state to ensure no stale metadata remains.
2.  Update DNS records to ensure all component FQDNs use exclusively lowercase letters.
3.  Re-run the deployment and ensure the FQDN entered in the configuration interface.
4.  Proceed with the environment redeployment using the corrected lowercase naming convention.