Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-1106

Enable priority and least-waste expanders for cluster autoscaler

XMLWordPrintable

    • Strategic Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-12(OUTCOME STUB) Cloud platform activation/retention for Managed OpenShift (ROSA/ARO/OSD non-Hypershift enhancements)
    • 0% To Do, 0% In Progress, 100% Done
    • 0
    • Program Call

      Market Problem

      • As an OpenShift cluster administrator for a self-managed standalone OpenShift cluster, I want to use the Priority based expander for cluster-autoscaler to select instance types based on priorities assigned by a user to scaling groups.
        The Configuration is based on the values stored in a ConfigMap
      apiVersion: v1
kind: ConfigMap
metadata:
  name: cluster-autoscaler-priority-expander
  namespace: kube-system
data:
  priorities: |-
    10: 
      - .*t2\.large.*
      - .*t3\.large.*
    50: 
      - .*m4\.4xlarge.*

      Expected Outcomes

      • When creating a MachineSet, customers would like to define their preferred instance types with priorities so that if one is not available a fallback instance type option is available down the list.

      https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/expander/priority/readme.md

              rh-ee-smodeel Subin M
              rh-ee-smodeel Subin M
              Joel Speed, Michael McCune, Simon Reber
              Michael McCune Michael McCune
              Zhaohua Sun Zhaohua Sun
              Jeana Routh Jeana Routh
              Joel Speed Joel Speed
              Joel Speed Joel Speed
              Subin M Subin M
              Eric Rich Eric Rich
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: