skills.rest
kagenti
kagentiOFFICIAL
Explore all skills by this author →
GitHub

kagenti:ui-debug

Diagnose Kagenti UI issues by analyzing pod status, Nginx logs, and Kubernetes events.

292|103|Updated Mar 27, 2025
Search Tags:#ui#api#debug#kubernetes#nginx#kagenti#502 error
One-click install
npx skills add https://github.com/kagenti/kagenti --skill kagenti-ui-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kagenti:ui-debug
Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/kagenti%3Aui-debug
Command: npx skills add https://github.com/kagenti/kagenti --skill kagenti-ui-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps troubleshoot and resolve common issues with the Kagenti user interface, including 502 errors, API connectivity problems, and Nginx proxy misconfigurations.

Core Features & Use Cases

  • Pod Status Checks: Quickly verify the health of Kagenti UI and backend pods.
  • Log Analysis: Inspect Nginx and backend logs for specific errors like 502 Bad Gateway.
  • Event Monitoring: Review recent Kubernetes events for underlying cluster issues.
  • Common Issue Diagnosis: Provides specific steps for diagnosing and fixing Nginx 502 errors, Istio mTLS problems, and API data discrepancies.
  • Use Case: If users report that the Kagenti dashboard is showing a 502 error, this Skill provides the exact commands to check pod status, Nginx logs, and backend connectivity to pinpoint the root cause.

Quick Start

Use the kagenti:ui-debug skill to check the status of Kagenti UI and backend pods in the kagenti-system namespace.

Frequently Asked Questions about kagenti:ui-debug

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

FAQPage Schema
How do I fix a 502 Bad Gateway error on the Kagenti UI?▼

To fix a 502 Bad Gateway error on the Kagenti UI, check pod status, inspect Nginx and backend logs, and review Kubernetes events within the kagenti-system namespace to pinpoint connectivity failures.

Why does my Kubernetes API connectivity fail with Nginx proxy problems?▼

Kubernetes API connectivity failures with Nginx proxy problems often stem from connection resets or Istio mTLS misconfigurations, which you can diagnose by analyzing Nginx logs and backend pod status.

How do I diagnose Istio mTLS misconfigurations causing connection resets?▼

Diagnose Istio mTLS misconfigurations by analyzing Kubernetes events and backend logs in the kagenti-system namespace, checking for connection resets and authentication configuration errors affecting the API.

Can I check Kagenti backend pod health in a specific Kubernetes namespace?▼

Yes, you can check Kagenti backend pod health by running status checks specifically within the kagenti-system namespace to quickly verify the health of UI and backend pods.

What is the best way to troubleshoot API data discrepancies in Kagenti?▼

The best way to troubleshoot API data discrepancies in Kagenti is to inspect backend logs and review recent Kubernetes events to identify underlying authentication configuration errors or proxy failures.

How do I monitor Kubernetes events for underlying cluster issues affecting Kagenti?▼

Monitor Kubernetes events for underlying cluster issues affecting Kagenti by reviewing recent events within the kagenti-system namespace, checking pod status, and analyzing Nginx logs for proxy errors.

Related Skills

Explore More Software Engineering Skills→
dieguscldieguscl

k8s-check

Diagnose Kubernetes cluster health by checking pod status, events, resource usage, and restart counts.

Community
Intermediate
JansenAnalyticsJansenAnalytics
5

nginx-caddy

Configure Nginx or Caddy as a secure reverse proxy with SSL/TLS.

Community
Intermediate
cosmixcosmix
53

istio

Configure Istio resources for mTLS, traffic routing, and policy enforcement.

Community
Advanced
kagentikagenti
292

k8s:logs

Query and analyze Kubernetes logs from Kagenti platform components.

Official
Intermediate