Cluster should provide tooling for automatic creation of DNS resources in a cloud native way.
This test case contains two different ways to manage DNS
- Tanzu Kubernetes Workload Cluster created
- Avi AKO Operator installed
- Avi Controller deployed and configured
- Avi admin access
- Log into the Avi UI as admin
- From the handburger icon in the top-left corner. Select "Administration"
- Select "Settings" from the top level ribbon
- Select "DNS Service" from the secondary ribbon
- Select "+ Add Virtual Service"
- Complete the DNS Service configuration accordingly, taking note of "Application Domain Name" service
- Deply the hello-world application
kubectl apply -f scenarios/devops/hello-world.yaml
- Open the hello-world ingress file and replace
avi-ns1.poc6349.wwtatc.lab
with the value from step 6 - Deploy the ingress manifest for hello-world
kubectl apply -f scenarios/devops/hello-world-ingress.yaml
- Retrieve the newly created ingress resource and wait for an IP Address to be assigned
kubectl get ing -w
- Perform an NSlookup to ensure the host has been added in DNS
note: this may take a couple minutes for DNS to propogate
nslookup helloworld.avi-ns1.poc6349.wwtatc.lab
- [ ] Pass
- [ ] Fail
- Tanzu Kubernetes Workload Cluster deployed
- Cluster-Admin access to k8s cluster
- Supported DNS provider (RFC2136 BIND, Route53, Azure)
- Install the External DNS provider from the Tanzu Extension via the documentation here.
- Deply the hello-world application
kubectl apply -f scenarios/devops/hello-world.yaml
- Validate external DNS using the steps outlined here.
- [ ] Pass
- [ ] Fail