Kubernetes & Cloud Ops Prompts

What's Inside

• ▸Pod inspection, exec, and the RBAC create-verb gotcha
• ▸Right-sizing requests/limits & fixing OOMKilled workloads
• ▸Pending / unschedulable pod diagnosis
• ▸PVC storage reclamation & volume-bind debugging
• ▸Service routing, endpoints, and ingress/TLS certificate issues
• ▸Autoscaling with HPAs and PodDisruptionBudgets
• ▸Secrets/config wiring (the dev-vs-prod selection gotcha)
• ▸CronJobs, cluster health, waste and cost audits

Try One Before You Buy

Published verbatim from the pack: “Fix an RBAC permission error” — When Kubernetes says forbidden and you want least-privilege, not cluster-admin.

I'm getting {{forbidden / permission error}} doing {{action}} as
{{user/serviceaccount}}. Give me the exact fix:
1. Name the precise verb + resource the action requires (people under-scope
   this — e.g. exec needs `create` on `pods/exec`, not just `get`).
2. The minimal Role/ClusterRole + binding to grant it (least privilege).
3. Apply it in BOTH the live cluster AND the gitops/manifest source so it
   survives the next reconcile.
Output the RBAC yaml and the apply/commit steps.

Why it works: RBAC errors are almost always a missing specific verb; fixing only the live cluster (not gitops) means it silently reverts.

Every prompt in the pack ships with a when-to-use line and a why-it-works note like this one.