autoscaler/cluster-autoscaler/cloudprovider/exoscale
Sebastian Krohn bf89632108
Add missing clusterrole permissions (#1)
2022-03-28 14:42:24 +02:00
..
examples Add missing clusterrole permissions (#1) 2022-03-28 14:42:24 +02:00
internal internal/vendor 2022-03-16 17:27:01 +01:00
OWNERS CA - Exoscale Provider - Add owners file 2022-01-30 17:41:31 +00:00
README.md Add missing clusterrole permissions (#1) 2022-03-28 14:42:24 +02:00
exoscale_cloud_provider.go Exoscale cloud provider overhaul 2022-03-16 17:35:27 +01:00
exoscale_cloud_provider_test.go Exoscale cloud provider overhaul 2022-03-16 17:35:27 +01:00
exoscale_manager.go Exoscale cloud provider overhaul 2022-03-16 17:35:27 +01:00
exoscale_manager_test.go Exoscale cloud provider overhaul 2022-03-16 17:35:27 +01:00
exoscale_node_group_instance_pool.go Exoscale cloud provider overhaul 2022-03-16 17:35:27 +01:00
exoscale_node_group_instance_pool_test.go Exoscale cloud provider overhaul 2022-03-16 17:35:27 +01:00
exoscale_node_group_sks_nodepool.go Exoscale cloud provider overhaul 2022-03-16 17:35:27 +01:00
exoscale_node_group_sks_nodepool_test.go Exoscale cloud provider overhaul 2022-03-16 17:35:27 +01:00
log.go Exoscale cloud provider overhaul 2022-03-16 17:35:27 +01:00
util.go Exoscale cloud provider overhaul 2022-03-16 17:35:27 +01:00
vendor_internal.sh Exoscale cloud provider overhaul 2022-03-16 17:35:27 +01:00

README.md

Cluster Autoscaler for Exoscale

The Cluster Autoscaler (CA) for Exoscale scales worker nodes running in Exoscale SKS Nodepools or Instance Pools.

Configuration

Note: the following guide assumes you have the permissions to create resources in the kube-system namespace of the target Kubernetes cluster.

In order to interact with the Exoscale API, the Exoscale CA must be configured with API credentials. This can be achieved using Kubernetes Secrets, by exposing those as container environment variables.

We provide a convenience script that generates and applies a k8s manifest declaring Exoscale API credentials as a k8s Secret in your cluster from your local shell environment variables: once created, this Secret can be used in the CA Deployment.

First, start by exporting the Exoscale API credentials (we recommend that you create dedicated API credentials using the Exoscale IAM service) to provide to the CA in your shell, as well as the zone the target Kubernetes cluster is located in:

export EXOSCALE_API_KEY="EXOxxxxxxxxxxxxxxxxxxxxxxxx"
export EXOSCALE_API_SECRET="xxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
export EXOSCALE_ZONE="ch-gva-2"

Next, run the following command from the same shell:

./examples/generate-secret.sh

Next, ensure that the exoscale-api-credentials Secret has been created successfully by running the following command:

kubectl get secret --namespace kube-system exoscale-api-credentials

Finally, a EXOSCALE_ZONE variable must be set to the target Kubernetes cluster zone along with the API credentials in the CA Deployment shell environment.

Deploying the Cluster Autoscaler

To deploy the CA on your Kubernetes cluster, you can use the manifest provided as example:

kubectl apply -f ./examples/cluster-autoscaler-run-on-control-plane.yaml

⚠️ Important Notes

  • The minimum node group size is 1
  • The maximum node group size is computed based on the current Compute instances limit of the Exoscale account the Cluster Autoscaler is running in.
  • The Instance Pool candidate for scaling is determined based on the Compute instance the Kubernetes node is running on, depending on cluster resource constraining events emitted by the Kubernetes scheduler.