Deploy a service foundation via Hub fails with a failed to resolve, type:WildcardDomainVerifier
search cancel

Deploy a service foundation via Hub fails with a failed to resolve, type:WildcardDomainVerifier

book

Article ID: 429342

calendar_today

Updated On:

Products

VMware Tanzu Platform - Hub

Issue/Introduction

Foundation Core deploys successfully. However, applying the service foundation capability fails with a failed to resolve, type:WildcardDomainVerifier . I didn't see anywhere in the steps where I can set the certificate. What did I miss? 

 

Environment

HUB 

Cause

WildcardDomainVerifier is a standard error when it tries to validate the FQDN for the domain specified in the EAR tile config.

Resolution

EAR for VMs gives each app its own hostname in your app domain.

With a wildcard DNS record, every hostname in your domain resolves to the IP address of your Gorouter or load balancer, and you do not have to configure an A record for each app hostname. For example, if you create a DNS record *.example.com pointing to your load balancer or Gorouter, every app deployed to the example.com domain resolves to the IP address of your Gorouter.

At least one wildcard TLS certificate that matches the DNS record you set up, *.example.com.

In case of Hub 

System Generates the Self Signed Certificate and assigns it to EAR
Currently only DVSwitch-backed port groups are supportd which mean IPs needs to be routable. (There is no LB for Go Router)
IP which we specify for Go Router should have a DNS with wildcard *.example.com