Record promoted stable channel and Harbor IaC deployment gates #43
No reviewers
Labels
No labels
app-migration
bug
ci-cd
cluster
Documentation
duplicate
enhancement
gpu
invalid
networking
question
security
Storage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/Documentation!43
Loading…
Reference in a new issue
No description provided.
Delete branch "kiyi/harbor-stable-readiness"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Record the first verified stable-v1 promotion, selecting v1.36.0 through snapshot c025748ca41b6525b2e1f6ab1ed00c95571df0a6 and audit workflow-channel-promotion-v1-r7086. Document owner-selected incremental caller migration, starting with Harbor and its direct Terraform dependencies.
Reconcile Harbor PR #5, Terraform stable-caller PR #10 and PostgreSQL PR #9 source status, preserving check names and embedded image provenance. The owner reconfirmed that state/KMS, the provisioner and all dev runtime resources remain unset. The disposable PostgreSQL provider regression has now passed in exact-head hosted run 36 and the reviewer accepted its specific SQL fix. Distinguish that fixture acceptance from the combined database/storage delivery profile, one runtime writer, live bootstrap and deployment still required. Keep detailed operator steps in the owning private repositories; no credentials or payloads are published.
Validation at
0bc685c: npm run check and npm run build passed; public/private link policy, source diff and native staged Gitleaks 8.30.1 passed. Documentation only; no infrastructure, tag movement or deployment performed.Source-only approval for exact head
0bc685c1e8. Read all three changed Markdown files at that head and reconciled their key status statements against the live workflows #94, Harbor #5 and terraform-modules #9/#10 PR records. The documentation keeps the initial stable-v1 channel promotion distinct from proposed caller adoption; preserves the security-image provenance boundary; and clearly separates the passed disposable PostgreSQL provider fixture from unprovisioned backend/KMS, provisioner, combined DB/storage profile, single writer, signed delivery and live acceptance. No source-level blocker found in this documentation review. This does not independently validate the channel tag/audit object or live infrastructure, and is not merge authorization. Source security and documentation-site checks are still pending on this head; require their exact-head successful results before merge.CI at submission: pending. This is a source-review approval, not a scan verdict; required checks still block merge.