Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ:DNS for feature environments #449

Merged
merged 3 commits into from
Jan 13, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions content/faq/dns-feature-environments.md
Original file line number Diff line number Diff line change
@@ -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.