This message was deleted.
# k3sa
adamant-kite-43734
10/07/2024, 8:59 PMThis message was deleted.
b
bland-article-62755
10/08/2024, 2:26 PMWaiting for the k3s service to come up?
b
brave-pilot-1886
10/08/2024, 8:41 PMIt was working previously but I had a power outage and it rebooted 😕
b
bland-article-62755
10/08/2024, 8:42 PMYou can try restarting the services or a new reboot?
b
brave-pilot-1886
10/08/2024, 8:43 PMAlready did that with no success :d
brave-pilot-1886
10/08/2024, 8:43 PMI have a doubt. In k3s is there any pod responsible for apiserver?
brave-pilot-1886
10/08/2024, 8:44 PMOr is handled by the binary?
b
bland-article-62755
10/08/2024, 8:44 PMkubectl get pods -A |grep apib
brave-pilot-1886
10/08/2024, 8:44 PMnothing
brave-pilot-1886
10/08/2024, 8:45 PM:c
b
bland-article-62755
10/08/2024, 8:45 PMIs this a single node or a cluster?
b
brave-pilot-1886
10/08/2024, 8:45 PMsingle node
b
bland-article-62755
10/08/2024, 8:45 PMOh...
bland-article-62755
10/08/2024, 8:46 PMSeems hosed. I think there's a way to basically tell k3s to re-init
bland-article-62755
10/08/2024, 8:46 PMHonestly though I don't remember, I'd wait for someone else to weigh in.
👍 1
b
brave-pilot-1886
10/08/2024, 9:03 PMI don't have anything stateful stored in this cluster and I'm using GitOps, so I decided to run the
/usr/local/bin/k3s-uninstall.shbrave-pilot-1886
10/08/2024, 9:06 PM[INFO] plugin/kubernetes: pkg/mod/k8s.io/client-go@v0.29.3/tools/cache/reflector.go:229: failed to list *v1.Service: Get "<https://10.43.0.1:443/api/v1/services?limit=500&resourceVersion=0>": dial tcp 10.43.0.1:443: connect: connection refused6 Views