Agent version 2.4.0

Added

• Support for setting default workload values at the cluster level
  You can now use a configuration file or command line arguments as part of the helm install command to set default values for all workloads in a cluster. See the examples below.

  Configuration file: Create a .yaml file and set the workload- and container-level values.

  clusterDefaultConfig:
      schedule: P1D
      containersCpuRequestsMin: 100m,istio-proxy=50m
  

  Command line arguments:

  --set clusterDefaultConfig.schedule=P1D \
  --set clusterDefaultConfig.containersCpuRequestsMin=100m,istio-proxy=50m
  

• Support for setting default workload values at the namespace level

  You can now use annotations to set default workload values at the namespace level. Namespace-level values override cluster-level values.

  Add the annotations to the metadata.annotations section of the namespace values file.

   apiVersion: v1
   kind: Namespace
   metadata:
   annotations: 
       live.stormforge.io/schedule: "P1D"
       live.stormforge.io/containers.cpu.requests.min: "100m,istio-proxy=50m"
   creationTimestamp: "2023-07-20T17:28:42Z"
   labels:
       kubernetes.io/metadata.name: kube-public
   name: kube-public
   resourceVersion: "9"
   uid: <UID>
   spec:
   ...
  

Changed

• Updated the Helm installation to simplify proxy configuration

  • You can now add --set proxyUrl=http://proxy.example.com to the helm install command to specify a proxy server.

  • The corresponding no_proxy variable is now seeded as follows with several RFC 1918 addresses: no_proxy:127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16

    If these seeded values meet your organizaton’s needs, you no longer have to create a separate proxy.yaml file as described in this advanced installation scenario in the product docs.

• Updated the Helm installation to expose Prometheus scrape interval
  In typical installations, you don’t need to change this interval — by default, the Prometheus scrapes for metrics every 15s.

  If StormForge Support requests that you change this interval, you can change it by adding --set prom.scrapeInterval=INTERVAL to the helm install command, replacing INTERVAL with the suggested frequency.

Fixed

• We now handle workload updates more gracefully, correcting an issue that caused controller panic.