-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Fix the default KubeletReadOnlyPort value to 0 (disabled) #94551
Conversation
Change-Id: I2b937764b6204a9ccf64446a0e57e7c58bc819e7 Signed-off-by: William Zhang <warmchang@outlook.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: warmchang 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 |
/test pull-kubernetes-node-e2e |
@warmchang: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
changing the constant to an invalid port is incorrect… if we want to disable by default, then we should modify the place where this value is set into the kubelet config |
The CLI documentation is saying to set it to 0 to disable, and that the default is still 10255. |
The default kubelet config value is 0 (disabled):
But the cli documentation said that the default is 10255. |
The CLI default is 10255, so the help is accurate. See https://github.com/kubernetes/kubernetes/blob/master/cmd/kubelet/app/options/options.go#L249-L252 When starting the kubelet from a config file, improved/stricter default values are used. See #59666 |
Got it, I seem to have pushed dominoes. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
"--read-only-port" field description (default 10255) is confusing, fix it.
Before:
After:
Which issue(s) this PR fixes:
Fixes #94550
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: