v1.8.0
This release fixes two issues with Escalator.
-
An edge case when increasing the minimum cloud provider nodegroup size above the current number of nodes would mean Escalator would skip untainting nodes to reach the desired capacity and instead request new nodes. This has been fixed such that Escalator will first try to untaint required nodes in that rare case.
-
A bug where using
NodeAffinity
to match pods to nodes would ignore the Operator instead of only matching against OperatorIn
as desired. Note: if you currently useNodeAffinity
match selector operators other thanIn
you should update your pod configuration to match the documentation before updating to this version of Escalator.
Changelog
Only match against In
operator for NodeAffinity
match selectors, #160
Untaint nodes when below minimum before requesting new nodes #168
Docker Image
atlassian/escalator:v1.8.0