You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
dalees
changed the title
Cluster Autoscaler provider is not customisable
🐛 Cluster Autoscaler: provider is not customisable
Apr 18, 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.
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.The text was updated successfully, but these errors were encountered: