feat: Add Service on top of operators

template/deploy/helm/[[operator]]/templates/deployment.yaml.j2

@@ -48,6 +48,12 @@ spec:
               valueFrom:
                 fieldRef:
                   fieldPath: metadata.annotations['internal.stackable.tech/image']
+            - name: OPERATOR_NAMESPACE
+              valueFrom:
+                fieldRef:
+                  fieldPath: metadata.namespace
+            - name: OPERATOR_SERVICE_NAME
+              value: {{ include "operator.fullname" . }}
             {{- if .Values.kubernetesClusterDomain }}
             - name: KUBERNETES_CLUSTER_DOMAIN
               value: {{ .Values.kubernetesClusterDomain | quote }}

template/deploy/helm/[[operator]]/templates/service.yaml

@@ -0,0 +1,19 @@
+
+---
+apiVersion: v1
+kind: Service
+metadata:
+  # Note(@sbernauer): We could also call the Service something like
+  # "product-operator-conversion-webhook". However, in the future we will have more webhooks, and
+  # it seems like an overkill to have a dedicated Service per webhook.
+  name: {{ include "operator.fullname" . }}
+  labels:
+    {{- include "operator.labels" . | nindent 4 }}
+spec:
+  selector:
+    {{- include "operator.selectorLabels" . | nindent 6 }}
+  ports:
+    - name: conversion-webhook
+      protocol: TCP
+      port: 8443
+      targetPort: 8443