v0.3.2

What's Changed

• feat: Implement scale-to-zero support for BudAIScaler by @dittops in #4

Full Changelog: 0.3.1...0.3.2

---

Installation

Using Helm (OCI Registry)

helm install scaler oci://ghcr.io/budecosystem/charts/scaler \
  --version 0.3.2 \
  --namespace scaler-system \
  --create-namespace

Using Docker Image

docker pull ghcr.io/budecosystem/scaler:0.3.2

v0.3.1

What's Changed

• feat: allow maxReplicas=0 to completely disable workload by @dittops in #3

Full Changelog: 0.3.0...0.3.1

---

Installation

Using Helm (OCI Registry)

helm install scaler oci://ghcr.io/budecosystem/charts/scaler \
  --version 0.3.1 \
  --namespace scaler-system \
  --create-namespace

Using Docker Image

docker pull ghcr.io/budecosystem/scaler:0.3.1

v0.3.0

What's Changed

• feat: Implement scale-to-zero support for BudAIScaler by @dittops in #2

New Contributors

• @dittops made their first contribution in #2

Full Changelog: 0.2.1...0.3.0

---

Installation

Using Helm (OCI Registry)

helm install scaler oci://ghcr.io/budecosystem/charts/scaler \
  --version 0.3.0 \
  --namespace scaler-system \
  --create-namespace

Using Docker Image

docker pull ghcr.io/budecosystem/scaler:0.3.0

v0.2.1

• Introduced StartingPods configuration in the scaler CRD to manage how starting (not-ready) pods affect scale-up decisions.
• Added properties: bypassGateOnPanic, maxStartingPods, maxStartingPodPercent, and startingPodWeight to control scaling behavior based on starting pods.
• Updated ScalingContext interface and its implementation to include methods for retrieving starting pods configuration.
• Enhanced scaling algorithms (BudScaler and KPA) to consider starting pods when calculating effective replicas and determining scale-up gating.
• Implemented tests for effective replica calculations and scale-up gating logic based on starting pods.
• Added utility functions to count starting pods in the autoscaler.

---

Installation

Using Helm (OCI Registry)

helm install scaler oci://ghcr.io/budecosystem/charts/scaler \
  --version 0.2.1 \
  --namespace scaler-system \
  --create-namespace

Using Docker Image

docker pull ghcr.io/budecosystem/scaler:0.2.1

v0.2.0

• Implement scaling policies for BudAIScaler with support for multiple policies and selection criteria

---

Installation

Using Helm (OCI Registry)

helm install scaler oci://ghcr.io/budecosystem/charts/scaler \
  --version 0.2.0 \
  --namespace scaler-system \
  --create-namespace

Using Docker Image

docker pull ghcr.io/budecosystem/scaler:0.2.0

v0.1.0

Release Notes - v0.2.0

Features

Generic Prediction Metrics

The prediction system is now fully generic and works with any metrics. Users can specify which metrics from metricsSources to use for prediction and seasonal learning. This enables BudAIScaler to work with any workload type - not just LLM inference engines like vLLM or TGI, but also custom applications, databases, and non-AI services.

External Metrics Source

Fixed JSON parsing for external HTTP metric endpoints
Added fallback to generic JSON parsing when structured response fields are empty
External metrics now correctly handle flat JSON responses like {"metric_name": value}
Documentation

Added comprehensive documentation in the docs/ folder:

docs/prediction-algorithm.md - Detailed explanation of the 3-layer prediction system including time-series prediction, seasonal learning (168 time buckets with EWMA), and workload pattern detection
docs/scaling-hierarchy.md - Priority order of scaling inputs (Cost > Max > Schedule Hints > Min > Metrics/GPU/Prediction) with decision flow diagrams and example scenarios
CI/CD

Added GitHub Actions workflow for automated releases
Docker images published to ghcr.io/budecosystem/scaler
Helm charts published to oci://ghcr.io/budecosystem/charts/scaler
Added CI workflow for PR validation (lint, test, build, helm lint)
Installation

Helm (OCI Registry):
helm install scaler oci://ghcr.io/budecosystem/charts/scaler
--version 0.2.0
--namespace scaler-system
--create-namespace

Docker:
docker pull ghcr.io/budecosystem/scaler:0.2.0

Breaking Changes

None. The new predictionMetrics and seasonalMetrics fields are optional and default to the first metric in metricsSources for backward compatibility.

Upgrade Notes

No action required. Existing configurations will continue to work. To take advantage of the new generic prediction metrics, add the predictionMetrics and seasonalMetrics fields to your predictionConfig.