homelab/traefik
1
0
Fork 0
Code Activity

clarify automatic service creation/assignment with labels

Browse source
This commit is contained in:
mpl 2019-09-26 12:48:05 +02:00 • committed by Traefiker Bot
parent c8fa059064
commit c6e783e7c3
6 changed files with 156 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/content/routing/routers/index.md
View file

@ -288,8 +288,14 @@ The middlewares will take effect only if the rule matches, and before forwarding
### Service
You must attach a [service](../services/index.md) per router.
Services are the target for the router.
Each request must eventually be handled by a [service](../services/index.md),
which is why each router definition should include a service target,
which is basically where the request will be passed along to.
In general, a service assigned to a router should have been defined,
but there are exceptions for label-based providers.
See the specific [docker](../providers/docker.md#service-definition), [rancher](../providers/rancher.md#service-definition),
or [marathon](../providers/marathon.md#service-definition) documentation.
!!! important "HTTP routers can only target HTTP services (not TCP services)."