Releases: neondatabase/autoscaling
Releases · neondatabase/autoscaling
v0.1.8
No features added. Protocol changes: - Added versioning to agent->plugin messages, initial set at v1.0. Refer to pkg/api/VERSIONING.md for compatibility information. Upgrade path from v0.1.7: - Deploy autoscaler-agent v0.1.7 BEFORE the updated scheduler. - No requirements relating to vm-informant.
v0.1.7
Features: - plugin: Allow unknown JSON fields in agent messages. This should allow future changes to be non-breaking. Upgrade path from v0.1.6: - This release is fully compatible with v0.1.6; any release order is acceptible.
v0.1.6
Hotfix release, contains only a bugfix for the VM informant, where it would incorrectly immediately retry on failure.
v0.1.5
Features: - informant: Added auto-restarting capability Upgrade path from v0.1.4: - This release is fully compatible with v0.1.4; nothing special is required.
v0.1.4
Features: - informant: Added immediate memory upscaling, via cgroup memory.events - enabled only when passed --cgroup=$NAME Protocol changes: - Bumped agent<->informant v1.0 -> v1.1 - Added agent /try-upscale endpoint for immediate-ish upscaling Refer to pkg/api/VERSIONING.md for compatibility information. Upgrade path from v0.1.3: - New scheduler and autoscaler-agent can be deployed in any order. - Deploy new autoscaler-agent before vm-informant.
v0.1.3
v0.1.3
0.1.2
v0.1.2
0.1.1
v0.1.1
0.1.0
v0.1.0