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

🐛 Cluster Autoscaler: provider is not customisable #317

Open
dalees opened this issue Apr 18, 2024 · 1 comment
Open

🐛 Cluster Autoscaler: provider is not customisable #317

dalees opened this issue Apr 18, 2024 · 1 comment

Comments

@dalees
Copy link

dalees commented Apr 18, 2024

The Cluster Autoscaler deployed by this Helm Chart uses the clusterapi provider.

This is fine when Magnum is not driving the Charts, but when using the magnum-capi-helm driver any scaling actions do not get reflected into Magnum. This leads to incorrect values for Node Groups showing in the Magnum API.

We should consider using --provider=magnum when Magnum is in use, so the Cluster Autoscaler talks to Magnum and not CAPI directly.

@dalees dalees changed the title Cluster Autoscaler provider is not customisable 🐛 Cluster Autoscaler: provider is not customisable Apr 18, 2024
@dalees
Copy link
Author

dalees commented Apr 19, 2024

This does not appear to be immediately solvable simply using provider=magnum and giving it args as it appears this reaches into Heat Stacks[1] to determine Server UUIDs.

The Magnum API should really provide these via the nodegroup information, so the driver can implement this however it likes - for exactly this reason.

[1] https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/magnum/magnum_manager_impl.go#L232

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant