We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm using kubeadm on system where /etc is mounted read-only, and it was non-trivial to set alternative config path.
kubeadm
/etc
Namely, I had to do this:
env KUBE_KUBERNETES_DIR=/var/lib/kubeadm kubeadm init --skip-preflight-checks --kubernetes-version v1.6.1 --cert-dir /var/lib/kubeadm/pki
It should be just one argument. The main question is – why do we have separate --cert-dir flag?
--cert-dir
There other good reasons why someone may wish to configure alternative path for configuration.
The text was updated successfully, but these errors were encountered:
spxtr/kubernetes@efa8c5e
Successfully merging a pull request may close this issue.
I'm using
kubeadm
on system where/etc
is mounted read-only, and it was non-trivial to set alternative config path.Namely, I had to do this:
It should be just one argument. The main question is – why do we have separate
--cert-dir
flag?There other good reasons why someone may wish to configure alternative path for configuration.
The text was updated successfully, but these errors were encountered: