Skip to content
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' and 'maxElem' customizable #129389

Open
weak-fox opened this issue Dec 25, 2024 · 3 comments · May be fixed by #129390
Open

Make kube-proxy ipset parameters 'hashSize' and 'maxElem' customizable #129389

weak-fox opened this issue Dec 25, 2024 · 3 comments · May be fixed by #129390
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/network Categorizes an issue or PR as relevant to SIG Network. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@weak-fox
Copy link

weak-fox commented Dec 25, 2024

What would you like to be added?

Allow users to configure ipset parameters 'hashSize' and 'maxElem' in kube-proxy configuration. These parameters should be customizable via the kube-proxy config file or command line flags.

Why is this needed?

In our use case, we have multiple LAN devices that need to interact with services in the cluster via RTP media streams. Each service can have thousands of ports, and we assign an external IP for each LAN to access these services. This results in the required ipset size reaching "ports num" * "external IP num," which can exceed the default limit of 65536.When the ipset size reaches its limit, any new services added will not take effect.

By making these parameters configurable, users can adjust the size based on their specific needs, providing greater flexibility and adaptability. Additionally, when modifying maxElem, users should also consider adjusting hashSize to achieve optimal performance, allowing them to balance memory usage according to their current scenario.

This feature will enhance kube-proxy's scalability and performance in diverse environments.

There are also many users like us who need to expose a large number of ports:
#23864
#23864 (comment)

@weak-fox weak-fox added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 25, 2024
@k8s-ci-robot k8s-ci-robot added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 25, 2024
@weak-fox
Copy link
Author

@kubernetes/sig-network-feature-requests

@k8s-ci-robot k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Dec 25, 2024
@k8s-ci-robot
Copy link
Contributor

@weak-fox: Reiterating the mentions to trigger a notification:
@kubernetes/sig-network-feature-requests

In response to this:

@kubernetes/sig-network-feature-requests

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.

@aroradaman
Copy link
Member

The request seems reasonable
/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/network Categorizes an issue or PR as relevant to SIG Network. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants