traefik

Configure Traefik reverse proxy routing, middlewares, TLS, and Kubernetes IngressRoute CRDs.

3|1|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/lukaskellerstein/claude-my-marketplace --skill traefik-lukaskellerstein
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: traefik
Source: https://github.com/lukaskellerstein/claude-my-marketplace/tree/main/plugins/infra-plugin/skills/traefik
Command: npx skills add https://github.com/lukaskellerstein/claude-my-marketplace --skill traefik-lukaskellerstein

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up Traefik as a reverse proxy or Kubernetes ingress controller involves many moving parts — entrypoints, routers, services, middlewares, TLS certificates, and CRDs — and misconfiguring any of them breaks traffic routing or security. This Skill provides production-tested configuration patterns so you can deploy and operate Traefik correctly without digging through scattered documentation. ## Core Features & Use Cases - Kubernetes Ingress Routing: Define IngressRoute and IngressRouteTCP resources with host/path matching, weighted load balancing, mirroring, and sticky sessions. - Middleware Library: Apply rate limiting, security headers, basic/forward auth (OAuth2-proxy), strip-prefix, circuit breakers, retries, compression, and reusable middleware chains. - TLS & Certificates: Terminate TLS via cert-manager ClusterIssuers, Traefik ACME cert resolvers, or strict TLSOption cipher policies. - Docker/Standalone Support: Configure static traefik.yml, watched dynamic file providers, and Docker Compose label-based routing. - Operations Guidance: Scrape Prometheus metrics, troubleshoot with kubectl commands, and follow production best practices. - Use Case: You need to expose a new microservice on Kubernetes with HTTPS, rate limiting, and security headers — the Skill walks you from Helm install through the IngressRoute and middleware chain. ## Quick Start Ask the assistant to help you deploy Traefik on Kubernetes with Helm and create an IngressRoute that routes app.example.com to your service with TLS and rate limiting.

Frequently Asked Questions about traefik

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Traefik IngressRoute on Kubernetes?▼

Define an IngressRoute CRD with apiVersion traefik.io/v1alpha1 specifying entryPoints, route match rules like Host(`app.example.com`), backend services, and a tls block. Attach middlewares by name and use certResolver or secretName for TLS.

How do I add rate limiting and security headers in Traefik?▼

Create Middleware resources with rateLimit (average, burst, period) and headers (frameDeny, contentTypeNosniff, stsSeconds) specs, then reference them by name from your IngressRoute. You can combine multiple middlewares into a reusable chain middleware.

Does Traefik work with cert-manager for Let's Encrypt certificates?▼

Yes, cert-manager provisions certificates via a ClusterIssuer using the ACME HTTP-01 challenge with the traefik ingress class. The IngressRoute then consumes the resulting secret through tls.secretName, or you can use Traefik's own ACME certResolver instead.

Can I use Traefik with Docker Compose instead of Kubernetes?▼

Yes, the Docker provider reads routing configuration from container labels such as traefik.http.routers and traefik.http.services. You combine a static traefik.yml for entrypoints and resolvers with watched dynamic files or labels for routers and services.

How do I troubleshoot Traefik routing not working?▼

Check Traefik pod logs with kubectl, inspect the loaded configuration via the API at /api/rawdata on port 9000, and verify IngressRoute and Middleware resources with kubectl describe. Temporarily setting the log level to DEBUG helps diagnose routing mismatches.

How do I integrate OAuth2-proxy authentication with Traefik?▼

Use a forwardAuth middleware pointing at the oauth2-proxy /oauth2/auth endpoint with trustForwardHeader enabled. The middleware can pass auth response headers like X-Auth-Request-User and X-Auth-Request-Email to your backend services.