Kubernetes Cloud Controller Manager for Linode
The Linode Cloud Controller Manager (CCM) provides a way for Kubernetes clusters to access additional Linode services. Linode's CCM will automatically provision a Linode NodeBalancer for Kubernetes Services of type "LoadBalancer".
Full Changelog: https://github.com/linode/linode-cloud-controller-manager/compare/v0.4.3...v0.4.4
The Linode Cloud Controller Manager (CCM) provides a way for Kubernetes clusters to access additional Linode services. Linode's CCM will automatically provision a Linode NodeBalancer for Kubernetes Services of type "LoadBalancer".
Full Changelog: https://github.com/linode/linode-cloud-controller-manager/compare/helm-v0.4.2...v0.4.3
The Linode Cloud Controller Manager (CCM) provides a way for Kubernetes clusters to access additional Linode services. Linode's CCM will automatically provision a Linode NodeBalancer for Kubernetes Services of type "LoadBalancer".
Full Changelog: https://github.com/linode/linode-cloud-controller-manager/compare/helm-v0.4.1...v0.4.2
The Linode Cloud Controller Manager (CCM) provides a way for Kubernetes clusters to access additional Linode services. Linode's CCM will automatically provision a Linode NodeBalancer for Kubernetes Services of type "LoadBalancer".
FIXES v0.4.0 This release patches the initialization error from v0.4.0. Please read those notes for full details on this release.
Full Changelog: https://github.com/linode/linode-cloud-controller-manager/compare/v0.4.0...v0.4.1
FIXES v0.3.25 This release patches the initialization error from v0.3.25. Please read those notes for full details on this release.
We won't have a helm release for v0.3.26. If one needs helm release, they can upgrade to v0.4.1 or later releases.
Full Changelog: https://github.com/linode/linode-cloud-controller-manager/compare/v0.3.25...v0.3.26
DO NOT USE due to ungated VPC logic this release does not boot with the following error, please use v0.4.1
main.go:130] Cloud provider could not be initialized: could not init cloud provider "linode": routes client was not created successfully: failed to find VPC: ""
This release changes the nodebalancer throttling default from 20 (throttled) to 0 (no throttling), when upgrading to this version all Services with nodebalancers managed by the CCM without the annotation service.beta.kubernetes.io/linode-loadbalancer-throttle
set to a number between 0-20 will have their throttling updated to 0. If your service requires throttling it is recommended to set the annotation before upgrading.
Full Changelog: https://github.com/linode/linode-cloud-controller-manager/compare/v0.3.25...v0.4.0