Tags

v0.5.1

Hotfix release, fixes a panic on autoscaler-agent dump-state requests.

v0.5.0

This release marks the first release where NeonVM has been merged into
the same repository. It was last at v0.4.6, so we've bumped to v0.5.0 as
a kind of clean slate.

Features:

- Added "dump state" endpoints to autoscaler-agent and scheduler plugin.
  Refer to https://github.com/neondatabase/autoscaling/pull/76 for more
  information. (The endpoints are enabled by default).

No protocol changes.

There have been significant changes to testing - everything is run by
the Makefile now. Refer to https://github.com/neondatabase/autoscaling/pull/91
for more information.

Upgrade path from v0.1.17 / v0.4.6:

- No ordering requirements.

v0.1.17

No new features.

Fixes:

- agent/billing: consumption event duplication fixed (#94)

No protocol changes.

Upgrade path from v0.1.16:

- No ordering requirements.

v0.1.16

Hotfix release, fixes a panic that occurs when billing is enabled.

v0.1.15

Features:

- billing: add additional active_time metric
- testing: add initial e2e tests and framework

Fixes:

- informant: improvements to process monitoring and signal handling

No protocol changes.

Upgrade path from v0.1.14:

- No ordering requirements.

v0.1.14

Features:

- vm-informant: Integration with Neon file cache (#47)
- scheduler, agent: Add pprof endpoints on port 7777 (#71, #70)

Fixes:

- scheduler, agent: Termination signal handling should be improved (#70, f3f1c38fe2)

No protocol changes.

Upgrade path from v0.1.13:

- No ordering requirements.

v0.1.12

No new features.

Fixes:

- Scheduler no longer spins 1+ CPU

No protocol changes.

Upgrade path from v0.1.11:

- No ordering requirements.

v0.1.11

Hotfix release, fixes a panic case while handling VMs, introduced in
v0.1.9.

Upgrade path from v0.1.10:

- No ordering requirements. Only the scheduler is updated.

v0.1.10

No new features.

Changes:

- Use resource requests (not limits) for non-VM pods

No protocol changes.

Upgrade path from v0.1.9:

- No ordering requirements.

v0.1.9

Features:

- agent: VM billing events pushing added

Protocol changes:

- Allow nil metrics in agent->plugin messages
- agent<->plugin version to v1.1

Refer to pkg/api/VERSIONING.md for compatibility information.

Upgrade path from v0.1.8:

- Deploy scheduler v0.1.9 BEFORE the updated autoscaler-agent.
- No requirements relating to vm-informant.

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

v0.1.1

v0.1.0