-
Notifications
You must be signed in to change notification settings - Fork 936
Enabling OIDC authentication for Karmada API server #6144
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
Comments
I think that generally looks good to me. Could you please elaborate on what args you are expecting? And would like to work on it? |
Thanks Hongcai! The full list of OIDC flags (from
I believe the minimum used by most installs would be I'm happy to take a look into implementation. It would be great if aggregated API server supported this as well, though I guess that will be more complex, as it's not using the |
Sounds great! |
karmada-io#6144 Signed-off-by: Matt Newman <[email protected]>
karmada-io#6144 Signed-off-by: Matt Newman <[email protected]>
karmada-io#6144 Signed-off-by: Matt Newman <[email protected]>
@tw-mnewman Is there anything needs to do with this issue? |
@RainbowMango 👋 Since #6159, it's possible to enable OIDC when installing via Helm, but I don't think it's exposed in the other installation methods (e.g. |
Yeah, you are right. Thanks for the reminder. So, would you like to help? |
What would you like to be added:
Hi folks, currently when installing Karmada using
karmadactl
/kubectl karmada
/Helm there is no option to enable OpenID Connect (OIDC) based authentication for the Karmada API Servce.I've tested manually adding the
--oidc-*
arguments to thekube-apiserver
command used forkarmada-apiserver
, and it seems to work fine.I'd love to see support for setting these parameters through the formally supported installation options.
Why is this needed:
A lot of companies (including my current client) have configured existing Kubernetes clusters using OIDC for workforce user authentication, this will allow users to interact with the Karmada API Server using the same method, reducing overhead of provisioning service accounts for teams.
The text was updated successfully, but these errors were encountered: