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.

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

[Documentation] Adding precisely how to reference Kubernetes-CRD Middleware from other providers #6318

Closed
Aniem opened this issue Feb 14, 2020 · 3 comments
Projects
Milestone

Comments

@Aniem
Copy link

Aniem commented Feb 14, 2020

Do you want to request a feature or report a bug?

Feature

What did you expect to see?

A Kubernetes-crd Middleware lives in kubernetes, and as such, has a kubernetes name (for instance fooName) and a kubernetes namespace (for instance barNS))
If one needs to configure traefik via another provider a routing using that middleware (for instance kubernetes Ingress middleware with the current master branch (commit 7c430e5 in my case) ), one needs to give the correct traefik name of the namespace. After some testing and a view of the dashboard, it appears the correct name is barNS-fooName@kubernetescrd

As this might be unclear for people getting familiar, I suggest the rule ( <K8SNamespace>-<K8SName>@kubernetescrd) be written in the documentation.

Furthermore, and I'll probably create some bug reports on that later, this naming rule can generate collision, for instance if one has a namespace foo-bar containing a middleware baz and a namespace foo containing a middleware bar-baz. This might require to change to traefik naming rule for kubernetes-crd, possibly before getting that rule written down in the documentation. I suggest using a . as separator, as this character is forbidden in kubernetes objet names.

@ldez ldez added area/documentation area/provider/k8s kind/enhancement a new or improved feature. priority/P2 need to be fixed in the future and removed status/0-needs-triage labels Feb 14, 2020
@ldez ldez added this to issues in v2 via automation Feb 14, 2020
@bradjones1
Copy link
Contributor

Refs #6322

@SantoDE
Copy link
Collaborator

SantoDE commented Apr 23, 2020

Hello!

I just raised a PR for that #6719. Is that enough for your request?

@traefiker traefiker added this to the 2.2 milestone Apr 27, 2020
v2 automation moved this from issues to Done Apr 27, 2020
@traefiker
Copy link
Contributor

Closed by #6719.

@traefik traefik locked and limited conversation to collaborators Jul 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
v2
Done
Development

No branches or pull requests

5 participants