-
Notifications
You must be signed in to change notification settings - Fork 42
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
Tenant Autoenrolling feature - api & operator #877
Tenant Autoenrolling feature - api & operator #877
Conversation
Hi @giacoliva. Thanks for your PR. I am @kingmakerbot.
Make sure this PR appears in the CrownLabs changelog, adding one of the following labels:
|
ba04f74
to
79baa75
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some initial comment on the actual implementation :)
9279479
to
e031daa
Compare
/deploy-staging |
b7d9e1c
to
5e5d47b
Compare
/deploy-staging |
/merge |
Tenant autoenrolling feature kc fix lint fix broken link fix
31a3133
to
d9dbc14
Compare
/merge |
Your staging environment has been correctly teared-down! |
Description
Workspaces can now set AutoEnroll features with two flags in the Spec (no auto enroll / enroll request and manager's approval / completely self enroll)
Tenants can now autoenroll in Workspaces enabled (with
user
orcandidate
role depending on settings)Tenants are able to edit themselves in order to add or remove Workspaces with
autoEnroll
enabledHow Has This Been Tested?
Environment:
KinD with CRDs installed, Tenant Operator and Webhooks running. Keycloak not configured.
kubectl
api - Tenant edit as root userkubectl
api - Tenant edit as tenant user role (kubectl --as <tenantname>
)kubectl
api - Workspace edit as root usergraphql
- Tenant & Workspace edit as default user