fix(argo-events): add managed namespace configuration

Signed-off-by: Carlos Oliveira <ceguimaraes@gmail.com>

charts/argo-events/README.md

@@ -127,6 +127,7 @@ done
 | controller.podLabels | object | `{}` | Labels to be added to events controller pods |
 | controller.priorityClassName | string | `""` | Priority class for the events controller pods |
 | controller.rbac.enabled | bool | `true` | Create events controller RBAC |
+| controller.rbac.managedNamespace | string | `""` | Additional namespace to be monitored by the controller |
 | controller.rbac.namespaced | bool | `false` | Restrict events controller to operate only in a single namespace instead of cluster-wide scope. |
 | controller.rbac.rules | list | `[]` | Additional user rules for event controller's rbac |
 | controller.readinessProbe.failureThreshold | int | `3` | Minimum consecutive failures for the [probe] to be considered failed after having succeeded |

charts/argo-events/templates/argo-events-controller/deployment.yaml

@@ -48,6 +48,10 @@ spec:
         {{- if .Values.controller.rbac.namespaced }}
         - --namespaced
         {{- end }}
+        {{- if .Values.controller.rbac.managedNamespace }}
+        - --managed-namespace
+        - {{ .Values.controller.rbac.managedNamespace }}
+        {{- end }}
         {{- with .Values.controller.containerSecurityContext }}
         securityContext:
           {{- toYaml . | nindent 10 }}

charts/argo-events/values.yaml

@@ -138,6 +138,8 @@ controller:
     enabled: true
     # -- Restrict events controller to operate only in a single namespace instead of cluster-wide scope.
     namespaced: false
+    # -- Additional namespace to be monitored by the controller
+    managedNamespace: ""
     # -- Additional user rules for event controller's rbac
     rules: []