-
Notifications
You must be signed in to change notification settings - Fork 83
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
Centrally managed technical user support #357
Comments
Hi @dkistner we @stackitcloud would really appreciate this feature and would be willing to put effort into it. Is there any way we can help with the implementation for it? |
Hi @brumhard, |
Hi @dkistner, |
Hey @dkistner, |
Hi @JuliusSte, so this feature consists from our point of view out of two parts:
The 1. is in development and already on its way, but for 2. we could indeed need some help. The implementation would look very similar to the cloudprovider webhook in the Azure extension ref. Let me know if you wanna give it a try. If you want we can also have a chat on this before. |
How to categorize this issue?
/area security
/kind enhancement
/priority 3
/platform openstack
What would you like to be added:
Similar like for Azure we can implement a central approach to manage technical users for Shoot clusters. The technical users would be provided centrally in the
Keystone
by yhe Gardener operators and users would need to grant the technical users (provided by the Gardener operator) access to their Openstack projects with proper permissions.Why is this needed:
Same reasons as for Azure. Gardener operators could take care of the technical user and rotate their secrets on regular basis. Users are not obligated to provide an own technical user.
cc @donistz, @RaphaelVogel
The text was updated successfully, but these errors were encountered: