Troubleshooting Network Issues

DNS

Kubernetes has a guide on Debugging DNS Resolution which is quite extensive and covers most of the general troubleshooting with relation to resolving domain names from within the cluster. In particular, though, the following sections would be the most pertinent.

• Check Local DNS Resolution

• Ensure CoreDNS is Running

• Enable Query Logging

Additionally, see Known Issues for any other documented edge case scenarios.

Calico

Pod Networking Broken if Kernel IP Forwarding Not Enabled

If net.ipv4.ip_forward is set to 0, meaning that kernel IP forwarding is disabled, pod networking will be broken. IP forwarding needs to be enabled (set to 1) to allow traffic to be forwarded from one interface to the other.

Pods may enter into a CrashLoopBackOff state as a result of being unable to reach the cluster VIP or otherwise and constantly failing their health checks.

The enabled value should be set by default on most installations. Otherwise, though, ensure it is not manually defined, or, if it cannot be undefined, set to enabled explicitly.

/etc/sysctl.d/90-ip-forward.conf

net.ipv4.ip_forward = 1

The value will be persisted on reboot.