You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: keps/sig-autoscaling/5030-attach-limit-autoscaler/README.md
-7Lines changed: 0 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -126,10 +126,6 @@ As part of this proposal we are proposing changes into both cluster-autoscaler a
126
126
2. Fix cluster-autoscaler so that it takes into account attach limits when scaling nodegroups with existing nodes.
127
127
3. Fix kubernetes built-in scheduler so that we do not schedule pods to nodes that doesn't have CSI driver installed.
128
128
129
-
While, changes into both CAS and scheduler can happen behind same featuregate that is being proposed in this enhancement, we propose delaying default enablement of scheduler change
130
-
that prevents scheduling of pods to a node that doesn't have CSI driver installed until a release when Cluster-AutoScaler (CAS) changes have been GAed and meet N-3 version skew criteria. See - version skew section for more information.
131
-
132
-
133
129
### User Stories (Optional)
134
130
135
131
#### Story 1
@@ -487,9 +483,6 @@ well as the [existing list] of feature gates.
487
483
- Will enabling / disabling the feature require downtime of the control
488
484
plane?
489
485
Yes, it should require restart of CAS and kube-scheduler.
490
-
- Will enabling / disabling the feature require downtime or reprovisioning
491
-
of a node?
492
-
No, it should not require reprovisioning a node.
493
486
494
487
###### Does enabling the feature change any default behavior?
0 commit comments