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.