v0.4.3

What's Changed

• Use Go 1.22 HTTP router in fake API by @okokes-akamai in #173
• Fixing the nodebalancer config rebuilds to include ids of preexisting nodebalancer nodes by @akaokunc in #192

New Contributors

• @akaokunc made their first contribution in #192

Full Changelog: helm-v0.4.2...v0.4.3

helm-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".

v0.4.2

What's Changed

• revert route_controller related changes done in PR 184, PR 190 by @rahulait in #195

Full Changelog: helm-v0.4.1...v0.4.2

helm-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".

v0.4.1

FIXES v0.4.0 This release patches the initialization error from v0.4.0. Please read those notes for full details on this release.

What's Changed

• don't error out with empty vpc name if routecontroller is disabled by @rahulait in #190

Full Changelog: v0.4.0...v0.4.1

v0.4.0

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: "" 

⚠️ WARNING

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.

What's Changed

• disable conn-throttle by default by @tchinmai7 in #189

Full Changelog: v0.3.25...v0.4.0

v0.3.26

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.

What's Changed

• don't error out with empty vpc name if routecontroller is disabled (#… by @rahulait in #191

Full Changelog: v0.3.25...v0.3.26

helm-v0.4.1

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".

v0.3.25

DO NOT USE due to ungated VPC logic this release does not boot with the following error, please use v0.3.26

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: "" 

⚠️ Breaking Changes

update default CCM node selector and tolerations from master to control-plane by @AshleyDumaine in #176

To use older CCM releases with k8s 1.29 or greater, install helm chart by passing in additional values.yaml file

apiToken: <api token>
region: <region>
nodeSelector:
  node-role.kubernetes.io/control-plane: ""
tolerations:
  - key: "node-role.kubernetes.io/control-plane"
    effect: "NoSchedule"

Install helm chart using helm install ccm-linode -f values.yaml ccm-linode/ccm-linode.
Similarly, if one wants to use CCM v0.3.25 with older versions of k8s, change node-selector and tolerations to node-role.kubernetes.io/master to have it installed.

🚀 Features

• Added route_controller functionality to CCM. To enable it, follow steps defined here.

💡What's Changed

• add helm test and publish workflow by @eljohnson92 in #177
• store helm packages directly in the Github page by @eljohnson92 in #178
• restrict helm releases to be triggered by Github releases by @eljohnson92 in #179
• Wrap node update in retry by @avestuk in #175
• fix adding labels to node by @rahulait in #181
• Support for acls with >255 IPs by @tchinmai7 in #180
• Refactor into distinct packages to prep for adding firewall support to Nodes by @AshleyDumaine in #186
• feat: add route-controller to linode ccm by @rahulait in #184

New Contributors

• @eljohnson92 made their first contribution in #177
• @avestuk made their first contribution in #175
• @AshleyDumaine made their first contribution in #176
• @rahulait made their first contribution in #181

Full Changelog: v0.3.24...v0.3.25

helm-v0.3.25

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".