From 4fcf7bf2de1bd2e55ba909089f18e9d993ef4b30 Mon Sep 17 00:00:00 2001 From: Manuel Zapf Date: Mon, 27 Apr 2020 11:32:05 +0200 Subject: [PATCH] Add sentence about the resource namespace and middleware --- docs/content/routing/providers/kubernetes-crd.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/content/routing/providers/kubernetes-crd.md b/docs/content/routing/providers/kubernetes-crd.md index 18a462956..f07d50573 100644 --- a/docs/content/routing/providers/kubernetes-crd.md +++ b/docs/content/routing/providers/kubernetes-crd.md @@ -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).