v0.4.5

What's Changed

• Fix Test Badge by @zliang-akamai in #205
• Set toolchain go1.22.2 go.mod by @mhmxs in #206
• update client to work for v4beta API by @AshleyDumaine in #210
• [bugfix] - handle LoadBalancer deletion if service type changes to no longer be a LoadBalancer by @AshleyDumaine in #211
• Update linodego by @okokes-akamai in #212
• [feat] - add support for cilium-backed loadbalancers by @AshleyDumaine in #208

New Contributors

• @zliang-akamai made their first contribution in #205
• @mhmxs made their first contribution in #206

Full Changelog: v0.4.4...v0.4.5

helm-v0.4.5

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

🚀 Features

• feat: Add route_controller to linode CCM by @rahulait in #199
  To enable it, follow steps defined here.

💡What's Changed

• fix-readme: firewall-acl invalid json by @Michkov in #203
• Lookup linode by IP instead if label or providerID do not match by @eljohnson92 in #198
• Adding --webhook-secure-port=0 to helmchart since it is needed workaround for issue #200 by @akaokunc in #204

New Contributors

• @Michkov made their first contribution in #203

Full Changelog: v0.4.3...v0.4.4

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

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