-
Bug
-
Resolution: Done
-
Major
-
1.5.0
-
Serverless Sprint 181
After updating Serverless 1.5 automatically in OCP 4.3.1, existing Istio pods in knative-serving-ingress namespace still remain as an attached screenshot. According to the attached logs, it keeps failing at Operation cannot be fulfilled on knativeservings.operator.knative.dev continuously.
In these circumstances, I'm not sure which component(Istio or Kourier) will process ingress traffic.
Expected Result: All Istio pods should be terminated automatically.