k8s-networking

Align Kubernetes services, endpoints, ingresses, and network policies to resolve connectivity issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/spigell/my-agents --skill k8s-networking-spigell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: k8s-networking
Source: https://github.com/spigell/my-agents/tree/main/agents/shared/src/tools/ask_kubernetes_expert/skills/k8s-networking
Command: npx skills add https://github.com/spigell/my-agents --skill k8s-networking-spigell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kubernetes networking changes are error-prone, making it difficult to expose services correctly, ensure endpoints receive traffic, and prevent unintended access due to misconfigured ingresses or network policies.

Core Features & Use Cases

  • Service and Endpoint Management: Validate service-to-pod connectivity by checking endpoints and ensuring selectors align with pod labels.
  • Ingress Configuration Guidance: List and describe ingresses and safely apply ingress manifests for routing and load balancing.
  • Network Policy Isolation Review: Inspect network policies and troubleshoot traffic isolation by reviewing rules and policy impact on allowed/denied flows.
  • Connectivity Troubleshooting: Debug DNS and traffic behavior from within pods by executing commands in a targeted debugging pod.

Quick Start

Use k8s-networking to troubleshoot why a service is unreachable in the given namespace by asking for endpoints, service selector alignment with pods, relevant network policies, and DNS verification from a debug pod.

Frequently Asked Questions about k8s-networking

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

FAQPage Schema
Why is my Kubernetes service unreachable and how do I troubleshoot the connectivity?▼

Troubleshoot Kubernetes service connectivity by validating endpoint health first, then verifying label selectors align with pod labels to ensure traffic routes correctly. This resolves misrouted traffic before assuming service configuration errors.

How do I review network policies to troubleshoot traffic isolation in Kubernetes?▼

Review Kubernetes network policies by inspecting the rules to determine their impact on allowed and denied flows. This traffic isolation review identifies if policies are unintentionally blocking legitimate pod communication.

What is the best way to verify DNS resolution and traffic behavior from within a pod?▼

Verify DNS resolution and traffic behavior by executing commands in a targeted debugging pod. This in-pod execution checks DNS routing and validates connectivity directly from the affected network namespace.

How do I safely apply ingress manifests for routing and load balancing in Kubernetes?▼

Safely apply Kubernetes ingress manifests by listing and describing existing ingresses before applying new configurations. This validates routing and load balancing rules to prevent misconfigured traffic exposure.

Do I need to check endpoint health before troubleshooting Kubernetes service routing?▼

Yes, validating endpoint health is required before making service assumptions. Checking endpoints ensures backing pods are ready to receive traffic, preventing misdiagnosis of Kubernetes routing issues.

Can I use kubectl to debug misrouted traffic and access issues across services and ingresses?▼

Yes, use kubectl-backed networking tools to debug misrouted traffic and access issues. This aligns services, endpoints, and ingresses to resolve connectivity problems across the cluster.