Upgrading to a Patch Build in Kubernetes

When an FME Server build is released, two tags are created for each component’s image. For example, if the release version is 2021.2, these tags are named 2021.2 and 2021.2-20211029, where 20211029 is the date the image was released.

The available tags for each FME Server component can be found on Dockerhub.

Patch Builds

Images of each build are patched periodically with security updates. When this occurs, each image is released again with the current date as a suffix to the build number (for example, 2021.2-20211030). As well, the original tag (for example, 2021.2 is updated to refer to the most recently released version of the build. With this in mind, if it is preferable to lock down to a specific image and avoid updating to a patched version, use the timestamped tags. Otherwise, to always use the latest version of a build, use the non-timestamped tag (for example, 2021.2).

To upgrade to a patched image in a Kubernetes deployment

  1. Add the FME Server Helm repository and the values file that were initially used to deploy FME Server. Run:

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

  2. Update fmeserver.image.tag in the values file to the desired tag. Run:

    3. >> helm upgrade --namespace <namespace> safesoftware/fmeserver-<version> -f values.yml

See Also