-
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
Extend retrieve current NEG endpoints to also look for NEGs in non-default subnets. #2731
base: master
Are you sure you want to change the base?
Conversation
Thanks! Haven't checked the tests, but besides those, this one is looking relatively straightforward. |
* 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.
824842c
to
ef83a05
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 |
@@ -883,6 +954,18 @@ func (s *transactionSyncer) computeEPSStaleness(endpointSlices []*discovery.Endp | |||
} | |||
} | |||
|
|||
func (s *transactionSyncer) getNonDefaultSubnetName(subnet string) (string, error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this must be able to detect if it's running for L4 or L7 NEG and use the appropriate namer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh I see, we can probably check the NEG type and use the correct namer(namer/l4namer). Both of them are available to NEG controller. Thanks for catching this!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for catching this!
ef83a05
to
5ae30eb
Compare
5ae30eb
to
8847eff
Compare
8847eff
to
2b8e5c7
Compare
/assign @gauravkghildiyal