From da04e81a6d10e0eb29f640690a80c115149d46d1 Mon Sep 17 00:00:00 2001 From: Cyrill Troxler Date: Wed, 16 Oct 2024 14:49:21 +0200 Subject: [PATCH] docs(rancher): clarify single RKE2 target Clarify that a cluster-autoscaler instance can target a single RKE2 cluster. --- cluster-autoscaler/cloudprovider/rancher/README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/cluster-autoscaler/cloudprovider/rancher/README.md b/cluster-autoscaler/cloudprovider/rancher/README.md index 15114c74461f..af99ea1fbb4e 100644 --- a/cluster-autoscaler/cloudprovider/rancher/README.md +++ b/cluster-autoscaler/cloudprovider/rancher/README.md @@ -6,11 +6,13 @@ underlying cluster-api types of RKE2. ## Configuration -The `cluster-autoscaler` for Rancher needs a configuration file to work by -using `--cloud-config` parameter. An up-to-date example can be found in -[examples/config.yaml](./examples/config.yaml). +The `cluster-autoscaler` for Rancher needs a configuration file to work by using +`--cloud-config` parameter. A `cluster-autoscaler` instance can target a single +downstream RKE2 cluster specified in the config. An up-to-date example can be +found in [examples/config.yaml](./examples/config.yaml). ### Configuration via environment variables + In order to override URL, token or clustername use following environment variables: - RANCHER_URL - RANCHER_TOKEN