Releases: neondatabase/autoscaling
Releases · neondatabase/autoscaling
v0.32.2
Fix for v0.32.1, just containing a fix to the generated neonvm.yaml, so that we don't have "neonvm-neonvm-runner-image-loader". See #933.
v0.32.1
Small release, three notable changes: 1. plugin: fix Score reserving when over-budget (#987) (fixes a critical bug with scheduler >= v0.31.0) 2. Remove go.mod dependency on controller-tools (#985) 3. neonvm: Move runner image env var into YAML (#988)
v0.32.0
Overall, relatively small release. One big item about adding support for virtio-mem. NOTE the breaking changes below. Features: - neonvm: Add support for virtio-mem (#970) Breaking changes: - neonvm: Make spec min/max/use resources required (#971) No protocol changes. Fixes: - neonvm-controller: Set podName only while Pending (#973) - neonvm: Use memory_hotplug.online_policy=auto-movable for virito-mem (#981) - This notably fixes OOM issues that can occur by running out of ZONE_NORMAL when there is a lot of hotplugged memory. Other changes: - neonvm-controller: Emit CpuInfo/MemoryInfo every reconcile (#974) Upgrade path from v0.31.0: - All VMs in the cluster must have spec min/max/use resources set. - All clients that may create VMs must set spec min/max/use resources. - NOTE: neonvm-controller still uses DIMM hotplug (instead of virtio-mem) by default. It IS NOT SAFE to roll back if any VMs are using virtio-mem; they will permanently break. Refer to #970 for more.
v0.31.0-k8s-1.27
Same as v0.31.0 but with 1.27 k8s API
v0.31.0
Small-ish release by number of commits, but some larger refactorings thrown in. NOTE: This release upgrades to k8s 1.26 ! No new features. No breaking changes. No protocol changes. Fixes: - neonvm-controller: Fix error in panic catching middleware (#965) - neonvm-runner: Exit with error if QEMU fails (#964) - neonvm-controller: Fix log sampling (#968) - (again) Other changes: - agent,api: Add support for fetching LFC metrics (#895) - Currently, this doesn't actually do anything! It's just setting up the piping so we can test it now and use it later. - plugin: Add transactions for speculative operations (#936) - plugin: Unify handleReserve+handleRequested (#936) - Upgrade k8s dependencies to 1.26.15 (#928) - util: Add taskgroup (#922) - neonvm-runner: Remove parted,sfdisk from final image (#966) - agent: Set log level to info (#969) Upgrade path from v0.30.x: - No ordering requirements.
v0.30.1-k8s-1.26
v0.30.1 but with 1.26 k8s API
v0.30.1
A hotfix after v0.30.0, only one change: neonvm-controller: bring back RecordSuccess for conflicting (#957
v0.30.0-k8s-1.26
v0.30.0 but with 1.26 k8s API
v0.30.0
Lots of internal changes, mostly tech debt and reliability improvements, but some bugfixes. Also of note: Kernel upgraded from 6.1.63 -> 6.1.92. Features: - api,agent/core: Make required ScalingConfig fields optional per-VM (#948) - neonvm-controller: replace failing reconciliation with per-VM failure interval (#949) No breaking changes. No protocol changes. Fixes: - neonvm-controller: Rework zap setup & disable sampling (#947) - neonvm-controller: Fix k3s cluster detection (#956) Other changes: - plugin: Remove vmStore from AutoscaleEnforcer (#904) - plugin: Handle Buffer in reserveResources() (#904) - plugin: Replace readClusterState with existing watch events (#904) - neonvm-controller: rename VirtualMachine -> VM (#942) - pg16-disk-test: add mkfifo (#944) - Use github.com/samber/lo.ToPtr everywhere (#946) - neonvm: Switch to kernel 6.1.92 (#950) Upgrade path from v0.29.x: - No ordering requirements.
v0.29.3-k8s-1.26
v0.29.3 but with 1.26 k8s API