Revisions for 1.18.0 (additional ingress/gateway examples).

Author: sj-porter-knime

networking/ingress-nginx/images/kots-networking-configuration.png

@@ -37,7 +37,11 @@ Additionally, some EnvoyFilters can be found in `networking/istio/envoyfilter/`
 
 By default the deployment includes an Istio Gateway that uses the correct DNS names and basic TLS configuration. If you need a custom Gateway instead, disable the default one either via Replicated config or with ArgoCD values overrides.
 
-[example-gateway.yaml](example-gateway.yaml) is an example Istio Gateway for KNIME Business Hub. Before applying it, set the gateway metadata namespace to your Hub namespace and replace the example hosts (`hub.example.com`, `apps.example.com`, etc.) with your actual hostnames. If TLS is terminated at the gateway instead of the load balancer, uncomment and configure the TLS section for port 443.
+[ingress-gateway.yaml](ingress-gateway.yaml) is an example Istio Gateway for KNIME Business Hub. Before applying it, set the gateway metadata namespace to your Hub namespace and replace the example hosts (`hub.example.com`, `apps.example.com`, etc.) with your actual hostnames. If TLS is terminated at the gateway instead of the load balancer, uncomment and configure the TLS section for port 443.
+
+## Ingress example
+
+[ingress.yaml](./ingress.yaml) is an example Ingress resource for routing traffic to the Istio Ingress Gateway service. In a KNIME Business Hub installation, all relevant traffic must reach the Istio Ingress Gateway and will be routed properly from that point onward. The example can be further configured to fit your desired ingress strategy.
 
 ## Openshift
 

networking/ingress-nginx/ingress-nginx-values.yaml

@@ -0,0 +1,68 @@
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: knime-business-hub-ingress
+  namespace: knime
+spec:
+  ingressClassName: <ingressclass>
+  rules:
+    - host: <baseurl>
+      http:
+        paths:
+          - path: /
+            pathType: ImplementationSpecific
+            backend:
+              service:
+                name: istio-ingressgateway
+                port:
+                  number: 443
+    - host: api.<baseurl>
+      http:
+        paths:
+          - path: /
+            pathType: ImplementationSpecific
+            backend:
+              service:
+                name: istio-ingressgateway
+                port:
+                  number: 443
+    - host: apps.<baseurl>
+      http:
+        paths:
+          - path: /
+            pathType: ImplementationSpecific
+            backend:
+              service:
+                name: istio-ingressgateway
+                port:
+                  number: 443
+    - host: ws.<baseurl>
+      http:
+        paths:
+          - path: /
+            pathType: ImplementationSpecific
+            backend:
+              service:
+                name: istio-ingressgateway
+                port:
+                  number: 443
+    - host: auth.<baseurl>
+      http:
+        paths:
+          - path: /
+            pathType: ImplementationSpecific
+            backend:
+              service:
+                name: istio-ingressgateway
+                port:
+                  number: 443
+    - host: storage.<baseurl>
+      http:
+        paths:
+          - path: /
+            pathType: ImplementationSpecific
+            backend:
+              service:
+                name: istio-ingressgateway
+                port:
+                  number: 443                                    

networking/ingress-nginx/istio-externalservice.yaml

@@ -1,24 +1,12 @@
 apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
-  name: business-hub-hub
+  name: knime-business-hub-ingress
   namespace: knime
   annotations:
     haproxy.router.openshift.io/timeout: "1800"
 spec:
   ingressClassName: <ingressclass>
-  ## The tls block needs additional configuration if cert-manager or similar
-  ## is used to create and bind certificates in the cluster to specific ingress rules.
-  #tls:
-  #- hosts:
-  #    - <baseurl>
-  #  secretName: <cert-secret-name>
-  #- hosts:
-  #    - api.<baseurl>
-  #  secretName: <cert-secret-name>
-  #- hosts:
-  #    - ws.<baseurl>
-  #  secretName: <cert-secret-name>
   rules:
     - host: <baseurl>
       http: