Skip to content

Releases: atlassian/escalator

v1.8.0

02 Oct 04:56
01a495f
Compare
Choose a tag to compare

This release fixes two issues with Escalator.

  1. 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.

  2. A bug where using NodeAffinity to match pods to nodes would ignore the Operator instead of only matching against Operator In as desired. Note: if you currently use NodeAffinity match selector operators other than In 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

v1.7.1

10 Sep 05:54
b446b4f
Compare
Choose a tag to compare

This release removes the Maximum Taint Limit of 10 nodes at time. fast_node_removal_rate described the node group config is now the maximum taint amount.
This release also updates the Golang toolchain to use Go 1.13 and Go modules for dependency management.

Changelog

Builds Escalator from Go v1.13, #163
Removes Maximum Taint Limit of 10 at a time, #162

Docker Image

atlassian/escalator:v1.7.1

v1.7.0

05 May 23:36
Compare
Choose a tag to compare

This release adds support for one-shot capacity using AWS Fleet.

Changelog

  • Add support for one-shot capacity using AWS Fleet, #153

Docker Image

atlassian/escalator:v1.7.0

v1.6.2

01 May 00:08
9b6d036
Compare
Choose a tag to compare

Changelog

This release only updates escalator container image on docker hub because of docker hub security incident on 25th April 2019.

Docker Image

atlassian/escalator:v1.6.2

v1.6.1

11 Apr 04:51
9b6d036
Compare
Choose a tag to compare

Features

Bug fix for metrics output from scale from 0.
Metrics output a zero value when scaling up from 0 instead of Float64.Max

Docker Image

atlassian/escalator:v1.6.1

v1.6.0

08 Apr 23:31
b50c6a9
Compare
Choose a tag to compare

Features

  • Add support for node group to scale to/from 0

Docker Image

atlassian/escalator:v1.6.0

v1.5.2

28 Feb 04:14
3d2f28d
Compare
Choose a tag to compare

This release allows Escalator to adjust the scaling of an ASG while another ASG scaling request is in-flight.

Bug Fixes

  • Fixed issue where Escalator could not adjust scaling on ASGs when an instance was taking a long time to become available. #151

Docker Image

atlassian/escalator:v1.5.2

v1.5.1

26 Feb 23:34
5e6a7ff
Compare
Choose a tag to compare

This release version of escalator now builds with Golang 1.11 instead of 1.10.

This release provides no functionality changes to escalator.

Docker Image

atlassian/escalator:v1.5.1

v1.5.0

26 Feb 00:06
6634ef6
Compare
Choose a tag to compare

This release contains a new configuration option to define the TaintEffect of the taint applied to nodes.

taint_effect can be applied to each node group.

Usage for this option can be found in the documentation here

Features

taint_effect nodegroup option.

Docker Image

atlassian/escalator:v1.5.0

v1.4.1

18 Feb 05:37
e798f39
Compare
Choose a tag to compare

This release adds a bug fix which would let the ASG min and max size become out of date when using the auto discovery option.

Bug Fixes

  • When auto discovering ASG sizes, ASG in and max will be refreshed before each run loop. #145

Docker Image

atlassian/escalator:v1.4.1