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
{{ message }}
This repository has been archived by the owner on Jul 28, 2019. It is now read-only.
When I run the gce-setup.sh script on the latest Kubernetes master, I see this error:
W0215 20:40:49.242] [init] Waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests".
W0215 20:40:49.243] [init] This might take a minute or longer if the control plane images have to be pulled.
W0215 20:41:29.243] [kubelet-check] It seems like the kubelet isn't running or healthy.
W0215 20:41:29.243] [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10255/healthz' failed with error: Get http://localhost:10255/healthz: dial tcp [::1]:10255: getsockopt: connection refused.
When I look at the kubelet journalctl log, I see this error:
The cause of this error seems to be this commit in kubernetes/kubernetes, which eliminated the deprecated "--require-kubeconfig" flag from kubelet configuration: kubernetes/kubernetes#58367
Seems to me that this setting in k-d-c/image/kubelet.service needs this change for latest Kubernetes (although this would need to be a kubernetes-version-dependent change):
Looks like we also need to have this flag '--fail-swap-on=false' as the defaut value of this flag has changed on Jan 2nd. Formery, the default falue was 'false', it is now 'true'.
When I run the gce-setup.sh script on the latest Kubernetes master, I see this error:
When I look at the kubelet journalctl log, I see this error:
The cause of this error seems to be this commit in kubernetes/kubernetes, which eliminated the deprecated "--require-kubeconfig" flag from kubelet configuration:
kubernetes/kubernetes#58367
Seems to me that this setting in k-d-c/image/kubelet.service needs this change for latest Kubernetes (although this would need to be a kubernetes-version-dependent change):
One quick workaround is to back up to the version of Kubernetes right before the commit of k8s PR #58367, e.g.:
The text was updated successfully, but these errors were encountered: