skills.rest
scitix
scitixOFFICIAL
Explore all skills by this author →
GitHub

service-debug

Diagnose Kubernetes Service connectivity by verifying Endpoints, selectors, and port alignment.

225|28|Updated Mar 2, 2026
Search Tags:#debugging#networking#kubernetes#service#connectivity#endpoints
One-click install
npx skills add https://github.com/scitix/siclaw --skill service-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: service-debug
Source: https://github.com/scitix/siclaw/tree/main/skills/core/service-debug
Command: npx skills add https://github.com/scitix/siclaw --skill service-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps identify why a Kubernetes Service might not be routing traffic to its backend pods, leading to connectivity issues or services appearing unreachable.

Core Features & Use Cases

  • Service & Endpoint Verification: Checks if the Service exists and if it has corresponding Endpoints.
  • Selector Mismatch Detection: Identifies if the Service's label selector is correctly matching backend pods.
  • Port Configuration Analysis: Verifies that Service ports, targetPorts, and container ports are aligned.
  • Use Case: When users report that a deployed application is inaccessible via its Service name, this Skill can pinpoint whether the issue lies in incorrect pod labels, missing pods, port misconfigurations, or other common Service-related problems.

Quick Start

Use the service-debug skill to diagnose connectivity issues for the 'my-app-service' service in the 'production' namespace.

Frequently Asked Questions about service-debug

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

FAQPage Schema
Why does my Kubernetes Service have no endpoints and cannot route traffic?▼

Kubernetes Service connectivity fails when Endpoints are empty due to selector mismatches or missing backend pods. This Skill diagnoses these issues by verifying Service configurations, label selectors, and ensuring backend pods are correctly matching and running.

How do I debug Kubernetes Service to pod connectivity issues?▼

Debug Kubernetes Service to pod connectivity by inspecting Service and Endpoint configurations, verifying selector matching, and checking port alignment between Service targetPorts and container ports. This Skill automates these kubectl inspections to pinpoint routing failures.

How do I check if a Kubernetes Service port matches the container port?▼

Check Kubernetes Service port alignment by comparing the Service port, targetPort, and the container's listening port. This Skill analyzes these configurations to identify misalignments that prevent traffic from reaching the application inside the pod.

Do I need kubectl access to troubleshoot Kubernetes Service connectivity?▼

Yes, you need kubectl access to the Kubernetes cluster to troubleshoot Service connectivity. This Skill requires kubectl to inspect Service, Endpoints, and Pod resources to accurately diagnose routing and configuration problems.

What causes a Kubernetes Service to be unreachable despite pods running?▼

A Kubernetes Service appears unreachable despite running pods due to incorrect pod labels, port misconfigurations, or application listening issues. This Skill verifies selector matching and port alignment to isolate the specific configuration conflict.

Related Skills

Explore More Software Engineering Skills→
paulanunes85paulanunes85
1

kubectl-cli

Execute kubectl commands to diagnose and fix Kubernetes cluster issues in AKS and ARO environments.

Community
Intermediate
racarracar
1

postgres-query

Execute SQL statements in PostgreSQL containers via automatic container detection.

Community
Advanced
scitixscitix
225

dns-debug

Diagnose DNS resolution failures in Kubernetes clusters using kubectl.

Official
Intermediate
pauldotyupauldotyu

aks-networking

Configure and troubleshoot AKS cluster networking with Azure CLI and kubectl.

Community
Advanced