Prerequisites for Dynamic Traffic Controller
This topic describes the prerequisites for installing the Dynamic Traffic Controller in your Kubernetes cluster(s).
Command Tools
The following command line tools are recommended before installing or testing external-dns.
| Package | Description | Installation |
|---|---|---|
| kubectl | Kubernetes CLI | Installing Tools |
| kubectx and kubens | Kubernetes Context Manager | Installing Kubectx |
Infrastructure Requirements
The following are the infrastructure requirements to install ExternalDNS.
Cluster Requirements
| Cluster Requirements | 1 Kubernetes Cluster |
| Supported Kubernetes Versions | 1.19+ |
| Latest Version of ExternalDNS | Avesha-1.12.2+ |
| Kubernetes Metrics Server | Installation |
ExternalDNS
Avesha has extended the Open-Source external-DNS package to support StackPath, Weighted NS1 records, and the ability to create records for the same hostname across multiple Kubernetes clusters. The Dynamic Traffic Controller relies on ExternalDNS to publish and propagate weight changes to your DNS provider.
ExternalDNS should be installed prior to proceeding with installation of the Dynamic Traffic Controller. For more information, see install ExternalDNS.
DNS Provider
To use the full functionality of the Dynamic Traffic Controller you must use NS1 as a DNS provider. This is due to NS1's support for complex filter chains which can be used to influence your DNS responses.
For more about setting up NS1 for use with ExternalDNS and the Dynamic Traffic Controller, see NS1 Setup.