-
Notifications
You must be signed in to change notification settings - Fork 724
fix: Fix panic in descheduler when using --secure-port=0
#1647
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
base: master
Are you sure you want to change the base?
fix: Fix panic in descheduler when using --secure-port=0
#1647
Conversation
Signed-off-by: dongjiang <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
Hi @dongjiang1989. Thanks for your PR. I'm waiting for a kubernetes-sigs 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. |
@dongjiang1989: GitHub didn't allow me to request PR reviews from the following users: PTAL. Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this: 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. |
/cc |
/ok-to-test |
/retest |
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.
I have a concern about this argument, its help reads:
The port on which to serve HTTPS with authentication and authorization. If 0, don't serve HTTPS at all. (default 10258)
I don't think we implement authentication and authorization.
Thanks @ricardomaraschini Hmmm.... Or we can override this |
You are probably right. Those flags seem to come out directly from a different project and have been reused here. This may be orthogonal to what we are trying to solve here but I would like us to evaluate all the flags and try to consolidate what is really applicable here. This one solves the panic and that is good. |
Thanks @ricardomaraschini |
Needs #1675 |
Fix panic in descheduler when using
--secure-port=0
:Fixed:
Close #1639