exoscale-cloud-controller-manager is the Kubernetes Cloud Controller
Manager (CCM) implementation for Exoscale. This component enables a
tighter integration of Kubernetes clusters with the Exoscale Compute platform.
The Exoscale CCM implements the following controllers:
- Node controller: dynamically annotates Exoscale Compute instances registered as Nodes with platform-specific information (e.g. instance type, zone), and detects when a Compute instance previously registered as a k8s Node doesn't exist anymore and de-registers it from the cluster.
- Service controller: dynamically manages Exoscale Network Load
Balancers with k8s Services of type
LoadBalancerto transparently forward traffic to k8s Pods running on Compute Instance Pools-managed cluster Nodes.
To get started with the Exoscale Cloud Controller Manager, please read the following guide.
The exoscale CCM adheres to Semantic Versioning.
New minor versions after 0.14 are aligned with the minor version number of the latest Kubernetes release.
The aligned version 0.y is compatible with Kubernetes version 1.y and unless specified otherwise in the compatibility matrix below, CCM 0.y is also compatible with the two most recent Kubernetes minor versions before 1.y. Versions that are even older may work but without guarantee.
For example, CCM 0.99 would be compatible with Kubernetes versions 1.99, 1.98 and 1.97.
| CCM version | supported Kubernetes versions |
|---|---|
| 0.30 | 1.30, 1.29, 1.28, |
| 0.14 | 1.28, 1.27, 1.26 |
- If you think you've found a bug in the code or you have a question regarding the usage of this software, please reach out to us by opening an issue in this GitHub repository.
- Contributions to this project are welcome: if you want to add a feature or a fix a bug, please do so by opening a Pull Request in this GitHub repository. In case of feature contribution, we kindly ask you to open an issue to discuss it beforehand.