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

Evaluate the requirement for having admin level permissions for rukpak controller #800

Open
varshaprasad96 opened this issue Jan 16, 2024 · 1 comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@varshaprasad96
Copy link
Member

varshaprasad96 commented Jan 16, 2024

Currently, we specify rukpak controller to have admin level permissions:

//+kubebuilder:rbac:groups=*,resources=*,verbs=*

This seems to be required to be able to manage the lifecycle of bundle resources effectively.

This issue is to evaluate the requirement for having this level of elevated permissions (Even if the outcome could be that we need to have it this way).

@varshaprasad96 varshaprasad96 changed the title Evaluate the requirement for having admin level permissions to rukpak controller Evaluate the requirement for having admin level permissions for rukpak controller Jan 16, 2024
Copy link

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

1 participant