How to prevent possible route collisions between groups?

Traefik
1

I am new to traefik and I have the following issue.

I would like to have one traefik server on http ports 80 and 443.

Software development groups will then start docker containers with the appropriate labels, and thus the appropriate rules, but in principle nothing prevents them from specify colliding routing rules and “take away” traffic from another group.

One easy fix would be a honor system where each group promises not to stomp on another, but it’s not really good enough for me. I checked multilayered routing, in particular this blog post

But it’s not clear if this does what I need. The routing hierarchy seems to be defined in the static configuration. I can’t seem to be able to say that the dynamic configuration from group A must be handled by child router A, and dynamic configuration from group B handled by child router B.

Is my requirement supported with multilayer routers, or should I have instead one global router, forwarding the request to independent root routers managed by each group?

Thanks

2

Can’t you solve it through requiring every group to have <group> in their router/service/middleware names?

It’s not bullet-proof, but simple and easy to remember. And if it’s forgotten one time, it still shouldn’t collide with another one.

Not sure how you would be able to solve this programmatically. Do groups have their own sub-domain?

3

no subdomains. I was hoping we could route to hostname/apps/group1 one group, and hostname/apps/group2 the other group, so that when they specify their application labels, they don’t need to specify the first part if not for url rewriting, and they would automatically end up in /apps/group1/myapp1 etc…