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

Not clear if the Memory limits must be set in GiB or GB

XMLWordPrintable

    • No
    • 1
    • CLOUD Sprint 249
    • 1
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      The customer is pointing that the memory max value scale up is based in GB value, while the min memory for scale down is based on GiB.

      So, setting both values in GB makes scale down fail:

      Skipping ocgc4preplatgt-98fwh-worker-c-sk2sz - minimal limit exceeded for [memory] 

      While setting both values in GiB makes the scale up fail.

       

      • API reference¬†says that GBs must be used for memory min/max limits:

      https://docs.openshift.com/container-platform/4.12/rest_api/autoscale_apis/clusterautoscaler-autoscaling-openshift-io-v1.html#spec-resourcelimits

      • While OCP Cluster Autoscaler documentation points to GiBs:

      https://docs.openshift.com/container-platform/4.12/machine_management/applying-autoscaling.html#cluster-autoscaler-cr_applying-autoscaling

            mimccune@redhat.com Michael McCune
            rhn-support-rauferna Raul Fernandez
            Zhaohua Sun Zhaohua Sun
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: