Troubleshooting and cheats

In order to check the health of your pods you can check their logs by running:

kubectl logs <pod-name>

Another useful command to show details of a pod is:

kubectl describe pod <pod-name>

To ssh into a pod use:

kubectl exec -it <pod-name> -- bash

To restart a pod, you can just delete it and a new pod will be created automatically:

kubectl delete pod <pod-name>

Find more useful commands in the documentation: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands

If you need to change the config in gw.values.yaml or alloy.values.yaml you can use the same helm upgrade command as used for the installation. Find the commands in this README and in clusters/backend/scripts/deploy_monitoring.sh script.

If you want to uninstall a chart you can simply run

helm uninstall <your-chart-name>

e.g.

helm uninstall alloy

But be aware that some old Custom Resources might linger around after chart uninstallation and have the potential to cause problems. You can check for lingering CRDs by running:

kubectl get crd

And delete single ones with:

kubectl delete crd <crd-name>

To stop all of the K3s containers and reset the containerd state, the k3s-killall.sh script can be used.

The killall script cleans up containers, K3s directories, and networking components while also removing the iptables chain with all the associated rules. The cluster data will not be deleted.

To run the killall script from a server node, run:

/usr/local/bin/k3s-killall.sh