v2.1.0

• This update lets different types of instances coexist within the same node pool. This will make it easier for older clusters to transition from the 1.1.5 naming system, which included instance type in the name, to the newer 2.x naming scheme that doesn’t include this detail.

v2.0.9

• Switched to new official autoscaler image (by @ghaering)

v2.0.8

Fixed

• Fixed an issue preventing correct detection of the private network interface for autoscaled nodes

Upgrading

Important: See notes for v2.0.0 if you are upgrading from v1.1.5.

v2.0.7

Fixed

• Temporarily switched to a custom autoscaler image by Hetzner. The official image still relies on an instance type that has been deprecated

Upgrading

Important: See notes for v2.0.0 if you are upgrading from v1.1.5.

v2.0.6

Fixed

• Fixed an issue with the JSON requests to Hetzner introduced by the upgrade of the Crest library in 2.0.5

Upgrading

Important: See notes for v2.0.0 if you are upgrading from v1.1.5.

v2.0.5

Improvements

• Configured memory requests for Cilium

Fixes

• Upgraded some shards to fix an issue with OpenSSL issue on Fedora (by @n7st)

Upgrading

Important: See notes for v2.0.0 if you are upgrading from v1.1.5.

v2.0.4

Improvements

• Changed the way we detect the current IP address to use IpInfo, since it works in location like China where the previous method based on an Akamai service wasn't working

Upgrading

Important: See notes for v2.0.0 if you are upgrading from v1.1.5.

v2.0.3

Fixes

• Fixed an issue with the firewall not opening the port necessary for the embedded registry mirror in configurations with the private network

Upgrading

Important: See notes for v2.0.0 if you are upgrading from v1.1.5.

v2.0.2

Fixed

• Fixed an issue with the Github Actions pipeline which was producing an ARM binary for Intel Mac due to a change in the expected OS introduced recently by Github

Upgrading

Important: See notes for v2.0.0 if you are upgrading from v1.1.5.

v2.0.1

Fixed

• Always use the private IP of the master - if the private network is enabled - when connecting to the API from the nodes. This way the access to the API from the Internet can be safely restricted to specific networks.

Upgrading

Important: See notes for v2.0.0 if you are upgrading from v1.1.5.