Is your feature request related to a problem? Please describe.
Bash files don't run well on Windows based containers!
Describe the solution you'd like
Would like an option in the helm chart values configuration to disable/disconnect the pre-stop-hook.sh setup in the worker-prestop-configmap.yaml, worker-deployment.yaml, worker-statefulset.yaml so that I can deploy a custom built Windows container for worker operations using the helm chart without worrying how a Windows container is going to handle the execution request of a bash script.
This could be enabled with a general flag setting in the values.yaml file specifying the container type, i.e. Windows or Unix with a default of Unix. Depending on the flag value, that bash script lines would be enabled or disabled.
Implementation of this functionality might allow the inclusion in the future of a custom Powershell script that executes the same functionality as the the Bash script.
Is your feature request related to a problem? Please describe.
Bash files don't run well on Windows based containers!
Describe the solution you'd like
Would like an option in the helm chart values configuration to disable/disconnect the pre-stop-hook.sh setup in the worker-prestop-configmap.yaml, worker-deployment.yaml, worker-statefulset.yaml so that I can deploy a custom built Windows container for worker operations using the helm chart without worrying how a Windows container is going to handle the execution request of a bash script.
This could be enabled with a general flag setting in the values.yaml file specifying the container type, i.e. Windows or Unix with a default of Unix. Depending on the flag value, that bash script lines would be enabled or disabled.
Implementation of this functionality might allow the inclusion in the future of a custom Powershell script that executes the same functionality as the the Bash script.
Describe alternatives you've considered
No response
Additional context
No response