I'm building a read-only context engine for Kubernetes and AI agents (opens in new tab)
Kubernetes gives us an incredibly powerful API. It also gives us a familiar debugging ritual: kubectl get pods kubectl describe pod ... kubectl get svc ... kubectl get endpointslices ... kubectl get deployment ... kubectl get events ... kubectl get application.argoproj.io ... Then we mentally stitch the result together. Which workload owns this Pod? Which Service routes to it? Are there ready endpoints? Is the namespace unhealthy because of one bad Deployment, a missing backend, warning Event...
Read the original article