-
Notifications
You must be signed in to change notification settings - Fork 38.8k
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
kube-scheduler: allow high ports in secure serving validation #65833
kube-scheduler: allow high ports in secure serving validation #65833
Conversation
/approve |
/lgtm Not only scheduler, kube-apiserver and controller-manager both have the same issue. |
/assign @wojtek-t for approval. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hzxuzhonghu, sttts, wojtek-t 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 |
Automatic merge from submit-queue (batch tested with PRs 65805, 65811, 65833, 65488, 65857). If you want to cherry-pick this change to another branch, please follow the instructions here. |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. controller-managers: allow high ports in secure serving validation Certain operating systems will select high port (>32768) when asked for a free port. This PR changes the validation to allow that. Like #65833, but for controller managers. ```release-note Allow kube- and cloud-controller-manager to listen on ports up to 65535. ```
Certain operating systems will select high port (>32768) when asked for a free port. This PR changes the validation to allow that.