Repository navigation
feat(arc): persistent /cache volume for unprivileged job containers - #4586
Merged
Merged
Conversation
Renovate on the in-cluster runner was ~2.5x slower than GitHub-hosted (348s vs 132-152s) because every run started cold over the WAN: fresh clone, tool downloads, all registry lookups. Mount an RWX cephfs PVC at /cache in every job-container pod (hook template) with fsGroup 1001 so it is writable, letting workflows keep state between runs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a persistent
/cachevolume (RWX cephfs PVCdapper-cluster-unprivileged-cache, 20Gi) to every job-container pod on the unprivileged runner set, through the hook template. It also sets podfsGroup: 1001(OnRootMismatch) so the uid-1001 job can write to it.Why
In-cluster Renovate (dry run 41946456740) took 348s versus 132–152s on
ubuntu-latest. Every phase was network-bound, because each run starts cold over the home WAN:With state kept in
/cache, Renovate (#4585) can persist its clone (persistRepoData), repository cache, package cache and containerbase tool downloads. Later runs then fetch only deltas. GitHub-hosted runners can never stay warm like that.Only affects job pods on
dapper-cluster-unprivileged(Renovate, still on a test branch). Workflows use their own subdirectory, e.g./cache/renovate.Validation
flate test all: 298 passedci/renovate-unprivileged-runner(cold, then warm) and compare timings