Agent version 2.9.0

Added

• Support for setting deployment thresholds (via UI, CLU, annotations)
  To help reduce pod churn, you can now define minimum change thresholds to prevent Optimize Live from automatically applying new recommendations.

  You can define a percent change, unit amount change, or both, by using the following methods:

  • UI: On the Config tab of workload details page, as part of the Automatic Deployment setting.
  • Annotations: live.stormforge.io/auto-deploy.thresholds.* annotations. See the examples in the Auto-deploy topic.
  • CLI: --auto-deploy-thresholds-min* arguments as part of the stormforge edit workloads handler command.

  For details, see Auto-deploy thresholds in the Auto-deploy settings topic.

• Changes to the default optimization policy and limit-to-request ratio
  The default optimization policy is now RequestsOnly. Previously, it was RequestsAndLimits.

  When the optimization policy is set to RequestsAndLimits, the new default limit-to-request ratio is 2.0 (increased from 1.2). Optimize Live will not update containers using a 1.2 ratio to the new default 2.0 ratio. In the UI, a 1.2 limit-to-request ratio is now shown as Custom.

Security

• To address CVE-2023-44487, we upgraded grpc-go to version 1.56.3.