-
Notifications
You must be signed in to change notification settings - Fork 10
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
[Request] Kubernetes RBAC auth proxy #629
Comments
Keycloak might do the job, not entirely sure if it can drop in as a k8s auth proxy replacement but at the least it can be configured to have its own user accounts or to hook up to an external OAuth provider (just maybe not the cluster internal one?) This sounds like it would do something similar: https://github.com/jwalton/kube-auth-proxy . But I'm not sure from reading this if it supports an OAuth interactive login flow for browser usage or if it is only meant for programmatic access like kube-rbac-proxy. I'm not even sure if generic Kubernetes' internal auth server supports interactive OAuth login flows, so supporting this feature on non-OpenShift might require connecting to a separate external OAuth provider. |
@grzesuav in the meantime, along with #630, I would recommend you try something like this:
|
got it, was hoping that this setup was already done by someone who can share its experience. Will try to figure out something, however I m usnure if I will have time to experiment with keycloack etc |
Please do share any findings you have, if you do find the time. We would really love to have a better authentication/authorization system for non-OpenShift users as well, but we have to make decisions where and how to focus our efforts, and OpenShift takes priority. |
Current Behavior
I can configure cryistat only via basic auth
Expected Behavior
I want to use sth like openshift rbac - https://github.com/cryostatio/cryostat-operator/blob/cryostat-v3.0/config/crd/bases/operator.cryostat.io_cryostats.yaml#L4887 - to allow users with specific permission in kubernetes to execute actions against target Vm in given namespace
Steps To Reproduce
n/a
Environment
Anything else?
Keycloak was suggested in #622 (reply in thread) - it would be valuable for users to have some example in documentation
The text was updated successfully, but these errors were encountered: