If a project is deployed to a Kubernetes cluster with a Helm chart, FlexDeploy can do that automatically according to the configurations on this tab:

The screen contains a reference to a chart which can be a chart in the repository configured on the deploying endpoint, a folder with a chart, a chart package or URL.

Optionally, a Helm Release name can be provided to easily track all deployments on the endpoint. If it is unspecified, helm will generate a random name.

In order to deploy a helm chart to a K8s cluster, FlexDeploy uses the deploy operation of Helm plugin, which invokes helm upgrade --install command under the hood. So, the deployment workflow should contain a step as in this example:

If Chart Name and Release Name are unspecified, FlexDeploy will take the values from the Helm Configuration tab.

FlexDeploy overrides values of the chart with the values configured in the Chart Values list. These values are specified with Groovy scripts evaluated on-the-fly during the deployment. The scripts may reference any Project or Environment-Instance (available for the project) properties.

There is a smart suggester of available properties. Just start typing something from a property name and hit Ctrl-Space.