What's new in StormForge
Monthly summaries of StormForge updates
Entries say when a change needs a new Agent or CLI version; everything else applies automatically.
July 2026
-
Schedule time zone shown in workload settings
The Schedule section of a workload’s Settings tab displays the time zone its schedule expressions are evaluated in. -
Workload expiration extended from 14 to 28 days
Workloads that stop reporting now remain available for 28 days before they expire, doubled from the previous 14 days.
June 2026
- StormForge Agent 3.0
A singlestormforgeHelm chart now installs the Agent and Applier together, replacing the separatestormforge-agentchart. Upgrading from v2 is a breaking change that requires migration. See StormForge Agent releases and Migrate v2 to v3.
May 2026
- CPU throttling visibility
The Workloads page includes a CPU throttling column, and the workload details page includes a CPU throttling chart, so you can see which containers are hitting their CPU limits and how often.
March 2026
- HPA settings shown on the workload details page
Workloads managed by a Horizontal Pod Autoscaler now show their HPA settings on the workload details page. See HPA for how StormForge adjusts target utilization when it changes resource requests.
February 2026
- Recommendations applied without restarting Pods
The webhook apply methods now use Kubernetes in-place Pod resizing by default, updating requests and limits on running Pods instead of triggering a rollout. Requires Applier v2.12.0 or later and Kubernetes v1.33 or later; on earlier Kubernetes versions these methods fall back to a rollout or defer the change until the next restart. See Apply settings.