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] - Allow changing Namespaces for TeamRoleBindings #764

Open
3 tasks
IvoGoman opened this issue Nov 19, 2024 · 0 comments · May be fixed by #813
Open
3 tasks

[FEAT] - Allow changing Namespaces for TeamRoleBindings #764

IvoGoman opened this issue Nov 19, 2024 · 0 comments · May be fixed by #813
Assignees
Labels

Comments

@IvoGoman
Copy link
Contributor

IvoGoman commented Nov 19, 2024

Priority

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

User Story

As a Organization Admin I would like to change the namespaces of a TeamRoleBinding, so that I can easily adapt to changes in a team's responsibility.

Description

The initial implementation of the TeamRoleBinding controller does not support changing the list of Namespaces. This is enforced in the webhook.

Changing the namespace should now be supported In order to make the TeamRoleBinding more usable.
This requires enhancing the status that tracks the deployment status of the TeamRoleBinding.

Acceptance Criteria

  • Admission webhook for TeamRoleBindings allows changing the list of namespaces but not removing all namespaces
  • Reconciliation of a TeamRoleBinding tracks the namespaces in each cluster to which the TRB is deployed
  • Ensure RoleBindings are removed from the namespaces in a cluster that no longer are part of .spec.Namespaces

Reference Issues

No response

@github-project-automation github-project-automation bot moved this to Sprint Backlog in Greenhouse Core Roadmap Nov 19, 2024
@Zaggy21 Zaggy21 self-assigned this Dec 10, 2024
@Zaggy21 Zaggy21 moved this from Sprint Backlog to In progress in Greenhouse Core Roadmap Dec 11, 2024
@Zaggy21 Zaggy21 linked a pull request Dec 17, 2024 that will close this issue
24 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In progress
Development

Successfully merging a pull request may close this issue.

2 participants