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

[feature request] deploy specified CRDs and its corresponding controllers #1624

Open
ColdsteelRail opened this issue May 15, 2024 · 0 comments
Assignees

Comments

@ColdsteelRail
Copy link

ColdsteelRail commented May 15, 2024

What would you like to be added:
Deploy specified CRDs and controllers, which could be achieved by ( just from my consideration ):

  1. Support some feature-gates;
  2. Or, document the minimal closure sets of CRDs (means bug-free if only which CRDs and controllers are deployed) clearly in the installation manual.

Why is this needed:
Once users deploy Kruise by Helm or make deploy, all CRDs and controllers will installed by default (except feature-gates like KruiseDaemon can enable or disable daemon and crr or imagepulljob controller). For some users just want to use specified CRD in their clusters.

For me, I just want to install the CRR (includes necessary CRDs needed to boot kruise-daemon) to recreate containers, and I don't want install the other CRDs and controllers.

@ColdsteelRail ColdsteelRail changed the title [feature request] deploy specified CRD and its corresponding controllers [feature request] deploy specified CRDs and its corresponding controllers May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants