aws / aws/eks-anywhere

Validate Pod and Service CIDR not conflict with network subnet range used for node machines

Open
#2,086 0 comments 0 reactions 0 assignees View on GitHub
area/cli kind/enhancement team/cli
Dominant language
Go
Stars
2.1k
Forks
328
Avg merge
1d 4h
Merged PRs (30d)
9

Description

CIDR block for services and pods should not conflict with the network subnet range selected for the machines (control plane endpoint).

**What would you like to be added**:

Add a preflight validation to verify cluster pod/service CIDR.

**Why is this needed**:

Contributor guide

Open the contributing guide

Research direction

The issue names no files or tests. Locate the cluster preflight validation entry point and inspect how pod and service CIDRs and the node-machine network range are represented; done means validation rejects conflicting ranges before cluster creation.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
infrastructure, networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.