Merge pull request #4684 from gjtempleton/4504-Clarify-Multiple-Expan…

…der-Support CA - Docs - Clarify when multi expander support introduced
kubernetes · Feb 21, 2022 · 5cf3b96 · 5cf3b96
2 parents 1b5aacd + 9c77960
commit 5cf3b96
Showing 1 changed file with 1 addition and 2 deletions.
diff --git 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.