generated from cloudoperators/repository-template
-
Notifications
You must be signed in to change notification settings - Fork 1
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] - Deny creation of Plugins #829
Labels
Comments
gciezkowski-acc
added a commit
that referenced
this issue
Jan 9, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 10, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 14, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 14, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 14, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 14, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 14, 2025
24 tasks
gciezkowski-acc
added a commit
that referenced
this issue
Jan 27, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 27, 2025
gciezkowski-acc
added a commit
that referenced
this issue
Jan 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Priority
Medium
User Story
No response
Description
The PluginPreset should become the default way to deploy Plugins. Therefore, it should not be possible to create new Plugin resources. Instead a PluginPreset scoped to a single cluster should be used.
Acceptance Criteria
Reference Issues
No response
The text was updated successfully, but these errors were encountered: