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
Which component are you using?:
cluster-autoscaler
Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:
During a maintenance window I need to quickly move workload away from a workergroup with minimal service disruption for the customer. I also want to control the resource overhead. I want to taint (all nodes of) a workergroup and drain a couple of them. When draining them is finished, I'd like to drain the next chunk and so on.
Describe the solution you'd like.:
I'd like to be able (after draining a node) to delete it or have "someone" delete it. The most natural solution for me would be to just allow kubectl delete node some-node without the creation of some replacement node after some time. At the moment this does not work (see FAQ of cluster autoscaler and machine-controller-manager).
Describe any alternative solutions you've considered.:
Another solution would be something like setting an annotation on the node resource that tells Gardener, that I want to have this node deleted.
Which component are you using?:
cluster-autoscaler
Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:
During a maintenance window I need to quickly move workload away from a workergroup with minimal service disruption for the customer. I also want to control the resource overhead. I want to taint (all nodes of) a workergroup and drain a couple of them. When draining them is finished, I'd like to drain the next chunk and so on.
Describe the solution you'd like.:
I'd like to be able (after draining a node) to delete it or have "someone" delete it. The most natural solution for me would be to just allow
kubectl delete node some-node
without the creation of some replacement node after some time. At the moment this does not work (see FAQ of cluster autoscaler and machine-controller-manager).Describe any alternative solutions you've considered.:
Another solution would be something like setting an annotation on the node resource that tells Gardener, that I want to have this node deleted.
Additional context.:
Had a discussion with @dguendisch @rishabh-11 and others already.
The text was updated successfully, but these errors were encountered: