diagnose-network-issue

Diagnose Kubernetes pod network connectivity issues via DNS, service, and policy checks.

3|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/X-McKay/kubani --skill diagnose-network-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose-network-issue
Source: https://github.com/X-McKay/kubani/tree/main/kubani/skills/k8s/diagnostic/diagnose-network-issue
Command: npx skills add https://github.com/X-McKay/kubani --skill diagnose-network-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose and identify the root cause of network connectivity problems experienced by Kubernetes pods, such as inability to reach other services or external endpoints.

Core Features & Use Cases

  • Automated Diagnostics: Performs checks for DNS resolution, service reachability, and network policy conflicts.
  • Root Cause Analysis: Gathers evidence from pod details, execution commands, and Kubernetes resources to pinpoint network issues.
  • Use Case: When a pod in the production namespace reports that it cannot connect to the database-service, this skill can be invoked to determine if it's a DNS issue, a firewall rule, or a network policy blocking the traffic.

Quick Start

Use the diagnose-network-issue skill to troubleshoot connectivity for the pod named 'my-app-pod' in the 'staging' namespace, targeting the service 'internal-api'.

Frequently Asked Questions about diagnose-network-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot Kubernetes pod network connectivity issues?

To troubleshoot Kubernetes pod network connectivity issues, you need to check DNS resolution, service accessibility, and network policy conflicts. This involves gathering evidence from pod details and Kubernetes resources to pinpoint the root cause.

Why does my Kubernetes pod fail to connect to an internal service?

A Kubernetes pod may fail to connect to an internal service due to DNS resolution failures, inaccessible service endpoints, or restrictive network policies. Diagnosing requires checking pod details and executing commands within the pod.

How do I check if a network policy is blocking traffic to my pod?

To check if a network policy is blocking pod traffic, analyze Kubernetes network policy conflicts by gathering evidence from the Kubernetes API. This identifies restrictive rules preventing communication with internal or external endpoints.

Do I need MCP tools to diagnose Kubernetes DNS resolution problems?

Yes, you need MCP tools to diagnose Kubernetes DNS resolution problems. They are required for interacting with the Kubernetes API and executing commands within pods to gather evidence for root cause analysis.

What is the best way to identify the root cause of pod connectivity failures in Kubernetes?

The best way to identify the root cause of pod connectivity failures is performing automated diagnostics for DNS resolution, service reachability, and network policy conflicts. This gathers evidence from Kubernetes resources to pinpoint network issues.