-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
Make kube-proxy ipset parameters 'hashSize' 'maxElem' customizable #129390
base: master
Are you sure you want to change the base?
Make kube-proxy ipset parameters 'hashSize' 'maxElem' customizable #129390
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
Welcome @weak-fox! |
Hi @weak-fox. 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-sigs/prow repository. |
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
/ok-to-test |
/cc @uablrek |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: weak-fox 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 |
1. Change `MaxElem` to `MaxElements` 2. Change `IPVSIPSetConfiguration` to `KubeProxyIPSetConfiguration`; 3. Resolved inconsistent variable names in comments
f2a1b40
to
d98c544
Compare
/retest-required |
What type of PR is this?
/kind feature
/kind api-change
What this PR does / why we need it:
This PR allows IPSet hashSize, maxElem to be configurable via kube-proxy flags/config.
The following flags are being added:
The default value comes from the previous code:
kubernetes/pkg/proxy/ipvs/ipset/ipset.go
Lines 130 to 149 in 35f5841
Which issue(s) this PR fixes:
Fixes #129389
Special notes for your reviewer:
The PR introduces new API fields in the v1alpha1 API group for kube-proxy configuration. The changes are backward compatible as default values are provided.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: