Configure DNS records

Create a subdomain to house Privacy Dynamics

Installation best practice is to partition off Privacy Dynamics into a subdomain, keeping everything separate from the rest the customer's infrastructure. It is better to create a subdomain pvcy.customer.com dedicated to hosting Privacy Dynamics endpoints so that there is no unintended interference from external-dns to other Route 53 records.

The example domain customer.com is used throughout the documentation and is intended to represent the customer's domain name. The customer's domain should be used wherever customer.com is present in code samples.

Create DNS zone

Each service within Privacy Dynamics will have its own DNS record. The web-based UI should be app.pvcy.customer.com and the API should be api.pvcy.customer.com. DNS A records for app and api will be automatically created in a later step when service ingresses are added.

Install ExternalDNS

ExternalDNS is an optional component that can automatically create DNS records for ingresses on your cluster. You can also create DNS records manually if you prefer.

ExternalDNS can be installed automatically onto the cluster using the KOTS Admin Console by selecting "Install ExternalDNS" under "Auxiliary Software" (see Install Privacy Dynamics).

Alternatively, you can install the Helm chart directly to take advantage of all configuration options. For more information, see the official ExternalDNS documentation.