posit-dev / posit-dev/team-operator
support non-hardcoded EKS in-cluster cidr block
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 1
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
A customer brought to our attention that they require all in-cluster (non-routeable) cidr to use 100.64.0.0/16. AWS docs suggest this as a best practice.
I suspect it's really just making the currently hardcoded value configurable, but we should check our network policy to ensure we also haven't hardcoded addrs there.
References:
- https://aws.amazon.com/blogs/containers/addressing-ipv4-address-exhaustion-in-amazon-eks-clusters-using-private-nat-gateways/
- https://docs.aws.amazon.com/vpc/latest/userguide/vpc-cidr-blocks.html
Migrated from rstudio/ptd#2394
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
Start by locating the hardcoded in-cluster CIDR and reviewing the network policy for hardcoded addresses, using the linked AWS documentation for context. Done means the CIDR can be configured for EKS deployments and the network policy does not retain an unintended hardcoded address.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, kubernetes
- Domain
- cloud, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100