UPSTREAM: <carry>: SSC RBAC

After reducing the RBAC granted to the OLM ServiceAccount in an earlier
commit, this commit introduces RBAC so pods that use the OLM
ServiceAccount will qualify to use the restricted-v2 SCC.

Signed-off-by: Alexander Greene <[email protected]>

Author: awgreene

manifests/0000_50_olm_01-olm-operator.serviceaccount.yaml

@@ -22,6 +22,14 @@ rules:
     verbs: ["*"]
   - nonResourceURLs: ["*"]
     verbs: ["*"]
+  - apiGroups:
+      - security.openshift.io
+    resources:
+      - securitycontextconstraints
+    resourceNames:
+      - restricted-v2
+    verbs:
+      - use
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding

scripts/generate_crds_manifests.sh

@@ -87,6 +87,7 @@ add_ibm_managed_cloud_annotations() {
 }
 
 ${YQ} merge --inplace -d'*' manifests/0000_50_olm_00-namespace.yaml scripts/namespaces.patch.yaml
+${YQ} merge --inplace --arrays=append -d'1' manifests/0000_50_olm_01-olm-operator.serviceaccount.yaml scripts/olm-service.patch.yaml
 ${YQ} merge --inplace -d'0' manifests/0000_50_olm_00-namespace.yaml scripts/monitoring-namespace.patch.yaml
 ${YQ} write --inplace -s scripts/olm-deployment.patch.yaml manifests/0000_50_olm_07-olm-operator.deployment.yaml
 ${YQ} write --inplace -s scripts/catalog-deployment.patch.yaml manifests/0000_50_olm_08-catalog-operator.deployment.yaml

scripts/olm-service.patch.yaml

@@ -0,0 +1,9 @@
+rules:
+  - apiGroups:
+    - security.openshift.io
+    resources:
+    - securitycontextconstraints
+    resourceNames:
+    - restricted-v2
+    verbs:
+    - use