Web / Traefik Interview questions
What is the difference between Traefik's Ingress support and the IngressRoute CRD?
Traefik can act as an Ingress controller for standard Kubernetes Ingress resources, interpreting the common rules and tls fields, plus Traefik-specific behavior added through annotations.
| Ingress | IngressRoute (CRD) |
| Portable across any Ingress controller | Traefik-specific, not portable to other controllers |
| Advanced features via annotations (limited, string-based) | Advanced features as native, typed spec fields |
| Middleware reuse is awkward | Middlewares are first-class, referenced by name |
Teams that need to stay portable across ingress controllers tend to stick with Ingress plus annotations, while teams fully committed to Traefik often prefer IngressRoute for its cleaner expression of routers, weighted services, and middleware chains.
Both can run side by side on the same cluster, since Traefik's Kubernetes providers for Ingress and for the CRD operate independently and simply contribute their own resources into the same merged dynamic configuration.
More Related questions...