Skip to content

Configure DNS for Cluster Failover

This is a guide about how to configure service dns failover between two Kubed clusters.

Steps

  1. Raise a PR in wbx3-application-groups repo: 1. Create a dns-config.yaml if not exists.

    2. Create or update DNS record config in applications/alert/dns.yaml.

    After PR merged, the newly kubed dns config goes following: uas-dns-config-p1

  2. Config global service DNS _acme-challenge CNAME in WCI.

    uas-dns-config-wci

    Warning: CNAME global service DNS will affect traffic routing. You should modify this wisely.

  3. Ask Kubed team to add your global service DNS to the delegated domains in Vault.

  4. Config Kubed Ingress by involving ALL the required DNS. uas-dns-config-ingress

  5. Verify Cerificate. Make sure Subject Alternative Name (SAN) include all required DNS. uas-dns-config-cert

  6. Verify DNS.

    dig xxx.webex.com

    uas-dns-config-dig

Reference

  1. See sample config: wbx3-application-groups/application-groups/monitoring-alerting-service/applications/alert/
  2. Route53 DNS failover.