-
Notifications
You must be signed in to change notification settings - Fork 25
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
Authentication Subsystem #60
Comments
Plugin created: |
The bulk of this ticket is hopefully implemented by e2369ec. the I like it! :) |
Missing docs and final touches on |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
There needs to be two Openstack roles:
kubernikus_admin
kubernikus_member
Generate certificates that use the principal from the Keystone token as username (CN). Depending on the Openstack the certificates organisation field is set to:
kubernikus:admins
kubernikus:members
This allows us to identify the user and her Openstack role. Then we preseed an RBAC rules into the customer's clusters, that add the
kubernikus:admins
group tosystem:masters
(or the same roles).In turn this also allows the customer to create their own RBAC rules for the
kubernikus:members
group. Management of who is allowed to access the Kluster is then possible using the usual Openstack role assignments.Revocation of the certificates is being handled by lowering the certificates expiration time. Suggestion would be 30d as default. This can be configured by the customer and adjusted to his security needs.
With 1.8 it will be possible to create plugins for
kubectl
. It will then be trivially easy to automate the certificate renewal similar tomonsoonctl
using a plugin.The text was updated successfully, but these errors were encountered: