Performing the Kubernetes Deployment

Use the Helm tool to deploy FME Flow with Kubernetes. This tool allows you to set various deployment parameters, depending on need.

Add the Safe Software Helm Repository

helm repo add safesoftware https://safesoftware.github.io/helm-charts/

At a minimum, you must provide the FME Flow release and build number.

helm install fmeflow safesoftware/fmeflow --set fmeflow.image.tag=2024.1

After running the install command, you can connect to the FME Flow Web User Interface on https://<hostname>. For more information, see:

Create a values.yaml file that passes user-supplied parameter values to the Helm chart.

To get the default Helm chart values file, run:

helm show values chart>

For example:

helm show values safesoftware/fmeflow

To write the values to a file:

helm show values safesoftware/fmeflow >> values.yaml

For more information on value files, see the Helm Docs.

A current list of supported parameters for FME Flow can be found on GitHub.

The following are parameters you may want to change in the values.yaml file:

Expand for Parameters

Parameter	Example or Possible Value	Description
fmeflow.image.tag	2024.1	Set to the FME Flow major release version you want to deploy, such as 2024.0 or 2024.1.
fmeflow.engines[].name	“standard-group”	The name of the engine group. This can be changed, particularly if creating multiple engine groups.
fmeflow.engines[].engines	2	Controls the number of engine pods to start.
fmeflow.engines[].type	STANDARD \| DYNAMIC	Controls the type of engine to start.
deployment.hostname		Set to the IP address of the ingress controller noted previously.
deployment.numCores	2	Starts two FME Flow Core pods for fault tolerance and load balancing.
deployment.useHostnameIngress	true \| false	If DNS is set up for the ingress controller, specify the DNS name for deployment.hostname and leave this parameter to true. If not, specify false.

Ensure the values.yaml file is saved, then reference it with the helm install command:

helm install <name> <chart> -f values.yaml

For example:

helm install fmeflow safesoftware/fmeflow -f values.yaml

If you make changes to the values.yaml file after FME Flow is installed (such as to scale FME Flow engines), use the helm upgrade command:

helm upgrade <name> <chart> -f values.yaml

For example:

helm upgrade fmeflow safesoftware/fmeflow -f values.yaml

To set the number of FME Engines, use the values.yaml file and set the fmeflow.engines[] parameters listed in Parameters to Note (above). Alternatively, see Defining FME Engines, Queue Control, and Streams to a Kubernetes Deployment.

Note Changing the number of FME Engines in the FME Flow Web User Interface is not supported in Kubernetes deployments.

helm uninstall fmeflow -n <namespace_name>