Replies: 3 comments 1 reply
-
|
Currently Omni always takes the role of OIDC provider for Kubernetes access. |
Beta Was this translation helpful? Give feedback.
-
|
Also when you access Kubernetes API via Omni, Omni impersonates to Kubernetes as the user performing the operation and a base role. So you can bind Kubernetes RBAC to the user pretty much same way as you do it with Dex. Dex shouldn't offer anything that Omni Kubernetes access already does. |
Beta Was this translation helpful? Give feedback.
-
|
When you skip Omni, you also skip Kubernetes API load-balancer, so this should be something you manage outside of Omni. With that said, nothing should prevent you from plugging in OIDC auth. If you have some specific steps you need to take, and you need help to do that with Omni, please point us towards these steps. If there is something on Omni side which blocks you from doing so, we can dig into that. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For a customer we're looking into setting up a self-hosted Omni instance and rolling out client clusters (for other teams).
One of the things we'd like to do is use our existing authentication and authorization setup that uses dex with an auth backend. Is it possible to configure dex as an additional OIDC authentication source in an omni managed cluster?
I've found the Strucuted Auth Config and this article https://blog.palark.com/kubernetes-structured-authentication-config-explained/ seems to suggest that it is possible, but what steps would need to be taken to make this work in an Omni cluster?
Is this even possible and is there any guide available on how to do this?
//edit: I'm aware that with omni itself it is possible to almost reach feature parity with this setup, however the client clusters should not be dependent on Omni for user auth.
Beta Was this translation helpful? Give feedback.
All reactions