Deploying with Kubernetes to a Production Environment

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

At a minimum, you must provide the FME Server release and build number. These values are available here.

Example: Install FME Server 2019.0.0 (build 19260)

helm repo update

helm install -n fmeserver safesoftware/fmeserver-2019.0.0 --set fmeserver.image.tag=19260

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

• Accessing the Web User Interface
• Logging in to the Web User Interface

Install with a Custom Hostname

Often you do not want to install using localhost. To override, set the deployment.hostname parameter.

helm install -n fmeserver safesoftware/fmeserver-2019.0.0 --set fmeserver.image.tag=<fmeBuildNumber>,deployment.hostname=<your.custom.hostname>

Delete an FME Server Deployment

helm delete --purge fmeserver

Scale FME Engines

To set the number of FME Engines, use the FME Server Helm chart (install or upgrade command) and set the following parameter:

deployment.numEngines=<numberOfDesiredEngines>

Note: The upgrade command is untested by Safe Software.

We recommend that you only scale FME Engines using Helm rather than the Kubernetes dashboard. Using the Kubernetes dashboard risks putting the deployment out of sync with Helm, which means the value reverts if something is updated through Helm in the future.

Note: Changing the number of FME Engines in the FME Server Web User Interface is disabled in Kubernetes deployments.