-
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
Mark --kubelet-https deprecated, unconditionally use https for apiserver->kubelet connections #91630
Mark --kubelet-https deprecated, unconditionally use https for apiserver->kubelet connections #91630
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt 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 |
ec0ee00
to
a1cf6ae
Compare
/lgtm |
/retest Review the full test history for this PR. Silence the bot with an |
1 similar comment
/retest Review the full test history for this PR. Silence the bot with an |
…ver->kubelet connections
a1cf6ae
to
2e8461a
Compare
New changes are detected. LGTM label has been removed. |
fixed lint error |
/priority backlog |
/lgtm |
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
1 similar comment
/retest |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Kubelets have unconditionally used https to serve the endpoints the apiserver communicates with since before v1.0 (in #6380), and the apiserver flag to allow switching communication with the kubelet to http has not be usable since then.
This PR marks that flag as deprecated and removes the option for the kube-apiserver -> kubelet connection to switch from https to http.
Does this PR introduce a user-facing change?: