-
Notifications
You must be signed in to change notification settings - Fork 302
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
Update endpoints for NEGs from non-default subnet. #2728
base: master
Are you sure you want to change the base?
Conversation
3e71b31
to
b6db771
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: sawsa307 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
b6db771
to
dbff2f8
Compare
dbff2f8
to
6018b3b
Compare
6018b3b
to
d8cd4bb
Compare
d8cd4bb
to
508a868
Compare
9f71175
to
9c6f6e6
Compare
* Remove NodeTopologyInformer from controller context hasSynced so it won't block controllers from starting up in case of the CRD or CR does not exist.
* Query Node Topology CR for the current set of NEGs in the cluster. * When ensureNetworkEndpointGroups(), ensure NEGs are properly provisioned in the non-default subnets as well.
9c6f6e6
to
4235164
Compare
4235164
to
240449b
Compare
240449b
to
f1880d2
Compare
/assign @gauravkghildiyal