Is your feature request related to a problem? Please describe.
Hi,
The variable worker.cleanUpWorkDirOnStart makes it possible to cleanup the workdir on workers startup but it's been implemented for statefulset only. Is there any good reason it's not implemented in deployments?
Nodes disk space keeps growing up because of unreleased disk space after a worker crashes, gets restarted or even upgraded.
Some may have good reasons for not using statefulsets: local high performance disks required, workers and nodes autoscaling, etc...
Describe the solution you'd like
I wish the cleanup initContainer was implemented in the worker deployment just like it is for statefulsets
I'd be happy to submit a patch
Describe alternatives you've considered
None that I can think of
Additional context
No response
Is your feature request related to a problem? Please describe.
Hi,
The variable
worker.cleanUpWorkDirOnStartmakes it possible to cleanup the workdir on workers startup but it's been implemented for statefulset only. Is there any good reason it's not implemented in deployments?Nodes disk space keeps growing up because of unreleased disk space after a worker crashes, gets restarted or even upgraded.
Some may have good reasons for not using statefulsets: local high performance disks required, workers and nodes autoscaling, etc...
Describe the solution you'd like
I wish the cleanup initContainer was implemented in the worker deployment just like it is for statefulsets
I'd be happy to submit a patch
Describe alternatives you've considered
None that I can think of
Additional context
No response