k8s-triage-robot
commented
2 years ago The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
rittneje
Which component are you using?:
cluster-autoscaler-priority-expander
https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler/expander/priority
Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:
Currently we can set the priority for an auto-scaling group via a ConfigMap that matches against the ASG name. However, this level of indirection makes it more confusing to manage. It would be preferable if the expander could reference some tag on the auto-scaling group to know its relative priority. This would also mean we don't have to worry about the order of events when a new ASG is being created.
Describe the solution you'd like.:
Respect the following tag on an auto-scaling group.
k8s.io/cluster-autoscaler/priority: XDescribe any alternative solutions you've considered.:
Our only other option at present is the regex-based ConfigMap, which is undesirable.
Additional context.:
The cluster-autoscaler already has similar tag-based logic for
--node-group-auto-discovery, so this concept is not new.