Replies: 2 comments 1 reply
-
Hi @rltbg |
Beta Was this translation helpful? Give feedback.
1 reply
-
I should be able to provide some help tomorrow
… Message ID:
<sevensolutions/traefik-oidc-auth/repo-discussions/171/comments/13590010@
github.com>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am encountering an issue while implementing the plugin on my Kubernetes cluster, which includes multiple namespaces. Since Traefik is deployed in its own namespace, it cannot access secrets located in other namespaces. When I deploy my applications in a specific namespace, I declare the middleware with the plugin secret using the syntax recommended in the getting started guide,
urn:k8s:secret:oidc-secret:pluginSecret
to reference the plugin secret. Despite this configuration, the middleware works correctly and OIDC authentication is performed without any issues.I am therefore wondering how URN links work in this context, because in theory, Traefik should not be able to load a secret located in a different namespace unless the secret is actually being loaded from the application's own namespace. This raises the question of whether, when I declare the middleware with a URN such as urn:k8s:secret:oidc-secret:pluginSecret, the secret is indeed retrieved from the current namespace of the application, or if there is a specific mechanism that allows Traefik to access it despite namespace isolation.
Beta Was this translation helpful? Give feedback.
All reactions