What would you like to be added:
I would like to expose the worker pool size for ContainerRecreateRequest (CRR) processing in kruise-daemon as a configurable command-line flag (e.g., --crr-workers).
Currently, this value is hardcoded to 32 in pkg/daemon/containerrecreate/crr_daemon_controller.go. This change introduces a flag to allow cluster admins to tune concurrency based on their node sizes and workload pressure.
Why is this needed:
As highlighted by a TODO comment in the codebase, this hardcoded value limits the flexibility of the daemon.
- Performance: In very large clusters, 32 workers might not be enough to handle high-frequency in-place updates efficiently.
- Resource Management: On smaller or resource-constrained nodes, admins may want to reduce this number to save daemon resources.
Exposing core concurrency limits as configurable flags follows standard Kubernetes controller practices and improves the scalability of OpenKruise.
What would you like to be added:
I would like to expose the worker pool size for
ContainerRecreateRequest(CRR) processing inkruise-daemonas a configurable command-line flag (e.g.,--crr-workers).Currently, this value is hardcoded to
32inpkg/daemon/containerrecreate/crr_daemon_controller.go. This change introduces a flag to allow cluster admins to tune concurrency based on their node sizes and workload pressure.Why is this needed:
As highlighted by a
TODOcomment in the codebase, this hardcoded value limits the flexibility of the daemon.Exposing core concurrency limits as configurable flags follows standard Kubernetes controller practices and improves the scalability of OpenKruise.