Fixing a 502 bad gateway on kubernetes cluster namespace using Kubegrade

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