Skip to content
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

[FEAT] - TeamRBAC adoption #388

Open
2 of 4 tasks
Tracked by #263
IvoGoman opened this issue Jul 25, 2024 · 2 comments
Open
2 of 4 tasks
Tracked by #263

[FEAT] - TeamRBAC adoption #388

IvoGoman opened this issue Jul 25, 2024 · 2 comments
Assignees

Comments

@IvoGoman
Copy link
Contributor

IvoGoman commented Jul 25, 2024

Priority

(Medium) I'm annoyed but I'll live

Description

As an Operator I would like to have default Developer/Admin TeamRoles, so that I can use these to manage my teams access on the onboarded clusters.

As part of driving the internal Greenhouse adoption there should be the option to superseed the cc-rbac chart with Greenhouse's TeamRBAC

Prerequisite is the implementation of #77 & #485

Acceptance Criteria:

  • onboarding of at least 1 QA cluster to Greenhouse
  • Introduction of TeamRoles which are equivalent to cc-rbac's (Cluster)Roles
  • Documentation of available default TeamRoles
  • Creation of TeamRoleBindings to rollout the rbac/v1 resources to the QA cluster, side-by-side with the existing RBAC

Reference Issues

No response

@IvoGoman
Copy link
Contributor Author

IvoGoman commented Aug 5, 2024

This requires #415 #485 to be implemented

@IvoGoman
Copy link
Contributor Author

Blocked by #701

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In progress
Development

No branches or pull requests

2 participants