ingress-debug

Diagnose Ingress failures by inspecting Kubernetes resources and controller health.

225|28|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/scitix/siclaw --skill ingress-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ingress-debug
Source: https://github.com/scitix/siclaw/tree/main/skills/core/ingress-debug
Command: npx skills add https://github.com/scitix/siclaw --skill ingress-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose and pinpoint the root cause of failures when external traffic cannot reach a Service through an Ingress, addressing issues like incorrect routing, backend unreachability, or TLS errors.

Core Features & Use Cases

  • Ingress Resource Analysis: Checks Ingress, IngressClass, and backend Services.
  • Controller Health Verification: Assesses the status and logs of Ingress controllers.
  • TLS/Certificate Debugging: Identifies issues with TLS secrets and certificate configurations.
  • Use Case: When users report a 404 or 502 error for a web application exposed via Ingress, this Skill systematically checks all relevant Kubernetes resources and controller configurations to find the source of the problem.

Quick Start

Use the ingress-debug skill to diagnose why the ingress named 'my-app-ingress' in the 'production' namespace is not routing traffic correctly.

Frequently Asked Questions about ingress-debug

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

FAQPage Schema
How do I troubleshoot a Kubernetes Ingress returning a 404 or 502 error?

Troubleshooting a Kubernetes Ingress 404 or 502 error involves inspecting Ingress resources, IngressClasses, backend Services, and controller health to pinpoint routing failures and external traffic misconfigurations.

Why does my Kubernetes Ingress rule not match external traffic?

Kubernetes Ingress rules fail to match external traffic when routing configurations are incorrect, IngressClass assignments are missing, or backend Services are unreachable due to misconfigurations.

How do I diagnose TLS errors preventing traffic from reaching my Ingress?

Diagnosing TLS errors preventing traffic from reaching an Ingress requires checking TLS secrets and validating certificate configurations within the Kubernetes cluster to ensure secure external traffic management.

What is the best way to verify Ingress controller health during routing failures?

Verifying Ingress controller health during routing failures involves assessing controller status and logs to identify issues affecting external traffic routing and backend connectivity.

Can I check backend Service unreachability when debugging an Ingress?

Yes, checking backend Service unreachability is possible by diagnosing Ingress failures, which involves inspecting backend Services and Ingress controller health to identify routing issue root causes.

When should I inspect IngressClasses to fix external traffic routing?

Inspect IngressClasses to fix external traffic routing when diagnosing Ingress failures, as incorrect class assignments prevent the Ingress controller from processing rules and reaching backend Services.