-
-
Notifications
You must be signed in to change notification settings - Fork 462
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
Cluster not working after reboot #262
Comments
Update: If I Create a cluster with k3d create, verify kubectl cluster-info works then do k3d stop cluster then do k3d start cluster I get the same behavior. I am no longer able to issue cluster-info etc. |
it happens to me similarly. but something wrong occurred before restart What did you do? How was the cluster created? What did you do afterwards?
(and create admin-user / admin-user-role following https://rancher.com/docs/k3s/latest/en/installation/kube-dashboard/)
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
What did you expect to happen? OS: k3d version: docker version: Server: Docker Engine - Community for more information,i execute:
and got: I0604 07:07:02.237225 54688 loader.go:375] Config loaded from file: /Users/myaccout/.kube/config To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. |
Hi there, thanks for opening this issue 👍 |
@iwilltry42 what's the current state on this (i still got an error but PR is merged) |
@bukowa what are your errors? |
cluster created with 3 servers |
still doesn't work |
@iwilltry42 I just tried again and still after restart i cannot connect.
Then i closed docker && wsl --shutdown
server 1 docker logs:
server 2 docker logs:
|
Thanks for the input @bukowa 👍 UPDATE: Following up in new issue: #550 |
What did you do?
Problem restarting the cluster after a reboot
How was the cluster created?
k3d create cluster dev --masters 3 --workers 3
What did you do afterwards?
reboot
What did you expect to happen?
Kubectl to work after K3d start cluster dev
Concise description of what you expected to happen after doing what you described above.
Running k3d in Wsl2 Debian
Creating the cluster works and I can initially issue kubectl commands to it. If I reboot the cluster is down on reboot. Issuing a "k3d start cluster dev" appears to work and "docker ps" shows the running containers but kubectl returns Error from server (ServiceUnavailable): the server is currently unable to handle the request.
If I delete the cluster and recreate then I can get it to work but cannot seem to get the existing cluster working after a restart
.
Screenshots or terminal output
Which OS & Architecture?
Windows 10 WSL2 Debian
Which version of
k3d
?v3.0.0-beta.1
k3d --version
k3d version v3.0.0-beta.1
Which version of docker?
19.03.11
docker version
Version: 19.03.11
API version: 1.40
Go version: go1.13.10
Git commit: 42e35e61f3
Built: Mon Jun 1 09:12:41 2020
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.8
API version: 1.40 (minimum version 1.12)
Go version: go1.12.17
Git commit: afacb8b
Built: Wed Mar 11 01:29:16 2020
OS/Arch: linux/amd64
Experimental: true
containerd:
Version: v1.2.13
GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
The text was updated successfully, but these errors were encountered: