debug-network

Diagnose and resolve OpenShift service connectivity issues by verifying endpoints, selectors, routes, and policies.

48|31|Updated Feb 2, 2026

Search Tags:#Kubernetes #OpenShift #network debugging #connectivity issues #service diagnosis

Ready to run

npx skills add https://github.com/RHEcosystemAppEng/agentic-plugins --skill debug-network

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-network
Source: https://github.com/RHEcosystemAppEng/agentic-plugins/tree/main/rh-developer/skills/debug-network
Command: npx skills add https://github.com/RHEcosystemAppEng/agentic-plugins --skill debug-network

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Quickly diagnose and fix OpenShift service connectivity issues by automating endpoint, route, network policy, and pod readiness checks.

Core Features & Use Cases

Service Endpoint Verification: Ensures service endpoints are reachable.
Pod Selector Matching: Validates pod selectors for service endpoints.
Route Status Analysis: Inspects route statuses and conditions.
Network Policy Analysis: Checks for potential network policy issues.
Use Case: When services cannot communicate, routes return errors, or external access fails, use this skill to pinpoint the issue.

Quick Start

To debug OpenShift service connectivity issues, use the /debug-network skill.

Frequently Asked Questions about debug-network

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

FAQPage Schema

How do I diagnose OpenShift service connectivity issues automatically?▼

To diagnose OpenShift service connectivity issues, you can automate the verification of service endpoints, pod selectors, route statuses, and network policies to pinpoint the root cause of communication failures.

Why does my OpenShift route return errors when external access fails?▼

OpenShift route errors during external access failures often stem from unreachable service endpoints or misconfigured route statuses, which can be identified by inspecting route conditions and verifying backend pod readiness.

How do network policies affect Kubernetes pod connectivity and service reachability?▼

Network policies affect Kubernetes pod connectivity by restricting traffic flow, and assessing these policies is crucial to ensure service reachability when pods cannot communicate within the OpenShift environment.

What's the best way to verify pod selectors for OpenShift service endpoints?▼

The best way to verify pod selectors for OpenShift service endpoints is to validate that the selectors correctly match the intended pods, ensuring the service routes traffic to reachable and ready backend instances.

Do I need OpenShift resource access to troubleshoot service endpoint connectivity?▼

Yes, you need OpenShift resource access and Kubernetes commands to troubleshoot service endpoint connectivity, as the diagnosis requires querying the cluster to check pod readiness, selectors, and network policies.

When should I check route statuses to resolve OpenShift connectivity problems?▼

You should check route statuses to resolve OpenShift connectivity problems when services cannot communicate or external access fails, as inspecting route conditions helps identify configuration issues blocking traffic.