autoscaler/cluster-autoscaler/cloudprovider/scaleway
Bartłomiej Wróblewski 3b47908e51 Add ForceDeleteNodes method to NodeGroup interface 2024-11-18 13:55:07 +00:00
..
scalewaygo fix: header formatting 2022-08-09 10:12:32 +02:00
OWNERS CA - Correct Cloudprovider PR labelling to area/provider/<provider name> 2023-05-29 15:30:46 +01:00
README.md add: Scaleway Cloud Provider for k8s CA 2022-08-09 10:12:29 +02:00
scaleway_cloud_provider.go Add GetNodeGpuConfig to cloud provider 2023-02-14 14:08:29 +00:00
scaleway_node_group.go Add ForceDeleteNodes method to NodeGroup interface 2024-11-18 13:55:07 +00: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.