Add helm variable for Role Labels (#367)

Provide option for users to specify Role labels in helm values 

This is useful when using [k8s clusterRole aggregation](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#aggregated-clusterroles)
We can use aggregation rule labels to give other applications access to ack resources (Eg: Kubeflow in our case)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Author: akartsky

templates/helm/templates/_controller-role-kind-patch.yaml.tpl

@@ -4,10 +4,18 @@ kind: ClusterRole
 metadata:
   creationTimestamp: null
   name: ack-{{ .ServicePackageName }}-controller
+  labels:
+  {{ "{{- range $key, $value := .Values.role.labels }}" }}
+    {{ "{{ $key }}: {{ $value | quote }}" }}
+  {{ "{{- end }}" }}
 {{ "{{ else }}" }}
 kind: Role
 metadata:
   creationTimestamp: null
   name: ack-{{ .ServicePackageName }}-controller
+  labels:
+  {{ "{{- range $key, $value := .Values.role.labels }}" }}
+    {{ "{{ $key }}: {{ $value | quote }}" }}
+  {{ "{{- end }}" }}
   namespace: {{ "{{ .Release.Namespace }}" }}
 {{ "{{ end }}" }}

templates/helm/values.schema.json

@@ -65,6 +65,14 @@
       ],
       "type": "object"
     },
+    "role": {
+      "description": "Role settings",
+      "properties": {
+        "labels": {
+	  "type": "object"
+	}
+      }
+    },
     "metrics": {
       "description": "Metrics settings",
       "properties": {

templates/helm/values.yaml.tpl

@@ -28,6 +28,10 @@ deployment:
   # Which priorityClassName to set?
   # See: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority
   priorityClassName: ""
+
+# If "installScope: cluster" then these labels will be applied to ClusterRole
+role:
+ labels: {}
 
 metrics:
   service: