From 0feab03bad3c94a41af27598255afc4a67e46dab Mon Sep 17 00:00:00 2001 From: Erik Sundell Date: Sun, 13 Sep 2020 00:17:43 +0200 Subject: [PATCH] Make docs/reference/scheduling/config focus on v1beta1 over alpha versions Suggestion to fix #23837 that was directing the focus towards an alpha API instead of the now available beta API. --- content/en/docs/reference/scheduling/config.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/content/en/docs/reference/scheduling/config.md b/content/en/docs/reference/scheduling/config.md index 530e881cbd84f..0dca862fb9f87 100644 --- a/content/en/docs/reference/scheduling/config.md +++ b/content/en/docs/reference/scheduling/config.md @@ -20,10 +20,7 @@ by implementing one or more of these extension points. You can specify scheduling profiles by running `kube-scheduler --config `, using the component config APIs -([`v1alpha1`](https://pkg.go.dev/k8s.io/kube-scheduler@v0.18.0/config/v1alpha1?tab=doc#KubeSchedulerConfiguration) -or [`v1alpha2`](https://pkg.go.dev/k8s.io/kube-scheduler@v0.18.0/config/v1alpha2?tab=doc#KubeSchedulerConfiguration)). -The `v1alpha2` API allows you to configure kube-scheduler to run -[multiple profiles](#multiple-profiles). +([`v1beta1`](https://pkg.go.dev/k8s.io/kube-scheduler@v0.19.0/config/v1beta1?tab=doc#KubeSchedulerConfiguration)). A minimal configuration looks as follows: