Uploaded image for project: 'OpenShift Workloads'
  1. OpenShift Workloads
  2. WRKLDS-1715

The taint still exists when I delete the kubeDescheduler object or completely remove the descheduler operator

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

       The taint not removed when I deleted the KubeDescheduler object, same happens when I completely removed the kube-descheduler operator.

       

      These leftovers may cause VMs/PODs to be scheduled on wrong nodes (for example in CNV tests automation we use the nodeAffinity preffered, so if the taint remains - the virt-launcher pod might be created in wrong place)

       

              stirabos Simone Tiraboschi
              dshchedr@redhat.com Denys Shchedrivyi
              None
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: