Traefik Enterprise Edition

A multi controller cluster is healthy as long as the nodes can reach a quorum to elect a new leader in case of failure. The quorum is (N/2)+1 where N is the initial number of controllers. If the number of healthy nodes goes below this number, the cluster must be recovered before it will resume normal operations.

Proxies will continue to route the requests based on the last known configuration.

Even after installation is complete, TraefikEE won't listen to any ports on the proxies until a static configuration specifying entrypoints is applied.

When using some kind of persistent volume in the host / pod / container, you can boot it up again and watch the logs to see if the state was automatically recovered. If the cluster data were lost, please refer to the Backup and Restore section for more recovery options.

You can update or change the cluster configuration without losing requests as long as the entrypoints are not changed.

Yes, you can enable more than one provider in your static configuration.

Yes. The only limitation is that the configuration files have to be replicated on every host executing a controller.

We recommend installing with teectl, even when customization is needed, as it will generate all the required manifest files for your platform. Manual installation is required for on-premise users.

Traefik has the concept of a default entrypoint to use for internal services, like the API or Ping, when they are enabled but no entrypoint is specified.

The traefik default internal entrypoint will use port ':8080'. When setting up your own custom entrypoint to the same port, make sure you are not using the traefik internal one by specifying the entrypoint value on internal services like the API, Metrics, Dashboard and Ping.