Use kubeconfig flag instead of kubeconfig-dir in kubeadm init phase bootstrap-token#71803
Conversation
|
/cc @kubernetes/sig-cluster-lifecycle-pr-reviews |
neolit123
left a comment
There was a problem hiding this comment.
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 |
timothysc
left a comment
There was a problem hiding this comment.
/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 DetailsNeeds 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-dirflag, that make sense only in thekubeconfigphaseDoes this PR introduce a user-facing change?:
-->