You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 24679bd
Browse filesBrowse the repository at this point in the historyBrowse files
feat(chart): use per-pod emptyDir git scratch when persistence disabled
The relay's git working dir (`BUZZ_GIT_REPO_PATH`) is ephemeral scratch —
reads/writes hydrate repos from object storage per request and repo-name
uniqueness lives in Postgres, so nothing durable lives on this disk.
Before: `persistence.git.enabled: true` mounted a PVC; `false` mounted
*nothing*, leaving the git path pointing at an unmounted directory. And a
single ReadWriteOnce PVC on a Deployment can only attach to one node, so
it cannot back a multi-replica relay across nodes despite the git data
being disposable.
Now: `enabled: false` mounts a per-pod `emptyDir` at the same mountPath —
true per-pod scratch with no shared volume to multi-attach, so the relay
scales to N replicas cleanly. `enabled: true` still renders the PVC
exactly as before (backward compatible).
- deployment.yaml: git-repos volume is always mounted; PVC when enabled,
emptyDir when disabled.
- values.yaml: document both modes; drop the misleading "RWO is fine at
any replicaCount" note (true only for disposability, not scheduling).
- render_test.yaml: assert the emptyDir + no-PVC path at replicaCount=5.
- Chart 0.1.1 -> 0.1.2.
Verified: `helm unittest` 31/31; `helm template` renders emptyDir (0 PVC
docs) when disabled and the PVC when enabled.
Co-authored-by: Tyler Longwell <[email protected]>
Signed-off-by: Tyler Longwell <[email protected]>
0 commit comments