This section describes how to use
external-dns to maintain your DNS records
You require a DNS record when setting up a custom domain for your cluster. You can either create one manually, or set up the
external-dns service to manage your DNS record automatically.
If you choose to use
external-dns to maintain your DNS records, the
external-dns will take care of pointing the DNS record to the ingress of the cluster automatically.
The following example shows how to configure
external-dns to manage DNS records in AWS Route 53 automatically:
If you do not have a
kommander.yamlfile, initialize the configuration file, so you can edit it in the following steps. WARNING: Initialize this file only ONCE, otherwise you will overwrite previous customizations.
If you have initialized the configuration file already, open the
kommander.yamlwith the editor of your choice.
appsection of your
kommander.yamlfile to include these values:
apps: external-dns: enabled: true values: | aws: credentials: secretKey: <secret-key> accessKey: <access-key> region: <provider-region> preferCNAME: true policy: upsert-only txtPrefix: local- domainFilters: - <example.com>CODE
In the same
appsection, adjust the
traefiksection to include the following:
traefik: enabled: true values: | service: annotations: external-dns.alpha.kubernetes.io/hostname: <mycluster.example.com>CODE
Refer to the external-dns documentation for more information, as well as further instructions on how to configure
external-dns to use other DNS providers like Google Cloud DNS, CloudFlare, or on-site providers.