helm: setting for reconciling concurrent clusters

The setting for concurrent clusters is now available in the
helm chart, instead of only as an env var on the operator
deployment. reconcileConcurrentClusters will be applied to the
env var ROOK_RECONCILE_CONCURRENT_CLUSTERS.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit 52393923d1)

Documentation/Helm-Charts/operator-chart.md

@@ -167,6 +167,7 @@ The following table lists the configurable parameters of the rook-operator chart
 | `priorityClassName` | Set the priority class for the rook operator deployment if desired | `nil` |
 | `rbacAggregate.enableOBCs` | If true, create a ClusterRole aggregated to [user facing roles](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles) for objectbucketclaims | `false` |
 | `rbacEnable` | If true, create & use RBAC resources | `true` |
+| `reconcileConcurrentClusters` | Number of clusters the operator reconciles concurrently | `1` |
 | `resources` | Pod resource requests & limits | `{"limits":{"memory":"512Mi"},"requests":{"cpu":"200m","memory":"128Mi"}}` |
 | `revisionHistoryLimit` | The revision history limit for all pods created by Rook. If blank, the K8s default is 10. | `nil` |
 | `scaleDownOperator` | If true, scale down the rook operator. This is useful for administrative actions where the rook operator must be scaled down, while using gitops style tooling to deploy your helm charts. | `false` |

deploy/charts/rook-ceph/templates/deployment.yaml

@@ -57,6 +57,8 @@ spec:
           env:
             - name: ROOK_CURRENT_NAMESPACE_ONLY
               value: {{ .Values.currentNamespaceOnly | quote }}
+            - name: ROOK_RECONCILE_CONCURRENT_CLUSTERS
+              value: {{ .Values.reconcileConcurrentClusters | quote }}
             {{- with .Values.discover }}
             {{- with .toleration }}
             - name: DISCOVER_TOLERATION

deploy/charts/rook-ceph/values.yaml

@@ -44,6 +44,9 @@ unreachableNodeTolerationSeconds: 5
 # -- Whether the operator should watch cluster CRD in its own namespace or not
 currentNamespaceOnly: false
 
+# -- Number of clusters the operator reconciles concurrently
+reconcileConcurrentClusters: 1
+
 # -- Custom pod labels for the operator
 operatorPodLabels: {}