From c8ac4a21057ee74aa7169180e577845d747f883a Mon Sep 17 00:00:00 2001 From: larssb Date: Mon, 6 Oct 2025 19:45:44 +0000 Subject: [PATCH] Use OnRootMismatch for fsGroupChangePolicy to avoid prolonged Pod upstart 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 --- script/helm/garage/values.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/script/helm/garage/values.yaml b/script/helm/garage/values.yaml index bc1f8f7a..f650d612 100644 --- a/script/helm/garage/values.yaml +++ b/script/helm/garage/values.yaml @@ -117,6 +117,7 @@ podSecurityContext: runAsUser: 1000 runAsGroup: 1000 fsGroup: 1000 + fsGroupChangePolicy: "OnRootMismatch" runAsNonRoot: true securityContext: