-
Notifications
You must be signed in to change notification settings - Fork 29
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
Kubernetes: can't be started #310
Comments
Actually, as I learned now, kubeadm doesn't need a running So everything is fine, just a bit different to how it behaved in the past (starting kubelet used to work). |
pohly
added a commit
to intel/pmem-csi
that referenced
this issue
Dec 3, 2018
Starting kubelet before kubeadm isn't necessary and while it worked in the past, it no longer does with Clear Linux 26630 / Kubernetes 1.12 (/var/lib/kubelet/config.yaml not found, clearlinux/distribution#310).
avalluri
pushed a commit
to intel/oim
that referenced
this issue
Jan 30, 2019
Starting kubelet before kubeadm isn't necessary and while it worked in the past, it no longer does with Clear Linux 26630 / Kubernetes 1.12 (/var/lib/kubelet/config.yaml not found, clearlinux/distribution#310).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On Clear Linux 26600, the kubelet service fails to start:
That's on a KVM virtual machine, with containers-basic and cloud-native-basic installed.
kubeadm
was not called because that depends on a runningkubelet
.The text was updated successfully, but these errors were encountered: