-
Notifications
You must be signed in to change notification settings - Fork 39.7k
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
Use kubeconfig flag instead of kubeconfig-dir in kubeadm init phase bootstrap-token #71803
Conversation
/cc @kubernetes/sig-cluster-lifecycle-pr-reviews |
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.
thanks for the quick fix @yagonobre
/lgtm
/approve
/priority critical-urgent
/assign @fabriziopandini
should we cherry pick?
+1 from me to cherry pick |
/test pull-kubernetes-e2e-kops-aws |
/hold |
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.
/hold cancel
/lgtm
/approve
Please cherry-pick and assign to me.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: neolit123, timothysc, yagonobre 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 |
/test pull-kubernetes-e2e-kops-aws |
…803-upstream-release-1.13 Automated cherry pick of #71803: Use kubeconfig flag instead of kubeconfig-dir in kubeadm init
What type of PR is this?
/kind bug
What this PR does / why we need it:
Fixes kubernetes/kubeadm#1306
Special notes for your reviewer:
bootstrap-token is the unique phase that use
data.Client()
andkubeconfig-dir
flag, that make sense only in thekubeconfig
phaseDoes this PR introduce a user-facing change?:
-->