Checklist:
Tanzu Application Platform (TAP) - DNS and Ingress (wildcards and A-records) FAQ
To help make TAP installation and configuration experience as simple as possible, R&D team compiled a list of most frequently asked questions.
1. Make sure to review the TAP prerequisites section on
DNS records.
2. Why is my workload defaulting to "example.com"?
"example.com" is the default domain with knative-serving.
3. How do I customize the domain name of my workloads?
Workload domain name is specified in the "cnrs.domain_name" key of tap-values.yml
# tap-values.yml (snippet)
cnrs:
domain_name: mydomain.com
4. How do I setup DNS for my workload?
Grab external IP address of the tanzu-system-ingress's envoy service with
$ kubectl get svc envoy -n tanzu-system-ingress -o jsonpath='{.status.loadBalancer.ingress[*].ip}’
Add a wildcard DNS entry (e.g. *.mydomain.com) that points to the external IP