Record signed controller build and current RKE2 delivery blockers #54
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!54
Loading…
Reference in a new issue
No description provided.
Delete branch "kiyi/rke2-delivery-progress"
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?
Reconcile all four RKE2 status pages with verified private Platform results. Controller build 5004 published signed
rke2-controller-bundle-v0.1.0-r7636; deploys 5005/5007 stopped at adoption/UDS delivery. Workflows #114 is now merged and released/promoted inv1.44.0, and private Platform #132 is merged. Record the exact channel binding separately from the owning source commit.Fresh controller deploy 5012 exercised automatic signed release selection and passed scans, 77 required/14 forbidden permission probes, init 0.73.0 and ownership preflight. UDS archive deployment failed with
kubernetes_authorization; session revocation passed. The denied operation, partial deployment and controller acceptance remain unverified. Workflows #115 prepares safe permission summaries; review/release/promotion and a separately approved retry remain pending.Plan build 5006 separately failed on 28 blocking findings in the Rancher upgrade image and published no Plan bundle. Preserve successful bootstrap/routine identity/temporary-role retirement evidence and the owner-selected upgrade order. Detailed procedures remain in owning repositories; public pages contain no private repository links or secret values.
Validation at head
7842245:npm run check,npm run build(default Turbopack), diff checks and the active Gitleaks 8.30.1 hook passed. Documentation only; no runtime configuration, manual Actions dispatch or deployment changes.Reviewed the four changed documentation pages at exact head
2e1a65746e. The controller signed-build record distinguishes publication from failed UDS archive deployment, leaves root cause/partial state/acceptance unverified, and keeps the Rancher Plan-image vulnerability gate separate from the controller/helper image scans. Proposed release selection is labeled pending; installed init/Core baselines and the owner-selected upgrade order remain consistent across pages. Documentation only: no deployment resources, routing, admission policy, or scan gates change. Forgejo did not supply file patch hunks, so this verdict rests on authenticated exact-head full-file source inspection rather than reconstructed base-to-head diffs. Source review approved; pending source-security and site checks remain independent merge gates, and private deployment-run facts were not independently revalidated here.CI at submission: pending. This is a source-review approval, not a scan verdict; required checks still block merge.
Reviewed the four changed documentation files at exact head
7842245dd4. The newly recorded workflows v1.44.0 channel binding and Platform #132 merge are distinguished from the owning controller deploy 5012: signed-release selection, scans, permissions, init and ownership preflight passed, but UDS archive delivery failed with kubernetes_authorization; denied operation, partial state and controller acceptance are explicitly unverified. Plan build 5006's separate Rancher upgrade-image blockers and absence of a published Plan bundle remain explicit. The bootstrap/routine-identity and temporary-role-retirement history and owner-selected upgrade order are preserved. Documentation only: no UDS resources, gateways/routes, admission policy or required scan gates are modified. Forgejo supplied no patch hunks, so this verdict uses authenticated full-file inspection at this head, not a reconstructed diff; the private deployment logs and reported local validation were not independently rerun. Source approved. Current source-security and site checks remain pending independent merge gates; this is not deployment or scan acceptance.CI at submission: pending. This is a source-review approval, not a scan verdict; required checks still block merge.