Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Network routes are not cleaned up by HCCM #1477

Open
apricote opened this issue Sep 11, 2024 · 0 comments · May be fixed by #1478
Open

[Bug]: Network routes are not cleaned up by HCCM #1477

apricote opened this issue Sep 11, 2024 · 0 comments · May be fixed by #1478
Labels
bug Something isn't working

Comments

@apricote
Copy link

Description

Network Routes are not properly cleaned up by hcloud-cloud-controller-manager since HCCM v1.20.0.

This causes issues when users cycle through their nodes (with autoscaler) and they have a lot of stale routes laying around. Adding new nodes then fails because they have already reached the routes limit (100).

HCCM only cleans up routes that are inside its configured --cluster-cidr.

In HCCM v1.20.0 we changed our pod spec from using command to args. Your patches (templates/ccm.yaml.tpl) still try to override the command, and are then ignored because the ccm-networks.yaml has the default --cluster-cidr in the args.

This was originally reported in hetznercloud/hcloud-cloud-controller-manager#734

Kube.tf file

The issue can be reproduced with the default `kube.tf`.

Screenshots

No response

Platform

Linux

@apricote apricote added the bug Something isn't working label Sep 11, 2024
@apricote apricote changed the title [Bug]: Custom [Bug]: Network routes are not cleaned up by HCCM Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant