Skip to content

Commit 19dfc48

Browse files
design-proposal(quota): close the workload paths around the gate before phase 5
The Context, §1 and §7 claimed every workload a tenant can create goes through apps.cozystack.io. Three paths do not, and tenant-quota is the only bound on each today: - cozy:tenant:super-admin:base grants '*' on kubevirt.io/virtualmachines, so a super-admin can create or resize a raw VM outside any reservation; - RestoreJob (admin) restores VMInstance/VMDisk HelmReleases directly through Velero and postRestoreRename, never through the gate; - VMImportTask (admin) has Forklift fill DataVolumes before the VMDisk that adopts them reaches the gate. §7 now makes closing them a phase-5 prerequisite: the super-admin VM grant becomes read-only (a ResourceQuota cannot select pods by owner, so a quota for non-application workloads would be tenant-quota again), restore and import check the pool through pkg/reservation before writing, unowned raw VMs are reported before tenant-quota is deleted, and an e2e allowlist of tenant write verbs keeps the next such path from going unnoticed. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
1 parent 6a2134b commit 19dfc48

1 file changed

Lines changed: 46 additions & 9 deletions

File tree

  • design-proposals/tenant-quota-reservation

0 commit comments

Comments
 (0)