From 1bf2724c4b764fbd0536c8a177cf8edbff0c0657 Mon Sep 17 00:00:00 2001 From: chrislu Date: Sat, 6 Dec 2025 11:51:03 -0800 Subject: [PATCH] helm: clarify updateStrategy multi-replica behavior Expand comment to warn users that RollingUpdate with multiple replicas requires shared storage (ReadWriteMany) to avoid data loss. --- k8s/charts/seaweedfs/values.yaml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/k8s/charts/seaweedfs/values.yaml b/k8s/charts/seaweedfs/values.yaml index 697562afb..1d90da8f5 100644 --- a/k8s/charts/seaweedfs/values.yaml +++ b/k8s/charts/seaweedfs/values.yaml @@ -1118,7 +1118,10 @@ allInOne: # Update strategy configuration # type: Recreate or RollingUpdate - # For single replica, Recreate is recommended to avoid data conflicts + # For single replica, Recreate is recommended to avoid data conflicts. + # For multiple replicas with RollingUpdate, you MUST use shared storage + # (e.g., data.type: persistentVolumeClaim with ReadWriteMany access mode) + # to avoid data loss or inconsistency between pods. updateStrategy: type: Recreate