Skip to content

MP+: utilize ReadWriteMany volumes for repository cache #476

Open

Description

@jpopelka

Description

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!)

Activity

  1. added
    area/generalNot tied to a specific area
    gain/lowDoesn't bring much value to users
    impact/lowAffects only few of the users
    kind/internalTask that doesn't affect users directly
    on Apr 20, 2023
  2. moved this from new to backlog in Packit Kanban Boardon Apr 20, 2023
  3. changed the title [-]Worker & sandcastle: utilize ReadWriteMany volumes[/-] [+]MP+: utilize ReadWriteMany volumes for repository cache[/+] on Apr 21, 2023
  4. nforro commented on Nov 14, 2024

    @nforro
    Member

    Still relevant.

  5. lbarcziova commented on Jan 23, 2026

    @lbarcziova
    Member

    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.

  6. removed their assignment
    on Jan 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/generalNot tied to a specific areacomplexity/single-taskRegular task; should be done within daysgain/lowDoesn't bring much value to usersimpact/lowAffects only few of the userskind/internalTask that doesn't affect users directly

    Type

    No type

    Projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions