-
Bug
-
Resolution: Done-Errata
-
Normal
-
OSSM 2.4.5
-
None
-
False
-
None
-
False
-
-
-
`istio-ingressgateway` created in different than control-plane namespace has a warning in proxy status check.
This happens because when `istio-ingressgateway` is deployed in different namespace that 'istio-system', in this case it is istio-ingress, deployed according to https://docs.openshift.com/container-platform/4.14/service_mesh/v2x/ossm-traffic-manage.html#ossm-automatic-gateway-injection_traffic-management, for automatic geteway injection the Deployment contains [sidecar.istio.io/inject=](http://sidecar.istio.io/inject=)"true" as required in the doc. But in that case, when sidecar is injected into istio-ingressgateway pod, Kiali starts checking proxy status for that pod and shows warning on workload RDS: NOT_SENT, which is fine, just that warning is not shown for istio-system gateway istio-ingressgateway generated by SMCP because the sidecars are not injected on that pod.
Expected Behavior:
For those Workloads and Pods which are Gateway, Kiali should skip the proxy status check.
No warning message of workload `istio-ingressgateway` in istio-ingress namespace.
- links to
-
RHBA-2024:129958 Red Hat OpenShift Service Mesh Containers for 2.5.1