Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-60298

release 4.18 - openshift-console/download pods running on random nodes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • 4.17.z
    • 4.18.z
    • Management Console
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • None
    • None
    • None
    • In Progress
    • Bug Fix
    • Hide
      * Before this update, downloads on control plane nodes were inconsistently scheduled because of a mismatch between the node selector for downloads and the console pods. As a consequence, downloads were scheduled on random nodes, which caused potential resource contention and sub-optimal performance. With this release, downloaded workloads consistently schedule on control plane nodes, which improves resource allocation. (link:https://issues.redhat.com/browse/OCPBUGS-60298[OCPBUGS-60298])
      Show
      * Before this update, downloads on control plane nodes were inconsistently scheduled because of a mismatch between the node selector for downloads and the console pods. As a consequence, downloads were scheduled on random nodes, which caused potential resource contention and sub-optimal performance. With this release, downloaded workloads consistently schedule on control plane nodes, which improves resource allocation. (link: https://issues.redhat.com/browse/OCPBUGS-60298 [ OCPBUGS-60298 ])
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-59897. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-59488. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-57630. The following is the description of the original issue:
      —
      Description:

      As noted in the parallel RFE-1896, while the console pods are scheduled [0] on control plane nodes by design, the downloads [1] is misaligned in this regard and can still be seen to be scheduled on random nodes.

      • It's therefore preferable to have the same "node-role.kubernetes.io/master": "" selector for the downloads deployment, in order to consistently schedule the non-customer workload on control plane nodes.

      [0]

      curl -s https://raw.githubusercontent.com/openshift/console-operator/refs/heads/release-4.16/bindata/assets/deployments/console-deployment.yaml | yq '.spec.template.spec.nodeSelector'
{
  "node-role.kubernetes.io/master": ""
}

      [1]

      $ curl -s https://raw.githubusercontent.com/openshift/console-operator/refs/heads/release-4.16/bindata/assets/deployments/downloads-deployment.yaml | yq '.spec.template.spec.nodeSelector'
{
  "kubernetes.io/os": "linux"
}

              jhadvig@redhat.com Jakub Hadvig
              rhn-support-rsandu Robert Sandu
              None
              None
              YaDan Pei YaDan Pei
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: