Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ConfigMap for protected IPs/subnets #11

Open
v-ctiutiu opened this issue Sep 14, 2022 · 0 comments
Open

ConfigMap for protected IPs/subnets #11

v-ctiutiu opened this issue Sep 14, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@v-ctiutiu
Copy link
Contributor

Background

It's very easy to overlap with other IP ranges defined in the routing table which should not be touched, such as CNI routes (DOKS uses Cilium). Another case would be to avoid egressing the public CIDRs used by DigitalOcean services (i.e. DOKS), which leads to instability.

Proposal

Controller should be aware of the protected subnets/IPs via a ConfigMap which can be updated afterwards based on requirements. Controller logic should read the config whenever it changes.

@v-ctiutiu v-ctiutiu self-assigned this Sep 14, 2022
@v-ctiutiu v-ctiutiu added the enhancement New feature or request label Sep 14, 2022
@v-ctiutiu v-ctiutiu removed their assignment Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant