---
title: Fixing a 502 bad gateway on kubernetes cluster namespace using Kubegrade
slug: fixing-a-502-bad-gateway-on-kubernetes-cluster-namespace-using-kubegrade
createdAt: 2026-03-09T09:43:30.900Z
---

::embed[]{url="https://www.youtube.com/embed/_3mO1gPeS7U"}



# Overview

This short demo shows how Kubegrade troubleshoots and fixes a real Kubernetes production issue end-to-end. 

Kubegrade automates Kubernetes troubleshooting by detecting issues, explaining root causes, and fixing them through GitOps pull requests.



# Scenario

An application returns a 502 Bad Gateway due to a misconfigured container port.



# What happens in the demo

- Navigate cluster and namespace visualization
- Ask Kubegrade AI to diagnose the issue
- AI correlates Git repo config with live cluster state
- Root cause identified: incorrect container/target port
- AI generates a Git pull request with the fix
- Change is merged and applied via Argo CD
- Application recovers successfully
- No manual YAML digging
- No tribal knowledge
- No copy-paste debugging



# This is one example. The same workflow applies to:

- Networking misconfigurations
- PVC and storage issues
- Deployment and runtime errors
- Drift between Git and cluster state