metrics-server/metrics-server@3.13.0 Production Support Workdown

This generated page is a human workdown for one target-scoped production support decision. It does not replace the source decision artifact:

support-decision.yaml

Current Decision

Open Work

Closeout Sequence

1. Keep the target-scoped evidence fresh for the declared support boundary.

Required Before Final Support

• None.

Support Boundary

Included:

• metrics-server/metrics-server@3.13.0 default base
• ConfigHub OCI delivery through Argo for the declared cub-lk vanilla kind target scope
• rendered Metrics Server Deployment, Service, APIService, cluster RBAC, labels, gates, receipts, and support objects produced by the recorded base
• mutable-image exception backed by registry digest-resolution evidence for the rendered image references
• recorded resource-warning acceptance, cluster RBAC review, no-hooks lifecycle policy, APIService availability, and metrics API observation for the declared public proof scope

Excluded:

• external-tls-ca unless separately reviewed with target certificate-chain evidence
• private values overlays, wrapper charts, and populated extension slots unless separately reviewed
• resource-hardened, RBAC-hardened, API aggregation hardened, custom TLS, or customer production bases unless separately reviewed
• non-vanilla Kubernetes distributions unless separately reviewed
• other delivery controllers or target scopes unless separately reviewed

Evidence

• recipes/metrics-server/metrics-server/3.13.0/revisions/default/r001/receipts/helm-equivalence-receipt.yaml - The candidate base is Helm-equivalent under recorded inputs.
• recipes/metrics-server/metrics-server/3.13.0/revisions/default/r001/receipts/scan-receipt.yaml - The rendered-object scan receipt exists for the candidate base.
• runs/live-kind-parity/metrics-server-metrics-server-default/receipt.yaml - The two-cluster Helm-vs-installer parity receipt exists for the candidate base.
• runs/live-helm-confighub-compare/metrics-server-metrics-server-default/receipt.yaml - The selected live Helm-vs-ConfigHub comparison receipt exists for the candidate base.
• data/runtime-gitops/receipts/metrics-server-metrics-server/default/latest.yaml - The runtime/GitOps receipt records APIService Available=True and kubectl top nodes returning metrics for the default base.
• data/production-support-decisions/metrics-server-metrics-server/fresh-target-evidence-2026-06-05.yaml - Fresh target-scoped ConfigHub OCI and Argo evidence passed for the declared cub-lk vanilla kind support scope.
• data/image-digest-workdown/receipts/metrics-server-metrics-server/default/image-digest-resolution.yaml - Registry digest resolution exists for the rendered default Metrics Server image reference.
• data/production-support-decisions/metrics-server-metrics-server/image-policy-decision.yaml - The target-scoped image policy decision records the mutable-image exception and digest-resolution evidence.
• data/production-support-decisions/metrics-server-metrics-server/security-decision.yaml - The target-scoped security decision accepts the default resource-warning shape only for this public proof scope.
• data/production-support-decisions/metrics-server-metrics-server/lifecycle-decision.yaml - The target-scoped lifecycle decision binds no-hooks policy, cluster RBAC, APIService observation, metrics API proof, and OCI/Argo runtime health to proof-scope evidence.
• data/production-disposition/receipts/metrics-server-metrics-server/cluster-rbac-review.yaml - The cluster rbac review receipt exists for this chart.
• data/production-disposition/receipts/metrics-server-metrics-server/generated-fact-ownership.yaml - The generated fact ownership receipt exists for this chart.
• data/production-disposition/receipts/metrics-server-metrics-server/hook-lifecycle-phase-policy.yaml - The hook lifecycle phase policy receipt exists for this chart.
• data/production-disposition/receipts/metrics-server-metrics-server/scan-gate-warning-disposition.yaml - The scan gate warning disposition receipt exists for this chart.
• data/production-disposition/receipts/metrics-server-metrics-server/target-fact-preflight.yaml - The target fact preflight receipt exists for this chart.

Next Action

Keep the target-scoped evidence fresh before using this supported scope as a production-support example; create separate external-tls-ca, resource-hardened, RBAC-hardened, API aggregation hardened, digest-pinned, or customer production bases for real Metrics Server workloads.

Regenerate:

npm run production:support-decisions
npm run production:support-decisions:verify