From 53c165db8169c9d017fa987c09a7288fb0cc7c5e Mon Sep 17 00:00:00 2001 From: Nicki Washington Date: Wed, 27 Mar 2019 21:54:46 -0400 Subject: [PATCH 1/3] add FAQ:DNS for feature environments --- content/faq/dns-feature-environments.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 content/faq/dns-feature-environments.md diff --git a/content/faq/dns-feature-environments.md b/content/faq/dns-feature-environments.md new file mode 100644 index 000000000..721b8bc11 --- /dev/null +++ b/content/faq/dns-feature-environments.md @@ -0,0 +1,18 @@ +--- +title: "How will DNS be managed?" +description: "The external-dns controller manages the DNS for PRs." +tags: +- DNS +- feature environments +- PRs +- AWS +--- + +## Question + +How will DNS be managed for feature/PR environments? + + +## Answer + +The `external-dns` controller manages the DNS for PRs. It supports AWS and GKE environments. Wildcard DNS is sometimes used instead. That’s also cool, but less dynamic. From e477531acc9cc4608d9a2090b5a6057cb66fc6e2 Mon Sep 17 00:00:00 2001 From: Nicki Washington Date: Thu, 25 Apr 2019 23:16:42 -0400 Subject: [PATCH 2/3] update dns feature environments FAQ --- content/faq/dns-feature-environments.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/content/faq/dns-feature-environments.md b/content/faq/dns-feature-environments.md index 721b8bc11..1c9edb941 100644 --- a/content/faq/dns-feature-environments.md +++ b/content/faq/dns-feature-environments.md @@ -1,18 +1,17 @@ --- -title: "How will DNS be managed?" -description: "The external-dns controller manages the DNS for PRs." +title: "How is DNS managed for short-lived environments?" +description: "The `external-dns` controller automatically setups DNS records for these environments." tags: - DNS - feature environments -- PRs +- unlimited-staging - AWS --- ## Question -How will DNS be managed for feature/PR environments? - +How will DNS be managed for short-lived environments (e.g. for feature branches and Pull Requests)? ## Answer -The `external-dns` controller manages the DNS for PRs. It supports AWS and GKE environments. Wildcard DNS is sometimes used instead. That’s also cool, but less dynamic. +The `external-dns` controller manages the DNS for PRs. It supports AWS and GKE environments. Wildcard DNS records pointed at the Ingress Load Balancer can be used in place of `external-dns`, but that is less flexible. From e7b22f8eef869ba45d088df6e2619dd6c7f8733a Mon Sep 17 00:00:00 2001 From: Erik Osterman Date: Sun, 12 Jan 2020 16:08:54 -0800 Subject: [PATCH 3/3] Update dns-feature-environments.md --- content/faq/dns-feature-environments.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/content/faq/dns-feature-environments.md b/content/faq/dns-feature-environments.md index 1c9edb941..22a59890b 100644 --- a/content/faq/dns-feature-environments.md +++ b/content/faq/dns-feature-environments.md @@ -5,7 +5,11 @@ tags: - DNS - feature environments - unlimited-staging +- external-dns +- route53 - AWS +- ingress +- service --- ## Question @@ -14,4 +18,6 @@ How will DNS be managed for short-lived environments (e.g. for feature branches ## Answer -The `external-dns` controller manages the DNS for PRs. It supports AWS and GKE environments. Wildcard DNS records pointed at the Ingress Load Balancer can be used in place of `external-dns`, but that is less flexible. +The `external-dns` controller manages the DNS for PRs. All we need to do is add an annotation to the `Ingress` or `Service` with the desired hostname and then the controller takes care of the rest. It supports AWS, GKE, Cloudflare, Digital Ocean, and Azure environments. + +Alternatlive, wildcard DNS records pointed at the Ingress Load Balancer. This may be used in place of `external-dns`, but that is less flexible because it only supports a flat hostname structure for a single domain.