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
pkg/proxy/userspace/roundrobin: Make lb.services
nil check standardized
#108259
pkg/proxy/userspace/roundrobin: Make lb.services
nil check standardized
#108259
Conversation
|
Welcome @carlosdamazio! |
Hi @carlosdamazio. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
lb.services
nil check standardized
/ok-to-test |
/lgtm |
/triage accepted |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: carlosdamazio, dcbw 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 |
/retest |
1 similar comment
/retest |
/retest |
@dcbw could you give lgtm again? Needed to fix the formatting. |
/lgtm |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
As suggested in here, some portions of the code contains the map checking for nil values in
lb.services
map, and others don't have. Even though we're never assigning nil values to this map, we should standardize the portions that does not have this check inroundrobin
module.Example:
Should be like this:
Which issue(s) this PR fixes:
Fixes #108257
Special notes for your reviewer:
NONE
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
NONE