feat(delivery): scan and sign containers and UDS releases #8
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/workflows!8
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/signed-delivery"
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?
Adds manual, reusable container publishing and UDS bundle build/deploy workflows. Owned images are built into a local archive, scanned with vulnerability, secret, configuration and ClamAV checks, and accompanied by signed scan reports and SBOM evidence uploaded before the registry push. Bundle deployment verifies signed file hashes, source provenance, current image scans, mitigation expiry and the selected cluster context.
Depends on #7; this PR is stacked on feat/security-pipelines. Merge #7 first, then retarget this PR to main. References #5. Runner migration (#2) remains deferred.
Validation: 23 unit tests and scaffold checks pass. Real scanner tests covered clean source, removed secrets in Git history, sanitized reports and downloaded Alpine image archives. Offline signing verified successfully and rejected tampering. No app images or UDS bundles were built, and no cluster deployment was performed.
Owner activation: follow docs/delivery.md to configure runner labels, protected-branch actor allowlists, registry credentials and signing/cluster secrets. Review and merge before running the UI workflows. End-to-end Forgejo publication/deployment remains an owner acceptance step.
kiyi referenced this pull request2026-10-15 10:35:31 -05:00