Hii Team , Regarding troubleshooting lab for networking, I have one confusion regarding kube-proxy config path which path is correct?
I have tried to make changes in daemonset as per configmap file, but my kube-proxy pod is still in error state.
Kindly assist.
Thanks
Sakshi
All pods and services are running correctly in namespace triton. How to know that issue is due to kube proxy ?
Thanks
This second problem doesn’t involve the triton namespace at all; it’s about figuring out why kube-proxy is broken. If you try k -n kube-system describe po kube-proxy-dcrbc (the name in my instance of the lab), you won’t see anything that will explain why the pod is not up. But if you log at the logs:
root@controlplane ~ ➜ k -n kube-system logs kube-proxy-dcrbc
E0302 04:14:39.418432 1 run.go:74] "command failed" err="failed complete: open /var/lib/kube-proxy/configuration.conf: no such file or directory"
So the config file wasn’t found. If you look at the daemonset that created that pod, you’ll see that the /var/lib/kube-porxy directory is mounted into the pod’s container from a configmap, kube-proxy, which is also in the kube-system namespace. So we look at the configmap. It has two keys that will be treated as files: config.conf, and kubeconfig.conf. The latter is a kubeconfig file, but the config.conf file looks like configuration for kube proxy. So we change the “configuration.conf” string in the daemonset to “config.conf”, and this fixes kube-proxy.