TROUBLESHOOTING, PRACTICE TEST – TROUBLESHOOT NETWORK Question

Kubernetes
#1

Hi,

For question#2, to fix the cluster, we need to correct the path in ds to --config =/var/lib/kube-proxy/config.conf but there is no file with at this location, getting error when i tried to look, Am i missing something here?

image
image712×139 8.52 KB

#2

the path of config.conf is located inside the pod itself not on the host. Check the steps in the attached gif
net

The kube-proxy pods are not running. As a result, the rules needed to allow connectivity to the services have not been created.

  1. Check the logs of the kube-proxy pods
    kubectl -n kube-system logs <name_of_the_kube_proxy_pod>

  2. The configuration file “/var/lib/kube-proxy/configuration.conf” is not valid. The configuration path does not match the data in the ConfigMap.
    kubectl -n kube-system describe configmap kube-proxy shows that the file name used is “config.conf” which is mounted in the kube-proxy daemonset pods at the path /var/lib/kube-proxy/config.conf

  3. However in the DaemonSet for kube-proxy, the command used to start the kube-proxy pod makes use of the path /var/lib/kube-proxy/configuration.conf.

Correct this path to /var/lib/kube-proxy/config.conf as per the ConfigMap and recreate the kube-proxy pods.

This should get the kube-proxy pods back in a running state.