-
Feature
-
Resolution: Done
-
Major
-
None
-
False
-
-
False
-
OCPSTRAT-12(OUTCOME STUB) Cloud platform activation/retention for Managed OpenShift (ROSA/ARO/OSD non-Hypershift enhancements)
-
0% To Do, 33% In Progress, 67% Done
-
0
-
0
-
Program Call
-
-
-
TE should be provided to make CEE aware of this capability and to showcase how it operates.
-
-
-
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
- is cloned by
-
-
- Refinement
-
- relates to
-
OCPBUGS-11115 Autoscaler does not work after entering in failed status for a single machineautoscaler
-
- ASSIGNED
-
-
-
- New
-
- links to
