ci: define additive k3s debug golden #119
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/k3s-debug-golden-additive"
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?
Outcome
Define a separate
k3s-debug-goldenCI image and debug VM artifact. Existingsim-goldenandnexus-goldenidentities and bytes remain unchanged.Descriptor v2 remains unchanged and closed to its authenticated top-level
source-shabinding plus exactly thesimandnexusgolden-artifact roles. The new artifact stays debug-only until a separate reviewed contract defines signed config-bundle binding, staging, verification, atomic activation, and rollback.The generic image-producer workflow remains exactly 120 minutes. Any future 180-minute debug exception requires a dedicated shared workflow profile whose verifier proves that only a debug candidate materializes the third artifact.
This PR does not define or activate a live
k3s-debugrunner, does not authorize production lookup, and does not change either existing image.Test-first evidence
bash scripts/tests/audit-spoke-ci.test.shpasses.bash scripts/tests/check-release-report.test.shpasses.git diff --checkpasses.Supersedes the rejected interpretation in closed PR #118; it does not reopen or reuse that branch. No merge is authorized by this submission.