Deploying with an NFS Client Provisioner

Warning  Safe Software has not yet tested an NFS Client Provisioner deployment for production workflows.

You can deploy an NFS Client provisioner to use an existing NFS Server to provision volumes for Kubernetes to use. The provisioner must be installed before FME Flow and should not be removed before FME Flow is removed from the cluster.

  1. Follow the instructions here to deploy the NFS client provisioner using the settings of your existing NFS Server.
  2. Install FME Flow.

    3. Example:

    Note  The following script assumes the storage class name of the NFS Client Provisioner is unchanged from its default, "managed-nfs-storage."
    • Helm v2: helm install --namespace <fmeserver-namespace> -n <fmeserver-deployment-name> safesoftware/fmeserver-2023-0 --set fmeserver.image.tag=<fmeVersion>,deployment.numCores=2,storage.fmeserver.class=managed-nfs-storage,storage.fmeserver.accessMode=ReadWriteMany
    • Helm v3: helm install <fmeserver-deployment-name> safesoftware/fmeserver-2023-0 --namespace <fmeserver-namespace> --set fmeserver.image.tag=<fmeVersion>,deployment.numCores=2,storage.fmeserver.class=managed-nfs-storage,storage.fmeserver.accessMode=ReadWriteMany

    Parameters

    Note  To add other parameters, if required, see the relevant topic under Deploying FME Flow with Kubernetes.
    • fmeserver-namespace: Kubernetes namespace in which to install FME Flow.
    • fmeserver-deployment-name: Helm deployment name, arbitrary.
    • fmeVersion: FME Flow major release version (examples: 2022.2 or 2023.0).