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
In the 1.31.0 and lower version SKS nodepools where discovered through exoscale instance pools.
Whereas it works as expected, end user experience is not very convenient, especially when end users use priority based expander.
On our portal SKS nodepools are shown with their ID and the instancepool is hidden in the SKS nodepool page itself. People trying to
use priority based expander put SKS nodepool ID instead of our generic compute API InstancePool ID.
For convenience, starting with this commit we are using SKS nodepool ID and we add retro compatibility for already cluster autoscaler
managed SKS clusters. This will reduce a bit our support on it, and make priority based expander UX more convenient.
0 commit comments