Prerequisites
Kubernetes Cluster
At least one cluster connected with the Kestrel operator installed.
Datadog / OpenTelemetry (optional)
Connect Datadog or OpenTelemetry to enable metrics queries (CPU, memory, latency, error rates).
Targeting Clusters
Use@cluster-name to direct your query to a specific Kubernetes cluster. You can target multiple clusters in a single query for cross-cluster comparisons.
@ prefix needed.
Pod Status and Logs
Ask about the health, status, and logs of any pod or group of pods.Events and Recent Changes
Query Kubernetes events to understand what happened and when.Resource Specs and Configuration
Inspect the configuration of deployments, pods, services, and other Kubernetes resources.Metrics
Requires Datadog or OpenTelemetry to be connected.Network Policies and Service Mesh
Query network policies, services, and connectivity.Deployment Status and Rollouts
Inspect deployments, rollouts, and scaling operations.Cross-Cluster Comparison
Compare resources and configurations across multiple connected clusters.Example Conversation
You:
@prod-eks-cluster Pods in the payments namespace are throwing 5xx errors. What’s going on? Cross-reference with Datadog latency and error rate metrics for the payments-api service.
Kestrel:
I found 3 pods in theYou:paymentsnamespace showing issues:Datadog metrics show the
payments-api-7f8b9c-x4k2m— Running but 12 container restarts in the last hourpayments-api-7f8b9c-n3j8p— CrashLoopBackOff since 14:47 UTCpayments-worker-6d4a8b-j9n3p— Running, 0 restartspayments-apiP99 latency spiked from 85ms to 3.8s at 14:32 UTC. Error rate jumped from 0.1% to 14.2% at the same time. The container logs frompayments-api-7f8b9c-n3j8pshow repeatedFATAL: connection pool exhausted, max_connections=10errors. The deployment was updated at 14:30 UTC — image changed fromv2.13.2tov2.14.0.
What changed in v2.14.0? Can you find the PR?Kestrel:
The image tagYou:v2.14.0maps to PR #847 inacme/payments-service, merged at 14:28 UTC by @jane.doe. The PR description says “Optimize DB connection handling” — it reducedDB_MAX_CONNECTIONSfrom 50 to 10 in the deployment environment variables. This matches theconnection pool exhaustederror in the logs. The connection pool is now too small for the current request volume.
Roll back the deployment to v2.13.2 and increase the memory limit to 512Mi while you’re at it.Kestrel:
Here’s the proposed change for thepayments-apideployment:(displays diff with Safe Apply, Create PR, and Copy options)
- Revert image tag from
v2.14.0tov2.13.2- Increase memory limit from
256Mito512Mi
Next Steps
- Cloud Investigation — query AWS and OCI resources and security configurations
- Code Investigation — search and trace code changes across repositories
- Cost Analysis — analyze Kubernetes and cloud spend patterns
- Configuration Changes — generate and apply YAML and Terraform changes