Change webhook svc from 8443 to webhook-server

Update the GKE docs since we use the name webhook-server
you don't have to update the svc targetPort.

Signed-off-by: Edvin Norling <edvin.norling@xenit.se>

config/webhook/service.yaml

@@ -1,4 +1,3 @@
-
 apiVersion: v1
 kind: Service
 metadata:
@@ -7,7 +6,7 @@ metadata:
 spec:
   ports:
     - port: 443
-      targetPort: 8443
+      targetPort: webhook-server
   selector:
     control-plane: controller-manager
     gatekeeper.sh/operation: webhook

manifest_staging/charts/gatekeeper/templates/gatekeeper-webhook-service-service.yaml

@@ -18,7 +18,7 @@ spec:
   {{- end }}
   ports:
   - port: 443
-    targetPort: 8443
+    targetPort: webhook-server
   selector:
     app: '{{ template "gatekeeper.name" . }}'
     chart: '{{ template "gatekeeper.name" . }}'

manifest_staging/deploy/gatekeeper.yaml

@@ -841,7 +841,7 @@ metadata:
 spec:
   ports:
   - port: 443
-    targetPort: 8443
+    targetPort: webhook-server
   selector:
     control-plane: controller-manager
     gatekeeper.sh/operation: webhook

website/docs/cloud-specific.md

@@ -25,14 +25,6 @@ Two ways of working around this:
         protocol: TCP
     ```
 
-  - update Gatekeeper service manifest spec:
-    - update `targetPort` from `8443` to `443`
-    ```yaml
-    ports:
-    - port: 443
-      targetPort: 443
-    ```
-
 ## Running on OpenShift 4.x
 
 When running on OpenShift, the `nouid` scc must be used to keep a restricted profile but being able to set the UserID.