Block changing nonMasqueradeCIDR
Open
lifecycle/frozen
lifecycle/rotten
P0
- Dominant language
- Go
- Stars
- 16.7k
- Forks
- 4.7k
- Avg merge
- 17h 21m
- Merged PRs (30d)
- 68
Description
It does not end well, because service IPs are out-of-range and cannot be changed.
We should either come up with a way to rejig the service IPs, or just prohibit this validation entirely.
Contributor guide
Research direction
Start by tracing the nonMasqueradeCIDR validation and how service IPs are assigned or changed. Determine whether the project can safely rejig existing service IPs or must prohibit the validation, then define tests for the chosen behavior and verify that changing nonMasqueradeCIDR no longer leaves service IPs out of range.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100