Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-4563

Deletion of SMCP doesn't trigger the deletion of istio-cni pods

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Normal Normal
    • None
    • OSSM 2.4.1
    • Maistra
    • None
    • False
    • None
    • False

      Issue: SMCP deletion doesn't delete the its respective istio-cni daemonset.

      Summary:

      Whenever SMCP is created it triggers istio-cni daemonset for that control plane version. However, when the control plane is deleted it doesn't automatically delete the istio-cni daemonset. This has to be manually deleted

            Unassigned Unassigned
            rhn-support-hchaturv Himank Chaturvedi
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: