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

FAQ:DNS for feature environments #449

merged 3 commits into from
Jan 13, 2020

Conversation

drnickiw
Copy link
Contributor

what

  • DNS for feature/PR environments FAQ

why

  • Imported from Google Doc

Links to #353

@@ -0,0 +1,18 @@
---
title: "How will DNS be managed?"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
title: "How will DNS be managed?"
title: "How is DNS managed for short-lived environments?"

@@ -0,0 +1,18 @@
---
title: "How will DNS be managed?"
description: "The external-dns controller manages the DNS for PRs."
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
description: "The external-dns controller manages the DNS for PRs."
description: "The `external-dns` controller automatically setups DNS records for these environments."

tags:
- DNS
- feature environments
- PRs
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- PRs
- unlimited-staging


## Question

How will DNS be managed for feature/PR environments?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

Copy link
Member

@osterman osterman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comments

@osterman osterman merged commit 2800fb6 into master Jan 13, 2020
@osterman osterman deleted the DNS-feature-environments branch January 13, 2020 00:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants