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
MP+: utilize ReadWriteMany volumes for repository cache #476
So far, we've been using only block storage (AWS EBS), which can't be accessed in ReadWriteMany mode.
Because of that, we need to have one repository cache for each worker - see #210
On MP+ we can also use AWS EFS file storage (basically NFS - network file system) which can be accessed in ReadWriteMany mode.
Hence, after we have both, stg & prod on MP+, we can consolidate all the RWO worker volumes (1+1 per long-running worker) we use for the repository cache into one(?) RWX.
And we can change workers from StatefulSet to Deployment at the same time, I guess.
Benefit
The long-running workers will use significantly less disk space (1 volume instead of 4 for 2 l-r workers)
Importance
gain/low, impact/low
Workaround
There is an existing workaround that can be used until this feature is implemented.
Participation
I am willing to submit a pull request for this issue. (Packit team is happy to help!)
We are still deploying one PVC per worker, so this is still relevant. But the cache itself isn't really utilised, so if we disabled it (or possibly even remove the related code), we can drop this issue.
Activity
[-]Worker & sandcastle: utilize ReadWriteMany volumes[/-][+]MP+: utilize ReadWriteMany volumes for repository cache[/+]nforro commentedon Nov 14, 2024
Still relevant.
lbarcziova commentedon Jan 23, 2026
We are still deploying one PVC per worker, so this is still relevant. But the cache itself isn't really utilised, so if we disabled it (or possibly even remove the related code), we can drop this issue.