Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-51720

KubeVirt should not use common label for CPUManager

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • CNV Virt-Node
    • None
    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • ---
    • ---
    • None

      Description of problem:

      
Currently KubeVirt uses the literal "cpumanager" label on a node to determine if CPUManager is enabled. This label is commonly used by all components on the cluster. We have an unfortunate side effect that if KubeVirt's config disabled CPU manager, this will disable this feature for all pods on the node, and not just for KubeVirt.

KubeVirt should use a properly namespaced prefix for this label.

      Version-Release number of selected component (if applicable):

      How reproducible:

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

      Expected results:

      Additional info:

              sgott@redhat.com Stuart Gott
              sgott@redhat.com Stuart Gott
              Denys Shchedrivyi Denys Shchedrivyi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: