Skip to content

Latest commit

 

History

History
22 lines (18 loc) · 1.72 KB

readme.md

File metadata and controls

22 lines (18 loc) · 1.72 KB
Raw

kubeCDN: ExternalDNS Setup

Follow instructions below to setup and test ExternalDNS. Make sure to add IAM role as described in the References section before following steps below. Also, read the limitations of ExternalDNS here.

  1. Update --domain-filter argument in externaldns.yaml and then run:
./install-externaldns.sh
  1. If you would like to deploy an Nginx webserver as a test service, update annotations in testservice.yaml and run:
./test-deploy.sh
  1. Route 53 should have an updated DNS record for the service deployed above.

Limitations:

Following are some limitations with ExternalDNS at the time of writing:

  • ExternalDNS is not currently capable of setting routing policies as per this. Due to this limitation, latency based routing will have to be manually set on AWS Console.
  • When deploying to multiple regions, note that only one region will have an A record set on Route53. It seems that ExternalDNS cannot set multiple records of the same type (multiple A records with different aliases). This limitation was overcome by manually setting A records using AWS console. This issue will need to be revisited in the future. Refer to this for more info.

References:

  • Here is a guide that walks through how to setup ExternalDNS with AWS. Specifically, use this guide to setup the correct IAM permissions on your account.
  • Another helpful guide to setup ExternalDNS with AWS EKS.