-
Notifications
You must be signed in to change notification settings - Fork 237
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
change apipa network gw address from .1 to .2 #2933
base: master
Are you sure you want to change the base?
Conversation
what's the impact of this change? is it backwards compatible? |
thanks for adding this context. what happens if this change goes out to a node where containers are already running with the old .1 address? |
This change only applies on new created apipa network/endpoints. It does not impact existed containers unless recreate them. @ashvindeodhar |
@ZetaoZhuang did we test this with existing clusters with old cns and new cni, with all combinations? |
This pull request is stale because it has been open for 2 weeks with no activity. Remove stale label or comment or this will be closed in 7 days |
Pull request closed due to inactivity. |
Reason for Change:
currently cns using the same ip address "169.254.128.1" for both apipa gw and loopback adapter. This cause conflict issue when hns get restarted and not able to rehydrate the apipa endpoints. our long-term goal is to make this gw address configurable in dnc. But for a short-term fix, in cns, we want to overwrite the address to 169.254.128.2, so customer can recreate apipa endpoints by restarting the cns.
Issue Fixed:
Requirements:
Notes: