Question

A ClusterIP Service named 'billing-api' correctly lists healthy pod endpoints when you run 'kubectl get endpoints billing-api'. However, requests from other pods to the Service's ClusterIP consistently time out, while connecting directly to the pod IPs works fine. On the affected worker node, you notice the kube-proxy pod has been in a running state but its logs show it failed to apply rules. Which action is the MOST likely to resolve the connectivity problem?

Accepted Answer

Restart the kube-proxy pod on the affected node so it can rebuild the iptables/IPVS rules that map the ClusterIP to backend endpoints

Answer

Recreate the Service object so a new ClusterIP is allocated and the endpoints are regenerated

Answer

Edit the Service and change its type to NodePort so traffic bypasses the ClusterIP routing layer

Answer

Add the pod IPs directly to a manually created Endpoints object to override the failed rules