From 9c779607edb3089ba700c17dc86629b0e4e1de0a Mon Sep 17 00:00:00 2001 From: GuyTempleton Date: Wed, 16 Feb 2022 21:26:15 +0000 Subject: [PATCH] CA - Docs - Clarify when multi expander support introduced --- cluster-autoscaler/FAQ.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/cluster-autoscaler/FAQ.md b/cluster-autoscaler/FAQ.md index 50bb9def04f6..8317293556e0 100644 --- a/cluster-autoscaler/FAQ.md +++ b/cluster-autoscaler/FAQ.md @@ -683,8 +683,7 @@ would match the cluster size. This expander is described in more details * `priority` - selects the node group that has the highest priority assigned by the user. It's configuration is described in more details [here](expander/priority/readme.md) - -Multiple expanders may be passed, i.e. +From 1.23.0 onwards, multiple expanders may be passed, i.e. `.cluster-autoscaler --expander=priority,least-waste` This will cause the `least-waste` expander to be used as a fallback in the event that the priority expander selects multiple node groups. In general, a list of expanders can be used, where the output of one is passed to the next and the final decision by randomly selecting one. An expander must not appear in the list more than once.