Keep BuildKit on the copied cache after worker evacuation #566
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/arm-cache-evacuation-20260910"
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?
The ARM canary replaces the worker that held the native BuildKit cache. Copy the stopped cache through ZFS snapshots to a bound PVC on a surviving worker, then keep that PVC in the declared deployment. Source and destination final snapshot IDs match. Retain the old data for recovery.
Validation: cache wiring guard passes; it now verifies that the mounted claim is declared with the correct storage class instead of fixing the claim name.