FAQ:DNS for feature environments (#449)

* add FAQ:DNS for feature environments * update dns feature environments FAQ * Update dns-feature-environments.md Co-authored-by: Erik Osterman <[email protected]>
cloudposse · Jan 13, 2020 · 2800fb6 · 2800fb6
1 parent 17e28db
commit 2800fb6
Showing 1 changed file with 23 additions and 0 deletions.
diff --git a/content/faq/dns-feature-environments.md b/content/faq/dns-feature-environments.md
@@ -0,0 +1,23 @@
+---
+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
+- unlimited-staging
+- external-dns
+- route53
+- AWS
+- ingress
+- service
+---
+
+## Question
+
+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. 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.