Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add sentence about the resource namespace and middleware #6719

Merged
merged 4 commits into from
Apr 27, 2020
Merged

Add sentence about the resource namespace and middleware #6719

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3fe3acc
Add sentence about that the ressource namespace is automatically appe…
SantoDE Apr 22, 2020
87d10fa
address feedback
SantoDE Apr 22, 2020
7bf7d37
fix spelling
SantoDE Apr 23, 2020
efda45f
review.
ldez Apr 23, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 6 additions & 4 deletions docs/content/routing/providers/kubernetes-crd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -618,10 +618,12 @@ Register the `Middleware` [kind](../../reference/dynamic-configuration/kubernete

!!! important "Cross-provider namespace"

As Kubernetes also has its own notion of namespace, one should not confuse the kubernetes namespace of a resource
(in the reference to the middleware) with the [provider namespace](../../middlewares/overview.md#provider-namespace),
when the definition of the middleware comes from another provider.
In this context, specifying a namespace when referring to the resource does not make any sense, and will be ignored.
As Kubernetes also has its own notion of namespace, one should not confuse the kubernetes namespace of a resource
(in the reference to the middleware) with the [provider namespace](../../middlewares/overview.md#provider-namespace),
when the definition of the middleware comes from another provider.
In this context, specifying a namespace when referring to the resource does not make any sense, and will be ignored.
Additionally, when you want to reference a Middleware from the CRD Provider,
you have to append the namespace of the resource in the resource-name as Traefik appends the namespace internally automatically.

More information about available middlewares in the dedicated [middlewares section](../../middlewares/overview.md).

Expand Down