You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added:
Deploy specified CRDs and controllers, which could be achieved by ( just from my consideration ):
Support some feature-gates;
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.
The text was updated successfully, but these errors were encountered:
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
What would you like to be added:
Deploy specified CRDs and controllers, which could be achieved by ( just from my consideration ):
Why is this needed:
Once users deploy Kruise by Helm or
make deploy
, all CRDs and controllers will installed by default (except feature-gates likeKruiseDaemon
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.
The text was updated successfully, but these errors were encountered: