Use cases / Kubernetes
Use case · Kubernetes
Repeat failures on Kubernetes, fixed before the page.
Stuck certificates, stuck ReplicaSets, frozen jobs, failed pods. Familiar problems that eat a platform team’s week.
What it takes off your plate
01
21 built-in checks
Read-only checks on your cluster. No metrics scraping and no log shipping.
02
A short list of safe fixers
Remove a failed pod, stop a frozen job, restart a stuck ReplicaSet. Each is safe and can be undone.
03
Works on your distro
Kubernetes, EKS, GKE, AKS, k3s, OpenShift and RKE2.
In practice
Every fix leaves a record
Detection, cause, policy decision, fix and verification — written down, signed and exportable.
fix record · prod-eu-1VERIFIED
10:34:12DETECTCrashLoopBackOff · payments-api · OOMKilled 137
10:34:48CAUSEmemory limit 512Mi vs p99 working set 780Mi
10:35:02POLICYlimit-raise ≤ 2× · namespace payments · auto-approved
10:35:19FIXpatched limits 512Mi → 1Gi, rollout restarted
10:41:30VERIFY0 restarts, error rate 0.02%, 6 min observed
signed by workload identity · srenix-fixer@prod-eu-1
Works with what you run
Cloud
AWS · GCP · Azure
K8s distros
Kubernetes · EKS · GKE · AKS · k3s · OpenShift · RKE2
Observability & ticketing
Prometheus · Alertmanager · Grafana · Loki (paid) · OTLP (paid) · OpenProject · Jira · ServiceNow · Slack
K8s-native infra
Vault · cert-manager · CNPG · Rook/Ceph · External Secrets · Kong · ArgoCD · Cloudflare
Trigger sources
K8s informers · Alertmanager polling · Webhook (HMAC) · CronJob resync
AI providers
OpenAI · Anthropic · In-cluster vLLM
On-call should be quieter every week
Helm install in 5 minutes. No telemetry exfiltration. No per-investigation surprises.