nebari-dev / nebari-dev/nebari-docs
AWS Private Deployment <Pre-liminary annotations>
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 21
- Forks
- 40
- Avg merge
- 19h 50m
- Merged PRs (30d)
- 6
Description
Context
When doing a private implementation subnets and security groups and other might need to be passed (via terraform overrides) down into the deployment implementation, there minimal AWS guidance on how to achieve this.
Value and/or benefit
When using a private network the load balancer deployment of EKS needs to have awareness of what subnets to use:
ingress:
terraform_overrides:
load-balancer-annotations:
service.beta.kubernetes.io/aws-load-balancer-internal: "true"
Reference: https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.2/guide/service/annotations/
Anything else?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the linked custom-overrides-configuration page and locate the deployment-inside-a-virtual-private-network section. Add the AWS private-network guidance and terraform_overrides example shown in the issue, retaining the AWS Load Balancer Controller reference. Done means the page explains the internal load balancer annotation for private EKS deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, terraform
- Domain
- cloud, documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100