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.

Sign up for GitHub

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

Jump to bottom

Create internal domain for private resources #137

Open
bmonkman opened this issue Oct 9, 2020 · 0 comments
Open

Create internal domain for private resources #137

bmonkman opened this issue Oct 9, 2020 · 0 comments
Labels
AWS Related to AWS infra enhancement New feature or request kubernetes terraform

Comments

@bmonkman
Copy link
Contributor

bmonkman commented Oct 9, 2020

There's a need in some cases to refer to internal resources by user friendly names. For example, kibana and grafana.
In this case we should have a private route53 zone with an internal domain where we can create records to point to things that are local to the network, and an ingress controller to be able to route internal traffic to things inside the EKS cluster.
The downside of this is that it will be an extra $20/month for another ELB. So maybe we just make it optional?
@bmonkman bmonkman added AWS Related to AWS infra enhancement New feature or request kubernetes terraform labels Oct 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
AWS Related to AWS infra enhancement New feature or request kubernetes terraform
Projects
Zero - Full project view
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bmonkman