-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
kubeadm: relax the validation of kubeconfig server URLs #94816
kubeadm: relax the validation of kubeconfig server URLs #94816
Conversation
For external CA users that have prepared the kubeconfig files for components, they might wish to provide a custom API server URL. When performing validation on these kubeconfig files, instead of erroring out on such custom URLs, show a klog Warning. This allows flexibility around topology setup, where users wish to make the kubeconfigs point to the ControlPlaneEndpoint instead of the LocalAPIEndpoint. Fix validation in ValidateKubeconfigsForExternalCA expecting all kubeconfig files to use the CPE. The kube-scheduler and kube-controller-manager now use LAE.
/kind regression |
/hold |
should be backported to 1.19 where this was regressed, even if there are workarounds. |
flake:
/retest |
xref #94567 |
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.
@neolit123 thanks for this PR!
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini, neolit123 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 |
/hold cancel |
/milestone v1.20 |
…816-origin-release-1.19 Automated cherry pick of #94816: kubeadm: relax the validation of kubeconfig server URLs
What this PR does / why we need it:
For external CA users that have prepared the kubeconfig files
for components, they might wish to provide a custom API server URL.
When performing validation on these kubeconfig files, instead of
erroring out on such custom URLs, show a klog Warning.
This allows flexibility around topology setup, where users
wish to make the kubeconfigs point to the ControlPlaneEndpoint instead
of the LocalAPIEndpoint.
Fix validation in ValidateKubeconfigsForExternalCA expecting
all kubeconfig files to use the CPE. The kube-scheduler and
kube-controller-manager now use LAE.
Which issue(s) this PR fixes:
xref kubernetes/kubeadm#2271
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: