The MediaMachine Runbook for Traefik

MediaMachine.io is an IaaS platform for user-generated video content and we use Traefik as the reverse proxy in our network layer.

In a previous post, we talked about how Traefik fits into our infrastructure and helps us serve requests with ease. This runbook is an extension to that - an overview of things we found important to highlight for someone looking to know more about running Traefik themselves including useful configuration snippets.

PS: Some of the configuration is AWS centric but the general concepts and Traefik specific configuration applies more broadly.

We currently use Datadog for monitoring Traefik. If you're running a Datadog agent on your instance, it is typically set to listen on port 8125.

It was fairly straightforward for us to simply run multiple Traefik instances with support from Consul. Since we run Consul in our environment, our service containers running on docker advertize their IP addresses (and routing metadata) to Consul.

Traefik has built-in support to pull in updates from consul at fixed intervals (https://doc.traefik.io/traefik/providers/consul-catalog/). This makes spinning multiple Traefik instances for HA simply plug-and-play since each instance can independently fetch updates from Consul without extra coordination overhead.

Leave a Comment