v0.16.3

Another single-PR release, this time for #442, which is a significant PR
that adds handling in the autoscaler-agent to connect directly to the
vm-monitor, if it's listening on the port that the vm-informant *was* on.

v0.16.2

Tiny release just adding #480, to allow configuring what vm-builder sets
as the admin user for the neon-postgres cgroup.

v0.16.1

Hotfix release containing #478 and #479, fixing a config field name and
a bug in the plugin's Score method that caused scheduling failures.

v0.16.0

This release contains a couple new features, but mostly groups together
a handful of recent hotfix releases.

No breaking API changes.

Features:

- neonvm/builder: Add flags to enable informant/monitor (#477)
- plugin: Penalize underfull nodes during Score (#476)

Fixes:

- agent: Fix endpointAssignedAt for VMs added with endpoint (#463)
  - Hotfixed as v0.15.1
- neonvm/runner: Handle hybrid cgroup v1/v2 systems (#467)
  - Hotfixed as v0.15.3
- neonvm/builder: Add additional fields to vm-monitor conn str (#469)
  - Hotfixed as v0.15.4
- agent/metrics: Fix runner state metrics deletion hanlding (#471)
  - Hotfixed as v0.15.5
- Disable zap's enabled-by-default log sampling (#475)

No protocol changes.

Other changes:

- agent/metrics: Initialize runnersCount label pairings to 0 (#465)
  - Hotfixed as v0.15.2
- neonvm/builder: Remove cgexec entrypoint prefix (#477)

Upgrade path from v0.15.x:

- No ordering requirements. Note that vm-builder now requires adding
  '-enable-informant' and '-enable-monitor' to keep the previous
  behavior.

v0.15.5

Yet another hotfix, this time to hopefully fix an issue with the agent's
runner state metrics. See #470 and #471 for more.

v0.15.4

Another hotfix release: We weren't providing a host or port in the
vm-monitor's connection string, which the informant didn't need because
they were included by default in Go's pq postgres driver, but they *are*
needed in the monitor.

v0.15.3

Another hotfix release, fixing neonvm-runner for hybrid cgroup v1/v2
setups. The only difference between v0.15.2 and this is #467.

v0.15.2

Another hotfix release, adding better metrics initialization to #459,
from PR #465.

v0.15.1

Hotfix release, fixing incorrectly setting podStatus.endpointAssignedAt
to nil, which caused staging to crash-loop with a nil pointer
dereference on startup. This release contains only #463 on top of v0.15.0

v0.15.0

This release contains a new NeonVM feature, a security improvement,
a new component (vm-monitor), and BREAKING CHANGES TO METRICS!

Breaking API changes:

Features:

- neonvm: Add user-defined additional InitContainers (#433)

No "fixes".

No protocol changes.

Other changes:

- informant: Move scaling logic into (new!) vm-monitor (#362)
- agent: Use fixed port for informant -> agent connections (#447)
- agent: Move "runner" state tracking from GaugeFuncs to GaugeVec (#447)
  - The following metrics were removed:
    - autoscaling_errored_vm_runners_current
    - autoscaling_panicked_vm_runners_current
    - autoscaling_agent_tracked_vms_current
    - autoscaling_vms_unsuccessful_communication_with_informant_current
    - autoscaling_billed_vms_unsuccessful_communication_with_informant_current
  - The following metric was added:
    - autoscaling_agent_runners_current

Upgrade path from v0.14.2:

- No ordering requirements, but all components must be upgraded before
  there's *any* usage of NeonVM's new extraInitContainers.