Agent version 2.11.0

Added

• New default container optimization policy
  We added a RequestsRaiseLimitsIfNeeded container optimization policy: Requests are always optimized; limits are optimized only if they already exist. If an existing limit is lower than what Optimize Live recommends, the limit is raised to Optimize Live’s recommended limit value.

  With this policy, limits are not lowered if they already exist, nor are they added if they don’t exist.

  Note: The default optimization policy is still RequestsOnly.

  Use the following annotation values (for details, see the product docs):

  live.stormforge.io/containers.cpu.optimization-policy: "RequestsRaiseLimitsIfNeeded"
  live.stormforge.io/containers.memory.optimization-policy: "RequestsRaiseLimitsIfNeeded"
  

• PatchPath annotations
  You can now use the following annotations to map a container resource value from a recommendation to where it belongs in the patchTarget:

  live.stormforge.io/containers.memory.limits.patch-path
  live.stormforge.io/containers.memory.requests.patch-path
  live.stormforge.io/containers.cpu.limits.patch-path
  live.stormforge.io/containers.cpu.requests.patch-path
  

Fixed

• We fixed a condition that caused an Agent panic with ownerless pods on clusters running older versions of spark-operator.

Security

• Upgraded the Prometheus agent to version 2.52.0

Known conditions

• When setting requests and limits patch-path annotations along with the DoNotOptimize policy, you will see values on patchpath fields (previously the fields were set with a -). Regardless of the patchpath, the recommendations will respect the policy. The same is true for limits patch-path annotations when using the RequestsOnly policy.