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.

Sign up for GitHub

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

Jump to bottom

Reserved an statically port range for nodeport #114129

Closed
xuzhenglun opened this issue Nov 25, 2022 · 4 comments · Fixed by #114418
Closed

Reserved an statically port range for nodeport #114129

xuzhenglun opened this issue Nov 25, 2022 · 4 comments · Fixed by #114418
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

@xuzhenglun
Copy link
Contributor

xuzhenglun commented Nov 25, 2022 •
edited
Loading

What would you like to be added?

just like KEP-3070 did, I want to reserve some port for nodeport. I can try to submit an KEP if it sound good for sig/network.

Why is this needed?

In our cluster, some applications are NOT deployed in Kubernetes. But they need to connect to service in Kubernetes too.

For example, some applications need to connect to the minio service but they have no idea what cluster-ip it is. In our situation, those applications just connect to a specific port (30009) of the Kubernetes master node.

This situation works most time, but in something 30009 is allocated by something else. And minio service will be failed to applied.
@xuzhenglun xuzhenglun added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 25, 2022
@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 Nov 25, 2022
@k8s-ci-robot
Copy link
Contributor

@xuzhenglun: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@xuzhenglun
Copy link
Contributor Author

/sig network

@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 Nov 25, 2022
@aojea
Copy link
Member

aojea commented Nov 26, 2022

I don't see why not, WDYT @thockin ?

@xuzhenglun xuzhenglun mentioned this issue Nov 28, 2022
Closed
16 tasks
@thockin
Copy link
Member

thockin commented Dec 8, 2022

I told you it would follow :)

@thockin thockin 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 8, 2022
This was referenced Dec 10, 2022
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Reserve Nodeport Ranges For Dynamic And Static Port Allocation xuzhenglun/kubernetes
4 participants
@xuzhenglun @thockin @aojea @k8s-ci-robot