How to manage certificates and HTTPS in Kubernetes deployments of FME Server

Introduction

When FME Server is deployed with Kubernetes it comes with a self signed certificate by default.

In production workflows this is not be recommended, and many organisations will want to use their own certificate. There are two options for doing this:
 

Deploying FME Server in Kubernetes with a custom certificate

Our documentation provides instructions on how to upload the certificate to the cluster and how to reference them in the helm install command.
 

Using a third-party load balancer with TLS termination

Customers may wish to use their own load balancer on top of the Kubernetes cluster. In this case, they may want FME Server to be installed without SSL. The certificate will terminate at the load balancer.

To do this, the parameter deployment.disableTLS can be set to ‘true’ (default value is false). You can find the list of parameters and default values on Github.