History

Clint Fooken 08dfc7e20f Changing deletion logic to rely on a new helper method in ClusterStateRegistry, and remove old complicated logic. Adjust the naming of the method for cloud instance deletion from NodeExists to HasInstance.		2022-11-04 17:54:05 -07:00
..
scalewaygo	fix: header formatting	2022-08-09 10:12:32 +02:00
OWNERS	ignore: comment out k8s org non-member OWNERS file	2022-08-09 10:14:51 +02:00
README.md	add: Scaleway Cloud Provider for k8s CA	2022-08-09 10:12:29 +02:00
scaleway_cloud_provider.go	Changing deletion logic to rely on a new helper method in ClusterStateRegistry, and remove old complicated logic. Adjust the naming of the method for cloud instance deletion from NodeExists to HasInstance.	2022-11-04 17:54:05 -07:00
scaleway_node_group.go	fix: header formatting	2022-08-09 10:12:32 +02:00
scaleway_node_group_test.go	fix: header formatting	2022-08-09 10:12:32 +02:00

README.md

Cluster Autoscaler for Scaleway

The Scaleway Cloud Provider implementation scales nodes on different pools attached to a Kapsule cluster. It can be configured from Scaleway Kapsule API. The cluster pools need to have the option Autoscaling set to true to be managed by the autoscaler.

Configuration

Cluster Autoscaler can be configured with 2 options

Config file

a config file can be passed with the --cloud-config flag.
here is the corresponding JSON schema:

cluster_id: Kapsule Cluster Id
secret_key: Secret Key used to manage associated Kapsule resources
region: Region where the control-plane is runnning
api_url: URL to contact Scaleway, defaults to api.scaleway.com

Env variables

The values expected by the autoscaler are the same as above

CLUSTER_ID
SCW_SECRET_KEY
SCW_REGION
SCW_API_URL

Notes

k8s nodes are identified through node.Spec.ProviderId, the scaleway node name or id MUST NOT be used.