fix(backend): Add securitycontext for k8s 1.25 (kubeflow#1132)

For k8s 1.25, a securityContext definition is needed for a pod.
Add proper security context to pipelineloop controler and webhook

Signed-off-by: Yihong Wang <[email protected]>

Signed-off-by: Yihong Wang <[email protected]>

Author: yhwang

manifests/kustomize/third-party/tekton-custom-task/pipeline-loops/500-controller.yaml

@@ -54,3 +54,13 @@ spec:
           value: config-observability
         - name: METRICS_DOMAIN
           value: tekton.dev/pipeline
+        securityContext:
+          allowPrivilegeEscalation: false
+          capabilities:
+            drop:
+            - ALL
+          runAsGroup: 65532
+          runAsNonRoot: true
+          runAsUser: 65532
+          seccompProfile:
+            type: RuntimeDefault

manifests/kustomize/third-party/tekton-custom-task/pipeline-loops/500-webhook.yaml

@@ -64,6 +64,16 @@ spec:
           containerPort: 8008
         - name: https-webhook
           containerPort: 8443
+        securityContext:
+          allowPrivilegeEscalation: false
+          capabilities:
+            drop:
+            - ALL
+          runAsGroup: 65532
+          runAsNonRoot: true
+          runAsUser: 65532
+          seccompProfile:
+            type: RuntimeDefault
 ---
 apiVersion: v1
 kind: Service