-
Notifications
You must be signed in to change notification settings - Fork 301
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
Use namer.L4Firewall and namer.L4Backend instead of servicePort #1821
Use namer.L4Firewall and namer.L4Backend instead of servicePort #1821
Conversation
|
||
name := l4netlb.ServicePort.BackendName() | ||
bsName := l4netlb.namer.L4Backend(l4netlb.Service.Namespace, l4netlb.Service.Name) |
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.
Is ServicePort
used after this refactoring? If not maybe you should delete it.
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.
Thank you, good catch, done,
but it needed to move a bit of logic upper to l4netlbcontroller, so now it's also changed
f97c236
to
0d15938
Compare
0d15938
to
221d825
Compare
/assign cezarygerard |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kl52752, panslava The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
It is better to have single source of naming, which is L4Namer in l4netlb
This PR changes getting Backend Service name and Firewall name with using namer, instead of ServicePort
This PR also helps to add DualStack implementation
/assign @kl52752