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
Restore IPAllocator ipv4 range handling #86534
Conversation
/sig network |
/priority critical-urgent |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt 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 |
/hold for network review |
LGTM, thanks. as part of #83422: https://github.com/kubernetes/kubernetes/pull/83422/files#diff-8901e0d89ec6745ac599b98964928090R388 are not very problematic as the clamped results only compare to the constant i will log an issue in k/kubeadm for that. |
Yeah, I swept the other uses and they looked to be done only for validation against much smaller ranges |
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.
/lgtm
/hold cancel |
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
…4-upstream-release-1.17 [v1.17.1] Automated cherry pick of #86534: Revert "remove ipallocator in favor of k/utils net
What type of PR is this?
/kind bug
What this PR does / why we need it:
Reverts the IP allocator portions of #83422, adds unit test covering #86497 scenario
Which issue(s) this PR fixes:
Fixes #86497
Does this PR introduce a user-facing change?: