Merge pull request #2220 from PhanLe1010/2152_upgrade_engine_automatically_chart_update

chart: add concurrent-automatic-engine-upgrade-per-node-limit setting

chart/questions.yml

@@ -429,6 +429,13 @@ Warning: This option works only when there is a failed replica in the volume. An
     group: "Longhorn Default Settings"
     type: boolean
     default: "true"
+  - variable: defaultSettings.concurrentAutomaticEngineUpgradePerNodeLimit
+    label: Concurrent Automatic Engine Upgrade Per Node Limit
+    description: "This setting controls how Longhorn automatically upgrades volumes' engines to the new default engine image after upgrading Longhorn manager. The value of this setting specifies the maximum number of engines per node that are allowed to upgrade to the default engine image at the same time. If the value is 0, Longhorn will not automatically upgrade volumes' engines to default version."
+    group: "Longhorn Default Settings"
+    type: int
+    min: 0
+    default: 0
 - variable: persistence.defaultClass
   default: "true"
   description: "Set as default StorageClass for Longhorn"

chart/templates/default-setting.yaml

@@ -36,3 +36,4 @@ data:
     system-managed-pods-image-pull-policy: {{ .Values.defaultSettings.systemManagedPodsImagePullPolicy }}
     allow-volume-creation-with-degraded-availability: {{ .Values.defaultSettings.allowVolumeCreationWithDegradedAvailability }}
     auto-cleanup-system-generated-snapshot: {{ .Values.defaultSettings.autoCleanupSystemGeneratedSnapshot }}
+    concurrent-automatic-engine-upgrade-per-node-limit: {{ .Values.defaultSettings.concurrentAutomaticEngineUpgradePerNodeLimit }}

chart/values.yaml

@@ -94,7 +94,7 @@ defaultSettings:
   systemManagedPodsImagePullPolicy: ~
   allowVolumeCreationWithDegradedAvailability: ~
   autoCleanupSystemGeneratedSnapshot: ~
-
+  concurrentAutomaticEngineUpgradePerNodeLimit: ~
 privateRegistry:
   registryUrl: ~
   registryUser: ~