Skip to content

On Premise

This documentation describes how to perform the version upgrade operation of an on-premise TraefikEE cluster.

Backing Up the Outdated Cluster

Follow the documentation on backing up your cluster to generate a backup archive. This archive will be used to create your new up-to-date cluster.

Upgrading traefikee and traefikeectl

The first thing you should do in order to upgrade the version of your TraefikEE cluster is to upgrade the version of your traefikeectl and traefikee tools: download the latest version of the binaries here and here, make sure they are executable and add them to your path.

Run traefikeectl version and traefikee version to ensure that you have the right versions installed.

Replacing the Outdated Cluster

The current way to upgrade your cluster is to start a new one running in parallel to the first one, and once it is up and reachable, to uninstall the outdated cluster.

In order to start your new cluster, without conflicting with the previous one, you will have to install it with a different cluster name. You will then need to add the --clustername option to every command you run with traefikee and traefikeectl.

  1. Run the same traefikee bootstrap command as you did for your previous TraefikEE installation, with a different cluster name and specifying the --frombackup option with the backup archive you previously generated
  2. Wait for your new cluster to be up and reachable
  3. Redirect the traffic to your new cluster. This could be done by updating the external DNS entry to point to the new load balancer service's IP, or by editing your L4 load balancer's configuration, for example
  4. Ensure that your applications are reachable through the new cluster
  5. Interrupt all processes of the previous cluster in order to uninstall it

You should now have your new cluster up and running, up to date and without having any dropped traffic to your applications.