Version 3.0.0

Added

  • ARM v8 support

Changed

  • Upgraded Kubernetes libraries to 0.25.5
  • Upgraded Controller Runtime to 0.13.1
  • The controller image and Helm chart are now distributed via registry.stormforge.io
  • Kubernetes resource names have changed to include “pro”
  • Trusted trial jobs can now get a STORMFORGE_TOKEN
  • Setup tasks must have a name
  • The manager exits when it receives an authorized error
  • The JSON logging format has changed and levels are now configurable
  • Installation no longer includes default RBAC

Deprecated

  • Polling for UI triggered experiment runs will be removed in the next release

Removed

  • The setuptools image has been removed. Setup tasks must have an image or Helm chart.

Fixed

  • Trial finalizers are cleaned up when setup tasks are no valid
  • All trial job pods must be terminated for a trial to complete

Upgrading

CLI

Previous versions of Optimize Pro included a dedicated CLI. Starting with v3, the StormForge CLI is distributed (and must be upgraded) separately from the Optimize Pro controller running in your cluster. You can run stormforge check version to ensure you are running the most up-to-date CLI. You can check what version of Optimize Pro is running in your cluster by running stormforge check optimize-pro.

From v2

If you are upgrading from version 2.x, you must fully uninstall the v2 controller before installing the v3 controller (due to changes in the resource names). To uninstall, run stormforge uninstall optimize-pro (or stormforge reset for older versions of the CLI). Note that uninstalling will remove the Experiment CRD, causing all experiments in the cluster to be deleted: Be sure to back up the experiment manifests outside the cluster before uninstalling. (Your trial data is stored on the StormForge servers and need not be backed up.)

Experiment Manifests

When upgrading Optimize Pro, be sure to upgrade your StormForge CLI and run the stormforge fix command to update your experiment manifests. You should also run stormforge check experiment to ensure there are no known issues with your experiments.

RBAC Changes

Previous versions of Optimize Pro included cluster-wide permissions to modify common resources (such as deployments). Starting in v3, these cluster roles are not included by default. After running stormforge fix over your experiment manifests, run the stormforge rbac command to generate the necessary roles and bindings for running your experiment.

Last modified June 27, 2024