From ecfdc21f0957f38f0ffd4307b7d0d7851bec1757 Mon Sep 17 00:00:00 2001 From: droctothorpe Date: Wed, 26 Jul 2023 13:45:27 -0400 Subject: [PATCH] Fix broken hyperlink Co-authored-by: Shubham --- cluster-autoscaler/FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cluster-autoscaler/FAQ.md b/cluster-autoscaler/FAQ.md index cec5ebf22573..17b25a0a8281 100644 --- a/cluster-autoscaler/FAQ.md +++ b/cluster-autoscaler/FAQ.md @@ -862,7 +862,7 @@ Events: ``` This limitation was solved with -[volume topological scheduling](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/volume-topology-scheduling.md) +[volume topological scheduling](https://github.com/kubernetes/design-proposals-archive/blob/main/storage/volume-topology-scheduling.md) introduced as beta in Kubernetes 1.11 and planned for GA in 1.13. To allow CA to take advantage of topological scheduling, use separate node groups per zone. This way CA knows exactly which node group will create nodes in the required zone rather than relying on the cloud provider choosing a zone for a new node in a multi-zone node group.