The Helm Chart of Step is versioned independently of Step itself. This page contains the release notes of the Helm Chart. For the release notes of Step refer to Release notes

Major release 1.5.0

New features

Support Grid Proxy file caching (only available from Step 31+): the Grid Proxy now caches the files it downloads from the primary grid and re-serves them to the local agents, avoiding repeated high-latency downloads from the primary cluster. See Grid Proxy file caching.
- Grid Proxy working directory can now be persisted via a PersistentVolumeClaim (gridproxy.persistence.*). Persistence must be enabled explicitly, see File caching and persistence and the migration guide.
- Grid Proxy file manager cleanup is now configurable (gridproxy.config.fileManagerConfiguration.*), mirroring the agent configuration.
Added the possibility to configure additional classpaths entries for the Step Controller via the controller.config.additionalClasspaths setting.
Added possibility to deploy a ListenerSet K8s API object (Gateway API) via the listenerSets list. A ListenerSet lets a Step release define its own listener — hostname, port and TLS certificate — on a Gateway managed by another team. See Accessing Step via ListenerSet and the ListenerSet configuration samples for details.
Added possibility to set the agent forker working directory via values (Java agent only)
Updated default Controller memory settings to mitigate the JVM native memory fragmentation and prevent the Controller container from being OOM-killed: MALLOC_ARENA_MAX is now set to 2 (controller.config.MALLOC_ARENA_MAX) and the JVM Metaspace is capped to 384M (controller.config.MAX_METASPACE_SIZE_MB). We recommend to set these values explicitly in your values file when migrating, see the migration guide for details.

Minor release 1.4.1

New features

Added the possibility to define a PersistentVolumeClaim retention policy on each Agent pool (agent.pools[N].persistentVolumeClaimRetentionPolicy) StatefulSets, to control whether the PersistentVolumeClaims created from their volumeClaimTemplates are retained or deleted when the StatefulSet is scaled down or deleted. See Control the retention of the StatefulSet PersistentVolumeClaims.

Major release 1.4.0

New features

Added possibility to include additional hosts in the default TLS entry (alongside ingress.host)
Added possibility to deploy an HTTPRoute K8s API object (Gateway API). An HTTPRoute and a standard Ingress can co-exist. See Accessing Step via HTTPRoute and the HTTPRoute configuration samples for details.
Added possibility to define host aliases for the Grid Proxy (gridproxy.hostAliases)
Added possibility to override the container timezone (TZ environment variable)
Default agent runtime image updated to use the new naming convention: <repository>/<product>/agent/runtime:<tag>> (previously <repository>/<product>/base:<version>-debian-12-slim)

Breaking changes

The old /base agent runtime image naming convention is no longer supported. If agent.pools[N].image is set to an image containing /base, a Helm warning is displayed. See the Agent Runtime Image Migration guide for details.

Minor release 1.3.3

New features

Added possibility to specify the client connect timeout for provisioning request from controller to grid proxy

Minor release 1.3.2

New features

Added possibility to fine tune Grid Proxy configuration
Controller agent provisioning settings now have dedicated value entries

Minor release 1.3.1

New features

Added possibility to define a service account name to create / user for the Grid Proxy

Major release 1.3.0

New features

Agents possibility to configure Java Agent forker (only available from Step 29+)
Extended grid proxy configuration capabilities (only available from Step 29+)
Removed support for PostgresqlHA as Step database
Added Helm tests suite
Added possibility to define the Controller termination grace period

Bug fixing

Fixed couple of issues when the Controller is not used (grid proxy usage)

Minor release 1.2.5

Bug fixing

Fixed indentation when a secret name for the default Ingress host is specified

Minor release 1.2.4

New features

Added possibility to specify a secret name for the default Ingress host
Added possibility to specify the default Ingress host path and pathPrefix
Added possibility to specify probes for the Controller

Minor release 1.2.3

New features

Technical release only, no new feature nor bug fix

# Minor release 1.2.2

New features

Controller config has a new attribute to allow usage of configuration placeholders

Minor release 1.2.1

New features

Agent pools: values “image” and “agentImage” now use the Helm “tpl” function to resolve other settings from the root values context
Added possibility to deploy any extra Kubernetes manifest

Bug fixing

Decommissioned the Controller configuration snippet related to Astra plugin

Major release 1.2.0

Note that this Chart release is only compatible with Step 27 onward. See compatibility matrix at the end of the page for more details.

New features

Agents now uses a binaries copy mode: one could now use a custom Docker image for the Agents without the need to include the Step Agent itself. See custom docker image requirement and the material request section for details.
Added support for Agent cleanup configuration (file manager and execution context cache)
Added possibility to define additional path for the default ingress host
Added host aliases support for Controller and Agents
Added tolerations support for Controller and Agents

Bug fixing

Incorrect warning message about persistence being disabled when using PostgreSQL as database

Minor release 1.1.5

New features

Added possibility to define additional path for the default ingress host
Added host aliases support for Controller and Agents

Bug fixing

Incorrect warning message about persistence being disabled when using PostgreSQL as database

Minor release 1.1.4

New features

Added support for Agent file manager configuration

Minor release 1.1.3

New features

Added possibility to override Controller and Java Agent logback configuration
Preparation for OpenShift support

Minor release 1.1.2

New features

Added possibility to expose Java Agent JVM metrics
Added possibility to add extra data on Controller and Agent default configMap
Added support for extraInitContainers in both Controller and Agents

Minor release 1.1.1

New features

Technical release only

Major release 1.1.0

New features

possibility to configure automatic agent provisioning (see Agent Provisioning configuration for more details)
ingressClassName is now optional
Controller persistentVolumeClaims access modes are now configurable

Bug fixing

Controller init containers resources were not customisable

Major release 1.0.0

New features

possibility to add Agent probes
prerequisites to support NodeJS Agent pools
removed old MySQL support

Bug fixing

wrong default Service Account name for the Controller when RBAC is not used
wrong MongoDB init container name used to wait for the database to be available on the Controller Pod

Minor release 0.0.15

New features

possibility to add topologySpreadConstraints to Pods
removed useless Controller configuration items
migrated MongoDB component management to sub-chart, refer to the MongoDB migration task page for instructions
possibility to add extraVolumeClaimTemplates in Controller and Agents Pods
possibility to configure affinity in Controller and Agents Pods

Bug fixing

Controller init container empty data folder when persistence is enabled

Minor release 0.0.14

New features

added Ingress extraRules and extraTLS configuration possibilities
added Step Controller UI customization possibility (from values file)

Bug fixing

fixed incorrect conditional statement in Controller configmap

Step compatibility matrix

Step version	Chart version
29	1.3.0+
28	1.2.0+
27	1.2.0+
26	1.1.0 to 1.1.5
25	1.0.0
24 and earlier	0.0.14 to 0.0.15