-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
K3s service does not start: failed to get CA certs #9343
Comments
What host is If you're going to use |
Thats a good hint. I will update this issue as soon as I find a solution - for future reference. I will most likely not bother you anymore. Thank you. |
Positive. It was a terraform state issue. Apparently there were some weird things going on in the state even though I destroyed Thanks for the hint again. |
Environmental Info:
k3s version v1.28.6+k3s1 (39a0001)
go version go1.20.13
Node(s) CPU architecture, OS, and Version:
openSUSE MicroOS , Linux 6.7.2-1-default
uname -a
Linux k3s-control-plane-nbg1-lso 6.7.2-1-default #1 SMP PREEMPT_DYNAMIC Fri Jan 26 11:01:28 UTC 2024 (a52bf76) x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
2 servers, 3 agents
Describe the bug:
I'm having issues spinning up a K3s cluster using
kube-hetzner
I also opened an Issue in their repository (kube-hetzner/terraform-hcloud-kube-hetzner#1201), as I am not certain, what the root cause is. After a fresh installation the nodes are unable to start/connect, as the ca certs are not exposed. Starting the server viaresults in
curling the cacerts endpoint does not work.
The node is available in the network.
ping 10.255.0.101 -c 4
lsof -i
shows that there are no k3s-related services running at all. The same issue comes up on all nodes, which is of course why the ca cert endpoints are not exposed anywhere. I am unaware of, if there are missing steps, as I am not able to backtrack the exact steps terraform/kube-hetzner does here.Steps To Reproduce:
Create a MicroOS Snapshot
kube.tf
Apply it.
Expected behavior:
The k3s service starts and the vm exposes its ca certs to the other nodes on
:6443
.Actual behavior:
The creation will timeout after ~10 minutes because the temporary terraform script runs into a timeout
/tmp/terraform_*.sh
Additional context / logs:
journalctl -xeu k3s.service
/usr/local/bin/k3s server
Installing k3s again on a node does not work either:
curl -sfL https://get.k3s.io 6 | INSTALL_K3S_VERSION=v1.28.6+k3s1 sh -s server
The text was updated successfully, but these errors were encountered: