Skip to content
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.

Sign up for GitHub

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

Jump to bottom

kubelet isn't running or healthy #27

Closed
rm-rf-etc opened this issue Jul 27, 2018 · 4 comments
Closed

kubelet isn't running or healthy #27

rm-rf-etc opened this issue Jul 27, 2018 · 4 comments

Comments

@rm-rf-etc
Copy link
Contributor 

module.kubernetes.null_resource.kubernetes[0] (remote-exec): [kubeconfig] Using existing up-to-date KubeConfig file: "/etc/kubernetes/scheduler.conf"
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [controlplane] wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml"
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [controlplane] wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml"
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [controlplane] wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml"
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [init] waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests"
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [init] this might take a minute or longer if the control plane images have to be pulled
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.1: Still creating... (40s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (40s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (40s elapsed)
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.1: Still creating... (50s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (50s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (50s elapsed)
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.1: Still creating... (1m0s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (1m0s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (1m0s elapsed)
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.1: Still creating... (1m10s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (1m10s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (1m10s elapsed)
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [kubelet-check] It seems like the kubelet isn't running or healthy.
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [kubelet-check] It seems like the kubelet isn't running or healthy.
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
module.kubernetes.null_resource.kubernetes.1: Still creating... (1m20s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (1m20s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (1m20s elapsed)
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [kubelet-check] It seems like the kubelet isn't running or healthy.
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.1: Still creating... (1m30s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (1m30s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (1m30s elapsed)
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.1: Still creating... (1m40s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (1m40s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (1m40s elapsed)
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [kubelet-check] It seems like the kubelet isn't running or healthy.
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
module.kubernetes.null_resource.kubernetes.1: Still creating... (1m50s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (1m50s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (1m50s elapsed)
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.2: Still creating... (2m0s elapsed)
module.kubernetes.null_resource.kubernetes.1: Still creating... (2m0s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (2m0s elapsed)
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.0: Still creating... (2m10s elapsed)
module.kubernetes.null_resource.kubernetes.1: Still creating... (2m10s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (2m10s elapsed)
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.0: Still creating... (2m20s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (2m20s elapsed)
module.kubernetes.null_resource.kubernetes.1: Still creating... (2m20s elapsed)
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [kubelet-check] It seems like the kubelet isn't running or healthy.
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[0] (remote-exec): [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.

module.kubernetes.null_resource.kubernetes[0] (remote-exec): 		Unfortunately, an error has occurred:

module.kubernetes.null_resource.kubernetes[0] (remote-exec): 		timed out waiting for the condition

module.kubernetes.null_resource.kubernetes[0] (remote-exec): 		This error is likely caused by:
module.kubernetes.null_resource.kubernetes[0] (remote-exec): 			- The kubelet is not running
module.kubernetes.null_resource.kubernetes[0] (remote-exec): 			- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
module.kubernetes.null_resource.kubernetes[0] (remote-exec): 			- No internet connection is available so the kubelet cannot pull or find the following control plane images:
module.kubernetes.null_resource.kubernetes[0] (remote-exec): 				- k8s.gcr.io/kube-apiserver-amd64:v1.11.1
module.kubernetes.null_resource.kubernetes[0] (remote-exec): 				- k8s.gcr.io/kube-controller-manager-amd64:v1.11.1
module.kubernetes.null_resource.kubernetes[0] (remote-exec): 				- k8s.gcr.io/kube-scheduler-amd64:v1.11.1

module.kubernetes.null_resource.kubernetes[0] (remote-exec): 				- You can check or miligate this in beforehand with "kubeadm config images pull" to make sure the images
module.kubernetes.null_resource.kubernetes[0] (remote-exec): 				  are downloaded locally and cached.

module.kubernetes.null_resource.kubernetes[0] (remote-exec): 		If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
module.kubernetes.null_resource.kubernetes[0] (remote-exec): 			- 'systemctl status kubelet'
module.kubernetes.null_resource.kubernetes[0] (remote-exec): 			- 'journalctl -xeu kubelet'

module.kubernetes.null_resource.kubernetes[0] (remote-exec): 		Additionally, a control plane component may have crashed or exited when started by the container runtime.
module.kubernetes.null_resource.kubernetes.1: Still creating... (2m30s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (2m30s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (2m30s elapsed)
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.2: Still creating... (2m40s elapsed)
module.kubernetes.null_resource.kubernetes.0: Still creating... (2m40s elapsed)
module.kubernetes.null_resource.kubernetes.1: Still creating... (2m40s elapsed)
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.0: Still creating... (2m50s elapsed)
module.kubernetes.null_resource.kubernetes.1: Still creating... (2m50s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (2m50s elapsed)
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.0: Still creating... (3m0s elapsed)
module.kubernetes.null_resource.kubernetes.1: Still creating... (3m0s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (3m0s elapsed)
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.0: Still creating... (3m10s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (3m10s elapsed)
module.kubernetes.null_resource.kubernetes.1: Still creating... (3m10s elapsed)
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.0: Still creating... (3m20s elapsed)
module.kubernetes.null_resource.kubernetes.1: Still creating... (3m20s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (3m20s elapsed)
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes.0: Still creating... (3m30s elapsed)
module.kubernetes.null_resource.kubernetes.1: Still creating... (3m30s elapsed)
module.kubernetes.null_resource.kubernetes.2: Still creating... (3m30s elapsed)
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[2] (remote-exec): Waiting for API server to respond
module.kubernetes.null_resource.kubernetes[1] (remote-exec): Waiting for API server to respond

These 3 targets all give me a 404.

k8s.gcr.io/kube-apiserver-amd64:v1.11.1
k8s.gcr.io/kube-controller-manager-amd64:v1.11.1
k8s.gcr.io/kube-scheduler-amd64:v1.11.1

systemctl status kubelet

root@kube1 ~ # systemctl status kubelet
● kubelet.service - kubelet: The Kubernetes Node Agent
   Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/kubelet.service.d
           └─10-kubeadm.conf, 90-kubelet-extras.conf
   Active: activating (auto-restart) (Result: exit-code) since Fri 2018-07-27 13:24:32 CEST; 6s ago
     Docs: http://kubernetes.io/docs/
  Process: 24221 ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS (code=exited, status=255)
 Main PID: 24221 (code=exited, status=255)

Jul 27 13:24:32 kube1 systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a
Jul 27 13:24:32 kube1 systemd[1]: kubelet.service: Unit entered failed state.
Jul 27 13:24:32 kube1 systemd[1]: kubelet.service: Failed with result 'exit-code'.

journalctl -xeu kubelet

root@kube1 ~ # journalctl -xeu kubelet
-- Subject: Unit kubelet.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit kubelet.service has finished shutting down.
Jul 27 13:25:02 kube1 systemd[1]: Started kubelet: The Kubernetes Node Agent.
-- Subject: Unit kubelet.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit kubelet.service has finished starting up.
-- 
-- The start-up result is done.
Jul 27 13:25:03 kube1 kubelet[24342]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jul 27 13:25:03 kube1 kubelet[24342]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jul 27 13:25:03 kube1 kubelet[24342]: I0727 13:25:03.077650   24342 server.go:408] Version: v1.11.1
Jul 27 13:25:03 kube1 kubelet[24342]: I0727 13:25:03.078114   24342 plugins.go:97] No cloud provider specified.
Jul 27 13:25:03 kube1 kubelet[24342]: I0727 13:25:03.080776   24342 certificate_store.go:131] Loading cert/key pair from "/var/lib/kubelet/pki/kubelet-client-current.pem".
Jul 27 13:25:03 kube1 kubelet[24342]: I0727 13:25:03.119614   24342 server.go:648] --cgroups-per-qos enabled, but --cgroup-root was not specified.  defaulting to /
Jul 27 13:25:03 kube1 kubelet[24342]: F0727 13:25:03.120245   24342 server.go:262] failed to run Kubelet: Running with swap on is not supported, please disable swap! or set --fail-swap-on flag to false. /proc/swaps contained: [Filename                                Type 
Jul 27 13:25:03 kube1 systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a
Jul 27 13:25:03 kube1 systemd[1]: kubelet.service: Unit entered failed state.
Jul 27 13:25:03 kube1 systemd[1]: kubelet.service: Failed with result 'exit-code'.
Jul 27 13:25:13 kube1 systemd[1]: kubelet.service: Service hold-off time over, scheduling restart.
Jul 27 13:25:13 kube1 systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
-- Subject: Unit kubelet.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit kubelet.service has finished shutting down.
Jul 27 13:25:13 kube1 systemd[1]: Started kubelet: The Kubernetes Node Agent.
-- Subject: Unit kubelet.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit kubelet.service has finished starting up.
-- 
-- The start-up result is done.
Jul 27 13:25:13 kube1 kubelet[24366]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jul 27 13:25:13 kube1 kubelet[24366]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jul 27 13:25:13 kube1 kubelet[24366]: I0727 13:25:13.327864   24366 server.go:408] Version: v1.11.1
Jul 27 13:25:13 kube1 kubelet[24366]: I0727 13:25:13.328368   24366 plugins.go:97] No cloud provider specified.
Jul 27 13:25:13 kube1 kubelet[24366]: I0727 13:25:13.334891   24366 certificate_store.go:131] Loading cert/key pair from "/var/lib/kubelet/pki/kubelet-client-current.pem".
Jul 27 13:25:13 kube1 kubelet[24366]: I0727 13:25:13.367249   24366 server.go:648] --cgroups-per-qos enabled, but --cgroup-root was not specified.  defaulting to /
Jul 27 13:25:13 kube1 kubelet[24366]: F0727 13:25:13.367845   24366 server.go:262] failed to run Kubelet: Running with swap on is not supported, please disable swap! or set --fail-swap-on flag to false. /proc/swaps contained: [Filename                                Type 
Jul 27 13:25:13 kube1 systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a
Jul 27 13:25:13 kube1 systemd[1]: kubelet.service: Unit entered failed state.
Jul 27 13:25:13 kube1 systemd[1]: kubelet.service: Failed with result 'exit-code'.
Jul 27 13:25:23 kube1 systemd[1]: kubelet.service: Service hold-off time over, scheduling restart.
Jul 27 13:25:23 kube1 systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
-- Subject: Unit kubelet.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit kubelet.service has finished shutting down.
Jul 27 13:25:23 kube1 systemd[1]: Started kubelet: The Kubernetes Node Agent.
-- Subject: Unit kubelet.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit kubelet.service has finished starting up.
-- 
-- The start-up result is done.
Jul 27 13:25:23 kube1 kubelet[24390]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jul 27 13:25:23 kube1 kubelet[24390]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jul 27 13:25:23 kube1 kubelet[24390]: I0727 13:25:23.631527   24390 server.go:408] Version: v1.11.1
Jul 27 13:25:23 kube1 kubelet[24390]: I0727 13:25:23.632335   24390 plugins.go:97] No cloud provider specified.
Jul 27 13:25:23 kube1 kubelet[24390]: I0727 13:25:23.650052   24390 certificate_store.go:131] Loading cert/key pair from "/var/lib/kubelet/pki/kubelet-client-current.pem".
Jul 27 13:25:23 kube1 kubelet[24390]: I0727 13:25:23.712878   24390 server.go:648] --cgroups-per-qos enabled, but --cgroup-root was not specified.  defaulting to /
Jul 27 13:25:23 kube1 kubelet[24390]: F0727 13:25:23.713852   24390 server.go:262] failed to run Kubelet: Running with swap on is not supported, please disable swap! or set --fail-swap-on flag to false. /proc/swaps contained: [Filename                                Type 
Jul 27 13:25:23 kube1 systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a
Jul 27 13:25:23 kube1 systemd[1]: kubelet.service: Unit entered failed state.
Jul 27 13:25:23 kube1 systemd[1]: kubelet.service: Failed with result 'exit-code'.
@pstadler
Copy link
Member

See: #22

@rm-rf-etc
Copy link
Contributor Author

I always get some variation of this result, no matter how many times I run terraform apply.

@rm-rf-etc
Copy link
Contributor Author

How is this the same as #22?

@pstadler
Copy link
Member

#24 - my bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pstadler @rm-rf-etc