chore(pkg-cache): move the cache to hcloud-volumes #230

Merged
binjovi-bot merged 1 commit from chore/pkg-cache-hcloud into trunk 2026-09-03 20:04:55 +00:00
Owner

Part of emptying Mayastor so its 25.5 cores and 14.8 GiB come back to the fleet.

storageClassName is immutable on a bound claim, so this is a rename, not an edit. Flux creates pkg-cache-hc, the Recreate Deployment picks it up, and prune removes pkg-cache-storage once the old pod releases it. No imperative step is needed, which is why pkg-cache goes early.

Every byte is re-fetchable from upstream, so the empty cache costs one slow build, not data.

The Kustomization health check on the Deployment gates the release: if the pod cannot bind the new claim, the release fails and rolls back. bash tests/check.sh passes.

https://claude.ai/code/session_01MdSbMhzabSbpG8TtP9Ur3H

Part of emptying Mayastor so its 25.5 cores and 14.8 GiB come back to the fleet. `storageClassName` is immutable on a bound claim, so this is a **rename**, not an edit. Flux creates `pkg-cache-hc`, the `Recreate` Deployment picks it up, and prune removes `pkg-cache-storage` once the old pod releases it. No imperative step is needed, which is why pkg-cache goes early. Every byte is re-fetchable from upstream, so the empty cache costs one slow build, not data. The Kustomization health check on the Deployment gates the release: if the pod cannot bind the new claim, the release fails and rolls back. `bash tests/check.sh` passes. https://claude.ai/code/session_01MdSbMhzabSbpG8TtP9Ur3H
chore(pkg-cache): move the cache to hcloud-volumes
All checks were successful
binjovi/ci Binjovi completed the frozen plan
4e073d0cdc
Part of emptying Mayastor so its 25.5 cores and 14.8 GiB come back to
the fleet.

storageClassName is immutable on a bound claim, so this is a rename, not
an edit. Flux creates pkg-cache-hc, the Recreate Deployment picks it up,
and prune removes pkg-cache-storage once the old pod releases it. No
imperative step is needed.

Every byte is re-fetchable from upstream, so the empty cache costs one
slow build, not data. The Kustomization health check on the Deployment
gates the release: if the pod cannot bind the new claim, the release
fails and rolls back.

Claude-Session: https://claude.ai/code/session_01MdSbMhzabSbpG8TtP9Ur3H
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sean/seanfarm!230
No description provided.