Web / Traefik Interview questions
What is the difference between Traefik's Gateway API support and the traditional IngressRoute CRD?
The Kubernetes Gateway API is a vendor-neutral, upstream Kubernetes API for describing traffic routing (via resources like Gateway and HTTPRoute), designed as the eventual successor to both Ingress and controller-specific CRDs across the ecosystem.
| IngressRoute CRD | Gateway API |
| Traefik-specific, not portable to other controllers | Vendor-neutral, works across any compliant controller |
| One resource type maintained by Traefik | Split into roles: Gateway (infra) and HTTPRoute (routing), owned by different teams |
| Immediate access to every Traefik-specific feature | Newer, evolving feature parity as the spec matures |
Traefik implements the Gateway API as a provider alongside its own CRD, so the two can coexist on the same cluster; teams prioritizing portability and role-based separation between infrastructure and application teams tend to move toward Gateway API, while teams wanting every current Traefik feature immediately still often reach for IngressRoute.
More Related questions...