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.

Sign up for GitHub

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

Jump to bottom

Limit Fleet CRD to One Instance per Namespace #382

Open
Xieql opened this issue Sep 8, 2023 · 1 comment
Open

Limit Fleet CRD to One Instance per Namespace #382

Xieql opened this issue Sep 8, 2023 · 1 comment
Assignees
@Xieql
Labels
kind/feature

Comments

@Xieql
Copy link
Contributor

Xieql commented Sep 8, 2023

What would you like to be added:
A mechanism to restrict the creation of Fleet CRD instances to just one per namespace, possibly using an admission controller.

Why is this needed:
Currently, users can create multiple Fleet instances within a single namespace, which contradicts our design.
Limiting this to one instance per namespace will prevent potential conflicts（such as in backup controller） and maintain system integrity.
@Xieql Xieql changed the title Enforce Singleton Constraint for Fleet CRD Instances per Namespace Limit Fleet CRD to One Instance per Namespace Sep 8, 2023
@Xieql
Copy link
Contributor Author

Xieql commented Sep 8, 2023

/assign

@Xieql Xieql mentioned this issue Oct 23, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Xieql Xieql

Labels
kind/feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fleet: init fleet webhook and ensure single fleet per namespace Xieql/kurator
1 participant
@Xieql