Skip to content

Commit 196fe93

Browse files
gnufiedmacsko
andcommitted
Update keps/sig-autoscaling/5030-attach-limit-autoscaler/kep.yaml
Co-authored-by: Maciej Skoczeń <[email protected]>
1 parent f3054d4 commit 196fe93

File tree

1 file changed

+0
-7
lines changed
  • keps/sig-autoscaling/5030-attach-limit-autoscaler

1 file changed

+0
-7
lines changed

keps/sig-autoscaling/5030-attach-limit-autoscaler/README.md

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -126,10 +126,6 @@ As part of this proposal we are proposing changes into both cluster-autoscaler a
126126
2. Fix cluster-autoscaler so that it takes into account attach limits when scaling nodegroups with existing nodes.
127127
3. Fix kubernetes built-in scheduler so that we do not schedule pods to nodes that doesn't have CSI driver installed.
128128

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-
133129
### User Stories (Optional)
134130

135131
#### Story 1
@@ -487,9 +483,6 @@ well as the [existing list] of feature gates.
487483
- Will enabling / disabling the feature require downtime of the control
488484
plane?
489485
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.
493486

494487
###### Does enabling the feature change any default behavior?
495488

0 commit comments

Comments
 (0)