How to debug issue with Pi-Hole provider #4990
Replies: 1 comment
-
Learned a lot about kubectl exec and kubectl debug....but in the end that was not how I resolved. Added "logLevel: debug" in helm values.yaml, which showed the error was after the http access to pi-hole. Eventually figured out that the pihole-password should not be enclosed in quotes when in YAM: file (I was doing because there is an exclamation mark in the password), and I had to quote the exclamation mark in the password when passing from command line - i.e. !. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to bring up external-DNS in a homelab RPi K3S installation, upstream Pi-Hole is running on a separate RPi. I am getting the following issue which I have no idea about what it means, but I don't know how to proceed with debugging further since I am unable to get a shell into the container as the pod is already in CrashLoopBackOff state. Any pointers would be most helpful. TIA.
time="2025-01-03T17:18:34Z" level=info msg="Instantiating new Kubernetes client"
time="2025-01-03T17:18:34Z" level=info msg="Using inCluster-config based on serviceaccount-token"
time="2025-01-03T17:18:34Z" level=info msg="Created Kubernetes client https://10.43.0.1:443"
time="2025-01-03T17:18:34Z" level=fatal msg="could not parse token from login response"
Beta Was this translation helpful? Give feedback.
All reactions