Details
-
Bug
-
Resolution: Done-Errata
-
Normal
-
OSSM 2.3.2
-
False
-
None
-
False
-
Release Notes
-
A `routeConfig` block can now be added to each `additionalIngress` gateway. This allows the creation of OpenShift routes to be enabled (default) or disabled for each gateway.
Description
Disabling .spec.gateways.ingress.routeConfig in the SMCP does not prevent the creation of routes for additional ingress gateways:
spec:
gateways:
additionalIngress:
test-ingress:
enabled: true
namespace: extra-routes
service:
externalName: test-ingress
metadata:
labels:
app: test
ports:
- name: http
port: 80
protocol: TCP
targetPort: 8080
type: ClusterIP
ingress:
routeConfig:
enabled: false
openshiftRoute:
enabled: false
The ingress pod is correctly created in the namespace:
❯ oc get pods -n extra-routes NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES nginx-ingress-6f5b5b79f-sjkk5 1/1 Running 0 6s 10.129.2.29 ocp411-gzz9s-worker-fg65j <none> <none>
But a route is created as well:
❯ oc get route -n istio-system NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD grafana grafana-istio-system.apps.ocp411.ocptest.xyz grafana <all> reencrypt/Redirect None jaeger jaeger-istio-system.apps.ocp411.ocptest.xyz jaeger-query https-query reencrypt None prometheus prometheus-istio-system.apps.ocp411.ocptest.xyz prometheus <all> reencrypt/Redirect None ❯ oc get route -n extra-routes NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD nginx-ingress nginx-ingress-extra-routes.apps.ocp411.ocptest.xyz nginx-ingress 8080 None
Either no routes should be created at all when setting .spec.gateways.ingress.routeConfig to false, or new parameters need to be set to have the ability of disabling the creation of routes for the additionalIngress
Attachments
Issue Links
- links to
-
RHBA-2023:121906
Red Hat OpenShift Service Mesh Containers for 2.4.4
- mentioned on
