Record security tool image decision and staged adoption #38
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/Documentation!38
Loading…
Reference in a new issue
No description provided.
Delete branch "kiyi/security-runtime"
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 owner’s 2026-10-11 decision to bake released workflows v1.33.0 and verified tools into a dedicated security job image. Document the review, independent signed publication, next workflow release, caller adoption and rollback sequence, with actual embedded-library provenance and fresh scan databases preserved.
Implementation: Homelab/base-images#40 and Homelab/workflows#87. Tracking remains open in Homelab/base-images#39 and Homelab/workflows#86, both in Roadmap Review. Public documentation links the public workflow procedure at its verified commit; private implementation references remain plain text.
Validation: npm run check and npm run build passed with the exact locked dependencies; git diff --check passed and the public diff was reviewed for secret values.
This records prepared source, not signed image publication, caller adoption, live deployment or measured performance improvements.
Reviewed the two-page documentation diff at
cda3520: it correctly distinguishes prepared source from signed image publication, workflow release, caller adoption, deployment and measured savings; documentation checks are green. Keep this as a decision/sequence record, not readiness evidence. At the time of this review, base-images #40 hosted run 181 still fails compiling Trivy (parser/parameter.go: undefined: json.SkipFunc), and workflows #87 depends on an accepted signed image. Neither image acceptance nor Harbor deployment is established by this docs PR. No documentation-only blocker.