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
With current versions of kind, helm and kubectl installed kind create cluster --config ./kind.yaml --image kindest/node:v1.18.2
fails with
[kubelet-check] It seems like the kubelet isn't running or healthy.
[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.
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
- 'systemctl status kubelet'
- 'journalctl -xeu kubelet'
Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
- 'crictl --runtime-endpoint unix:///run/containerd/containerd.sock ps -a | grep kube | grep -v pause'
Once you have found the failing container, you can inspect its logs with:
- 'crictl --runtime-endpoint unix:///run/containerd/containerd.sock logs CONTAINERID'
couldn't initialize a Kubernetes cluster
Just running kind create cluster --config ./kind.yaml
seems to fix the issue (at least for this step)
The text was updated successfully, but these errors were encountered:
Local Setup: https://github.com/datastaxdevs/workshop-k8ssandra/wiki/Local-Setup
With current versions of kind, helm and kubectl installed
kind create cluster --config ./kind.yaml --image kindest/node:v1.18.2
fails with
Just running
kind create cluster --config ./kind.yaml
seems to fix the issue (at least for this step)
The text was updated successfully, but these errors were encountered: