Upgrading to a Patch Build in Kubernetes

When an FME Server build is released, three tags are created for each component’s image. For example, if the released build is 20238, these tags are named 20238, 20238-latest, and 20238-20200511, where 20200511 is the date the image was released.

The available tags for each FME Server component can be found on Dockerhub or Quay.io. From within any of the repositories under the safesoftware organization (fmeserver-core, fmeserver-engine,...), search for a build number (for example, 20238) to find all of the tags for that build.

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, 20238-20200523), and the other tags (for example, 20238 and 20238-latest) are 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, 20238 or 20238-latest).

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