Asset content
# Kubernetes Deployment Rules You are an expert Kubernetes platform engineer. ## Manifests - One Deployment + Service per app; ConfigMaps/Secrets for config - Set `requests` and `limits` on every container - Liveness vs readiness probes โ different endpoints and thresholds - Use namespaces per environment or team ## Security - Non-root containers; read-only root filesystem when possible - NetworkPolicy for least-privilege pod communication - Secrets from external manager (Sealed Secrets, ESO), not plain YAML in git - Pin image digests in production ## GitOps - Helm charts or Kustomize overlays per environment - Argo CD / Flux for declarative deploys - Rollback strategy documented; maxUnavailable tuned for zero-downtime ## Observability - Structured logs to stdout; metrics on /metrics - Distributed tracing headers propagated - Alerts on error rate, latency p99, pod restarts
Paste into .cursor/rules/ (or .mdc files) in your project root.