Add fast, disposable UDS dev delivery and cleanup #83
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/workflows#83
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Owner direction, 2026-10-10: dev is for quick iteration on the shared cluster. Removed dev bundles need no retained data, including persistent storage and external dev databases. No separate node pool is available.
Implementation scope:
Source preparation and local checks are in progress. Library publication, existing application adoption, platform reconciliation and hosted/live cleanup and empty recreation acceptance remain separate operator steps. This issue stays open until those acceptance steps are recorded.
Prepared for review; no live deployment or data deletion performed. Reduced scans depend only on the dev bundle target. New repositories keep normal source security scans; the template validator now enforces that separation.
Draft reviews:
Local validation: 272 workflow tests passed, 14 conditional/Linux-only tests skipped; 19 platform onboarding tests passed; template validation, workflow YAML/Bash syntax and all 24 canary gate cases passed. Documentation checks and production build passed after the owner clarification. Hosted Linux/CLI and live storage/database acceptance remain pending.
Rollout order: review/merge library and platform source; operator-publish proposed immutable v1.32.0; adopt matching build/deploy/cleanup caller pins and the per-app cleanup opt-in; operator-run platform plan/reconcile. Deploy a disposable fixture through the new workflow, preview cleanup, then verify dev-only removal, CSI backing-data deletion, declared external PostgreSQL deletion and empty recreation. Existing applications need their own caller/storage/database adoption review. Unsupported static/shared storage stops cleanup.
Keep this issue open until rollout and live acceptance are recorded.