← Todas las plantillas

Todo en Git, límites de recursos en cada pod, service accounts con el mínimo privilegio.

Constitution — Kubernetes platform

Version 1.0.0 · Ratified 2026-11-10

These principles hold for every spec, plan and task of the platform. A spec may add rules; it never weakens these.

  1. Everything in Git. Every manifest, Helm values file and cluster setting lives in Git and is applied by a GitOps controller (Argo CD or Flux). kubectl apply or kubectl edit by hand on a shared cluster is not allowed, and the controller reverts drift.

  2. Resource limits on every pod. Every container declares CPU and memory requests and a memory limit, enforced by a LimitRange and an admission policy. A workload without them is rejected by the cluster, not only in review.

  3. Least-privilege service accounts. Each workload has its own service account with a Role that lists only the verbs and resources it uses; automountServiceAccountToken is off where the API is not needed. No workload is bound to cluster-admin.

  4. Health checks and disruption budgets. Every deployment has readiness and liveness probes, at least two replicas when it serves traffic, and a PodDisruptionBudget. Node upgrades never take a service fully down.

  5. Restricted pod security. Namespaces enforce the Pod Security restricted profile: non-root, read-only root filesystem where possible, no privilege escalation and dropped capabilities. Exceptions are listed in the plan with a reason.

  6. Network is denied by default. Each namespace starts with a default-deny NetworkPolicy, and allowed traffic is declared per workload. A service reachable from everywhere fails the review.

  7. Charts are versioned and linted. Helm charts are versioned, pass helm lint and a schema check (kubeconform) in CI, and images are referenced by digest or immutable tag, never latest.

  8. Secrets never sit in Git in clear. Secrets come from an external secret manager through External Secrets or Sealed Secrets. A plain Secret manifest with data in Git fails CI.