Kubernetes taste — Claude & Claude.ai prompt: platform team rules
A prompt that hands your AI assistant a platform team's Kubernetes rules: GitOps, probes, resources, pod security. Useful when you ask a model to write or review manifests.
Open on GitHubWhat Kubernetes taste does
This prompt spells out a platform team's taste in Kubernetes — a rule set the assistant follows when working with manifests. Everything ships through GitOps, Argo CD or Flux, and nobody runs kubectl apply against production by hand. Shared services get packaged with Helm or Kustomize, while per-environment overlays stay small and readable.
A chunk of it covers resources and probes. Every container gets CPU and memory requests, with the memory limit equal to the request. Latency-sensitive services skip CPU limits so they don't get throttled. Each Deployment needs a readiness probe; add liveness only when the app can truly deadlock. Slow-booting apps get a startup probe instead of a long initialDelaySeconds.
Security and reliability come next. Images are pinned by digest or an immutable tag, never latest. Containers run as non-root with a read-only root filesystem and all capabilities dropped. Every namespace starts with a default-deny NetworkPolicy. Secrets stay out of Git and sync from a secret manager via External Secrets or Sealed Secrets. If your team hasn't moved to GitOps yet, some of these rules won't map onto how you deploy today.
What it helps with
- check manifests against a platform team's rules
- set container resource requests and limits
- configure probes for a slow-booting app
- lock down a new namespace with default-deny
- move secrets out of Git into a secret manager
Example prompts for the agent
- Review my Deployment against the Kubernetes taste rules and tell me what's off
- Write a manifest for a stateless service with probes, resources and a PodDisruptionBudget
- How do I set up a NetworkPolicy for a new namespace under these rules?
How to install Kubernetes taste
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Kubernetes taste
How do I install Kubernetes taste in Claude?
There's no install command: paste the prompt into a chat or save it as custom instructions. Copy the rule text and send it as your first message.
What does Kubernetes taste do?
It gives the assistant a platform team's Kubernetes rules covering GitOps, probes, resource requests, pod security and secrets handling. The model then leans on them when generating or reviewing manifests.
Which platforms does the prompt work on?
It targets Claude and Claude.ai as plain text you paste into a conversation. In Claude it goes in as the file .claude/commands/prompts.csv.md.
Source text
prompts.csv · CC0-1.0
# Kubernetes taste of a platform team - Deploy everything through GitOps (Argo CD or Flux); nobody runs kubectl apply against production by hand. Confidence: 0.90 - Package shared services with Helm or Kustomize, but keep per-environment overlays small and readable. Confidence: 0.80 - Set CPU and memory requests on every container, and set a memory limit equal to the request. Confidence: 0.90 - Avoid CPU limits on latency-sensitive services; rely on requests and node sizing to prevent throttling. Confidence: 0.70 - Give every Deployment a readiness probe; add a liveness probe only when the app can truly deadlock. Confidence: 0.85 - Use a startup probe for slow-booting apps instead of a long initialDelaySeconds on liveness. Confidence: 0.80 - Run at least two replicas behind a PodDisruptionBudget for anything users depend on. Confidence: 0.90 - Spread replicas across zones with topologySpreadConstraints. Confidence: 0.80 - Pin images by digest or an immutable version tag, never latest. Confidence: 0.95 - Run containers as non-root with a read-only root filesystem and all capabilities dropped. Confidence: 0.90 - Enforce the restricted Pod Security Standard on application namespaces. Confidence: 0.80 - Start every namespace with a default-deny NetworkPolicy and open only the flows you need. Confidence: 0.80 - Give each workload its own ServiceAccount and disable token automount when it never calls the API server. Confidence: 0.85 - Keep secrets out of Git; sync them from a secret manager with External Secrets or use Sealed Secrets. Confidence: 0.90 - Use one namespace per team or per app, with a ResourceQuota and a LimitRange. Confidence: 0.80 - Apply the standard app.kubernetes.io labels to every resource. Confidence: 0.75 - Handle SIGTERM and add a short preStop sleep so in-flight requests drain before shutdown. Confidence: 0.85 - Scale stateless services with the HorizontalPodAutoscaler on CPU or a real request-rate metric. Confidence: 0.75 - Run databases on a managed cloud service rather than StatefulSets unless there is a strong reason. Confidence: 0.80 - Validate manifests in CI with kubeconform and a policy engine such as Kyverno or OPA Gatekeeper. Confidence: 0.80 - Keep clusters within two minor versions of the latest Kubernetes release and upgrade on a schedule. Confidence: 0.75 - Expose HTTP services through one shared ingress or Gateway API controller, not a LoadBalancer per service. Confidence: 0.75
© f · CC0-1.0 · f/prompts.chat