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