Container Registry and Software Supply Chain Platform  ·  View 24 of 33  ·  5 · Operations

Delivery of the Platform Itself

How a change to the platform reaches production, through the platform's own gates.

Editable source SVG draw.io All views
Source Platform Monorepo GitLab Policy Repository Rego + tests Helm Charts Build Tekton self-hosted Unit and Integration Self-attest SBOM + Provenance Cosign Signature same path as tenants Gate Dry-Run Policy last 24 h traffic Bundle Diff Review 2 approvers Deliver Argo CD · development Argo CD · staging Argo CD · production digest pinned Verify Admits its own image SLO Watch 48 h rollback on deny Delivery of the Platform Itself External / third party Application we own Security / platform Decision point failure / alternate The platform is its own first customer: its images pass the same admission control as everything else. v 1.0 · owner Platform Engineering · date 2026-09

Decisions

  • The platform is its own first customer: its images carry provenance and SBOMs and pass the same admission control
  • Policy bundle changes ship through the same pipeline as code, with a dry-run gate and two approvers
  • Argo CD deploys digests, never tags

The bootstrap problem

  • The admission controller cannot deny its own upgrade into an unrecoverable state: it is excluded from its own namespace's policy by an explicit, audited rule
  • That exclusion is the single most sensitive rule in the bundle and is reviewed every release
  • Rollback is by digest, and the previous digest is retained regardless of lifecycle rules

Deliberately omitted

  • Application team pipelines — they are producers, shown in act 4
  • Infrastructure provisioning — outside the platform boundary