Uploaded image for project: 'Knative Serving'
  1. Knative Serving
  2. SRVKS-455

Existing Istio components aren't removed after Serverless 1.5 update automatically

XMLWordPrintable

    • 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.

              Unassigned Unassigned
              doh@redhat.com Daniel Oh
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: