You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to bootstrap a Container Linux (CoreOS) cluster with kubeadm-installer, thanks for all the good work!
My node's kubelet is failing to start looking for a kubelet.conf file that does not exist on the system. I don't see one generated by the installer, is this a change in kubeadm setup? Should I be providing one for the system?
Logs:
Jan 21 14:23:07 core-01-node systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 1.
Jan 21 14:23:07 core-01-node systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Jan 21 14:23:07 core-01-node systemd[1]: Started kubelet: The Kubernetes Node Agent.
Jan 21 14:23:07 core-01-node kubelet-wrapper[1936]: KUBELET_VERSION environment variable is deprecated, please use KUBELET_IMAGE_TAG instead
Jan 21 14:23:07 core-01-node kubelet-wrapper[1936]: + exec /usr/bin/rkt run --volume opt-cni,kind=host,source=/opt/cni --mount volume=opt-cni,target=/opt/cni --volume etc-cni,kind=host,source=/etc/cni --mount volume=etc-cni,target=/etc/cni
Jan 21 14:23:08 core-01-node kubelet-wrapper[1936]: Flag --require-kubeconfig has been deprecated, You no longer need to use --require-kubeconfig. This will be removed in a future version. Providing --kubeconfig enables API server mode, om
Jan 21 14:23:08 core-01-node kubelet-wrapper[1936]: I0121 14:23:08.812095 1936 server.go:182] Version: v1.9.2+coreos.0
Jan 21 14:23:08 core-01-node kubelet-wrapper[1936]: I0121 14:23:08.812326 1936 feature_gate.go:220] feature gates: &{{} map[]}
Jan 21 14:23:08 core-01-node kubelet-wrapper[1936]: W0121 14:23:08.812621 1936 server.go:280] --require-kubeconfig is deprecated. Set --kubeconfig without using --require-kubeconfig.
Jan 21 14:23:08 core-01-node kubelet-wrapper[1936]: W0121 14:23:08.812979 1936 cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d
Jan 21 14:23:08 core-01-node kubelet-wrapper[1936]: I0121 14:23:08.835305 1936 plugins.go:101] No cloud provider specified.
Jan 21 14:23:08 core-01-node kubelet-wrapper[1936]: Error: failed to run Kubelet: invalid kubeconfig: stat /etc/kubernetes/kubelet.conf: no such file or directory
Trying to bootstrap a Container Linux (CoreOS) cluster with kubeadm-installer, thanks for all the good work!
My node's kubelet is failing to start looking for a kubelet.conf file that does not exist on the system. I don't see one generated by the installer, is this a change in kubeadm setup? Should I be providing one for the system?
Logs:
kubelet.service file:
CoreOS v 1662.0.0
I'm pulling the 'latest' tag on the kubeadm-installer
@xakraz
The text was updated successfully, but these errors were encountered: