k8s-network-troubleshooting
Use when traffic does not reach a workload in Kubernetes although its pods are running: a Service with no endpoints, a wrong selector or targetPort, connection refused or time-outs between pods, DNS names that do not resolve (NXDOMAIN, "server can't find"), a NetworkPolicy blocking traffic, or an Ingress or Gateway API route that does not route. Investigates with kubectl get and describe, asks before checks inside a container, and proposes fixes. Reads first and asks before changing anything.
- License
- Apache-2.0
Pinned to revision ce7de97330d7, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/k8s-network-troubleshooting/SKILL.md
- skills/k8s-network-troubleshooting/.claude-plugin/plugin.json
- skills/k8s-network-troubleshooting/references/dns.md
- skills/k8s-network-troubleshooting/references/ingress-gateway.md
- skills/k8s-network-troubleshooting/references/networkpolicy.md
- skills/k8s-network-troubleshooting/references/services.md
Every link opens the file at its source, pinned to the revision this page describes.