Use OnRootMismatch for fsGroupChangePolicy to avoid prolonged Pod upstart

mirror of https://github.com/deuxfleurs-org/garage.git synced 2026-07-26 16:08:13 +00:00

When not used. Especially with a lot of small files on the PVC's Garage uses/is configured with,
Pod upstart time can get quite extreme. For more context see a very good description
of the issues and the technical intricacies behind it here: https://github.com/longhorn/longhorn/issues/2131#issuecomment-778897129

I think it's sane to have fsGroupChangePolicy at "OnRootMismatch" as Garage is an S3 system and thereby
is likely to process a lot of files. And somewhat likely that many of these will be small files as well.

---

Using `fsGroupChangePolicy: "OnRootMismatch"` in my env. changed the Garage Pod upstart. E.g. in an
upgrade case from 5-7minutes ( around 50GB of data ). Many small files though. To 1-15sec.

Thank you.

Signed-off-by: larssb <larssb@noreply.localhost>

This commit is contained in:

larssb

2025-10-06 19:45:44 +00:00

parent 6c740ff05c

commit c8ac4a2105

1 changed files with 1 additions and 0 deletions

									
										script/helm/garage/values.yaml
									
		+1
		
												View File
												
				@@ -117,6 +117,7 @@ podSecurityContext:

				  runAsUser: 1000

				  runAsGroup: 1000

				  fsGroup: 1000

				  fsGroupChangePolicy: "OnRootMismatch"

				  runAsNonRoot: true

				securityContext: