apiVersion: helm-expt.confighub.com/v1alpha1 kind: ProductionSupportDecision metadata: name: "bitnami-mysql-static-passwords-public-oci-supported" spec: chart: "bitnami/mysql" version: "14.0.3" decision: supported decisionDate: "2026-06-09" supportedSince: "2026-06-08T17:46:04Z" supportedBase: "static-passwords" targetScope: clusterClass: cub-lk-kind-vanilla namespace: "mysql" deliveryPath: confighub-oci gitopsController: argo lastEvidenceAt: "2026-06-08T17:46:04Z" lastEvidenceTarget: helm-expt-parity-mysql-mq5i5crp-1sge-cluster/oci lastEvidenceKubeContext: kind-helm-expt-parity-mysql-mq5i5crp-1sge liveEvidenceTTL: 30d storageAssumptions: - "The supported base uses the chart's default primary StatefulSet PVC posture for the public proof scope; production storage class, backup, restore, failover, and rollback need separate target decisions." networkAssumptions: - "Use the service behavior recorded by the supported scope unless a narrower scope is separately reviewed." requiredTargetFacts: [] supportBoundary: includes: - "bitnami/mysql@14.0.3 static-passwords base" - ConfigHub OCI delivery through Argo for the declared cub-lk vanilla kind target scope - rendered MySQL StatefulSet, Service, PVC, PDB, generated Secret, 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 - generated MySQL root password bound before render, rendered deterministically, and separated by cub installer output - recorded PDB warning acceptance and no-hooks lifecycle policy for the declared public proof scope excludes: - "existing-secret unless separately reviewed for target credential presence, custody, and rotation policy" - "replication, backup, restore, point-in-time recovery, failover, credential rotation, and storage-class/SLO policy unless separately reviewed" - "private values overlays, wrapper charts, and populated extension slots unless separately reviewed" - "init scripts, custom configuration, external credentials, resource-hardened, storage-hardened, or customer production bases unless separately reviewed" - "non-vanilla Kubernetes distributions unless separately reviewed" - "other delivery controllers or target scopes unless separately reviewed" decisions: imageDecision: state: "mutable-image-exception-accepted-for-target-scope" detail: "rendered MySQL image tags are mutable, with registry digest-resolution evidence recorded for this public proof scope; stricter environments should use digest-pinned bases or image overrides" scanDecision: state: "pdb-policy-accepted-for-target-scope" detail: "the chart PDB warning is accepted only for the declared public proof scope; target production deployments should choose an availability policy" lifecycleDecision: state: "lifecycle-observed-for-proof-scope" detail: "the static-passwords base has no Helm hooks and reaches readiness through regular Helm, cub installer apply, and ConfigHub OCI/Argo" targetFactDecision: state: "no-unresolved-target-prerequisite-in-candidate-base" detail: "no unresolved target prerequisite in candidate base" liveEvidenceDecision: state: "fresh-target-evidence-passed" detail: "fresh target-scoped ConfigHub OCI and Argo evidence passed on 2026-06-08 for the declared cub-lk vanilla kind MySQL static-passwords scope" evidence: - path: "recipes/bitnami/mysql/14.0.3/revisions/static-passwords/r001/receipts/helm-equivalence-receipt.yaml" claim: "The candidate base is Helm-equivalent under recorded inputs." - path: "recipes/bitnami/mysql/14.0.3/revisions/static-passwords/r001/receipts/scan-receipt.yaml" claim: "The rendered-object scan receipt exists for the candidate base." - path: "runs/live-kind-parity/bitnami-mysql-static-passwords/receipt.yaml" claim: "The two-cluster Helm-vs-installer parity receipt exists for the candidate base." - path: "runs/live-helm-confighub-compare/bitnami-mysql-static-passwords/receipt.yaml" claim: "The selected live Helm-vs-ConfigHub comparison receipt exists for the candidate base." - path: "data/production-support-decisions/bitnami-mysql/fresh-target-evidence-2026-06-08.yaml" claim: "Fresh target-scoped ConfigHub OCI and Argo evidence passed for the declared cub-lk vanilla kind support scope." - path: "data/image-digest-workdown/receipts/bitnami-mysql/static-passwords/image-digest-resolution.yaml" claim: "Registry digest resolution exists for the rendered static-passwords MySQL image reference." - path: "data/production-support-decisions/bitnami-mysql/image-policy-decision.yaml" claim: "The target-scoped image policy decision records the mutable-image exception and digest-resolution evidence." - path: "data/production-support-decisions/bitnami-mysql/security-decision.yaml" claim: "The target-scoped security decision accepts the static-passwords PDB warning shape only for this public proof scope." - path: "data/production-support-decisions/bitnami-mysql/lifecycle-decision.yaml" claim: "The target-scoped lifecycle decision binds no-hooks policy, generated credential ownership, separated Secret handling, storage boundaries, and OCI/Argo runtime health to proof-scope evidence." - path: "data/production-disposition/receipts/bitnami-mysql/generated-fact-ownership.yaml" claim: "The generated fact ownership receipt exists for this chart." - path: "data/production-disposition/receipts/bitnami-mysql/hook-and-lifecycle-phase-policy.yaml" claim: "The hook and lifecycle phase policy receipt exists for this chart." - path: "data/production-disposition/receipts/bitnami-mysql/scan-gate-warning-disposition.yaml" claim: "The scan gate warning disposition receipt exists for this chart." - path: "data/production-disposition/receipts/bitnami-mysql/storage-backup-restore-and-rollback-policy.yaml" claim: "The storage backup restore and rollback policy receipt exists for this chart." - path: "data/production-disposition/receipts/bitnami-mysql/target-fact-preflight.yaml" claim: "The target fact preflight receipt exists for this chart." requiredBeforeFinal: [] nextAction: "Keep the target-scoped evidence fresh before using this supported scope as a production-support example; create separate existing-secret, backup/restore, failover, credential-rotation, storage-class, SLO, or resource-hardened bases for real customer MySQL workloads."