on my k0s cluster which is running on arch linux/wsl-2
After setting up k0s.yaml and restarting my cluster the Traefik pod starts but not the metallb load balancer. What’s the best way to debug why. Are there log files generated when processing the config file how can I access these log files?
As it’s the controller that processes the Helm extensions you should have some logs in the controller logs. Assumin you’re running on systemd based setup, you can access the logs via journalctl -u k0scontroller.
The controller also creates Chart objects in the API so you can also look at the status of those: kubectl get chart -A.
If the metallb chart is not creating any resources my guess would be malformed values input.
> NAME READY STATUS RESTARTS AGE
> pod/local-ai-59db6b9c94-742qt 1/1 Running 1 (155m ago) 46h
> pod/traefik-778f995998-hvn76 1/1 Running 0 100m
> NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
> service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 11d
> service/local-ai ClusterIP 10.105.91.246 <none> 80/TCP 46h
> service/traefik LoadBalancer 10.109.154.133 <pending> 80:31506/TCP,443:31345/TCP 100m
> NAME READY UP-TO-DATE AVAILABLE AGE
> deployment.apps/local-ai 1/1 1 1 46h
> deployment.apps/traefik 1/1 1 1 100m
> NAME DESIRED CURRENT READY AGE
> replicaset.apps/local-ai-59db6b9c94 1 1 1 46h
> replicaset.apps/traefik-778f995998 1 1 1 100m
> Any suggestions on how to fix
> sudo k0s reset
> WARN[2023-06-12 09:56:40] To ensure a full reset, a node reboot is recommended.
> mwoodpatrick@westie_arch:~$ sudo k0s install
> Install k0s on a brand-new system. Must be run as root (or with sudo)
> sudo whoami
Why does k0s think its not being run as root, or how do I debug this