Auto-discover, route, and terminate TLS automatically
Day 1
Configuration, Routing & Kubernetes
- Traefik architecture: Entrypoints, routers, middlewares, services, providers — the Traefik mental model
- Static vs dynamic configuration: traefik.yml vs IngressRoute CRDs — what goes where and why
- Provider model: Docker, Kubernetes Ingress, Kubernetes CRD, file — auto-discovery from multiple sources
- Routers: Rule syntax — Host, PathPrefix, Headers, Methods, query strings — building routing rules
- Middlewares: BasicAuth, RateLimit, StripPrefix, Headers, RedirectScheme, Compress — chaining behaviors
- TLS: Let's Encrypt ACME (HTTP-01 and DNS-01 challenges), certificate resolvers — zero-config TLS
- Kubernetes Ingress integration: Annotations and IngressRoute CRD comparison — when to use each
- TCP and UDP routing: Non-HTTP services through Traefik — databases, game servers, custom protocols
- Dashboard: Enabling securely, authentication, read-only API — operational visibility into routing rules
- Traefik Hub and Pilot: Optional cloud management overview
What your team walks away with
A fully configured Traefik setup: auto-discovered routing, Let's Encrypt TLS, middleware chains, and Kubernetes Ingress — with no manual certificate management.
- Configure Traefik with Docker and Kubernetes providers for auto-discovery
- Build routing rules and middleware chains for real-world traffic patterns
- Automate TLS with Let's Encrypt ACME — HTTP-01 and DNS-01
- Deploy and configure IngressRoute CRDs for fine-grained Kubernetes routing
Book the Traefik training
A focused one-day training — natural follow-on to K3s since Traefik is the default ingress controller bundled with K3s.
Get in touch