-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rephrase the traefik.backend
definition in documentation
#4317
Rephrase the traefik.backend
definition in documentation
#4317
Conversation
Signed-off-by: Damien DUPORTAL <[email protected]>
Signed-off-by: Damien DUPORTAL <[email protected]>
Signed-off-by: Damien DUPORTAL <[email protected]>
@ldez : I've taken your feedback and explanations in account. The code from
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| `traefik.tags=foo,bar,myTag` | Adds Traefik tags to the Docker container/service to be used in [constraints](/configuration/commons/#constraints). | | ||
| `traefik.protocol=https` | Overrides the default `http` protocol | | ||
| `traefik.weight=10` | Assigns this weight to the container | | ||
| `traefik.backend=foo` | Overrides the container name by `foo` in the generated name of the backend. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is accurate for backends which are not segments. However, when we use segments, as explained in #4284, the backend name is being set as backend-<container-name>-backendsite1
where traefik.backend=backendsite1
has been specified by
the user.
Signed-off-by: Damien DUPORTAL [email protected]
What does this PR do?
This PR rephrases the definition of the label
traefik.backend
in the documentation.Motivation
As underlined in #4284 and #4024, the actual definition of the label
traefik.backend
leads to confusion: the provided value is expected to be the full backend name.
But it is an internal naming, which depends on dynamic name generation,
and the provided value is used as a suffix, to discriminate backends from each others.
So here is this PR, trying to rephrase to make it more close to reality, and to avoid false expectations when using the API.
More
Additional Notes
Here is a nice gopher image, because gophers are cute: