-
Notifications
You must be signed in to change notification settings - Fork 713
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
kubeadm v1.13 ignores --kubeconfig-dir on phases #1306
Comments
Hi @tommyknows can you post the output of |
/kind bug |
Well, it's a temp-directory (
I've also tried setting |
@tommyknows I'll send a pr with the fix soon |
@yagonobre: Those labels are not set on the issue: In response to this:
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. |
@yagonobre: Those labels are not set on the issue: In response to this:
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. |
/assign |
Is this a BUG REPORT or FEATURE REQUEST?
BUG REPORT (?)
Versions
kubeadm version (use
kubeadm version
):What happened?
I'm writing a script to automate kubernetes deployments with kubeadm. Up until now, I have used the following command to do all the steps regarding bootstrap-tokens on a remote server:
With kubeadm v1.13, this does not work anymore - there's no
--kubeconfig
flag anymore.I'm now trying to use
This does not work:
I have removed the
--config
flag (as this may not be relevant in my case), and set$kubeconfig_dir
to a path that contains theadmin.conf
file or giving the path to a valid kubeconfig file directly into this variable.However, I am always getting the following output:
What you expected to happen?
I expect kubeadm to either read from the kubeconfig-file (supplied by
--kubeconfig-dir
), or search the--kubeconfig-dir
for aadmin.conf
file.How to reproduce it (as minimally and precisely as possible)?
admin.conf
) to some pathThe text was updated successfully, but these errors were encountered: