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

Node label for KAS go mem limit is different than what OSDFM expects

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • 4.19.0
    • 4.19.0
    • HyperShift
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Critical
    • Yes
    • None
    • Proposed
    • None
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • None

      Description of problem:

          The node label that osdfm sets for KAS GOMEMLIMIT on request serving nodes is hypershift.openshift.io/request-serving-gomemlimit. However, in PR#5417, we changed the label we read to hypershift.openshift.io/kas-go-mem-limit, resulting in the go mem limit not getting applied on existing HostedClusters anymore

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

          4.19.0

      How reproducible:

          always

      Steps to Reproduce:

          1. Create a ROSA hosted cluster in stage
    2. Obtain the KAS deployment YAML
    3. Check for GOMEMLIMIT environment variable on the kube-apiserver container.

      Actual results:

          No GOMEMLIMIT environment variable is set

      Expected results:

      The GOMEMLIMIT environment variable is set

      Additional info:

              cewong@redhat.com Cesar Wong
              cewong@redhat.com Cesar Wong
              None
              None
              Jie Zhao Jie Zhao
              None
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: