awslabs / awslabs/eks-perf-tests
[operator] service cluster IP range can conflict
Open
0.2
- Dominant language
- Shell
- Stars
- 72
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
Currently the service cluster IP range in KIT cluster is `10.96.0.0/12`, and DNS cluster IP is `10.100.0.10`.
A user might have the same underlying subnet in VPC and it can conflict. At some point we should revisit this and detect the VPC cidr block where cluster is running and select another service cluster IP range like `172.16.0.0/12` and DNS cluster IP to be `172.16.0.10`
Contributor guide
Research direction
No files or tests are named. Start by tracing the operator's service and DNS CIDR configuration and how the cluster's VPC CIDR is obtained; done means selecting a non-conflicting service range and matching DNS cluster IP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, shell
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100