deploymentMode of type Job or Cronjob should not have main container commands and args set in separate jobspec and cronjobspec sections.
It only complicicate things in templates, end user might find this counter intuitive.
This should be rewritten so that main container in those deploymentModes inherit the command and args from image value just like regular deployments and statefulsets.
For now (up untill version 2.x) old command and args values from jobspec and cronjobspec should take priority, and deprecation warning message should be printed in NOTES.txt if user is still using them.
Update deprecation warning in docs and values as well.
deploymentModeof type Job or Cronjob should not have main container commands and args set in separatejobspecandcronjobspecsections.It only complicicate things in templates, end user might find this counter intuitive.
This should be rewritten so that main container in those deploymentModes inherit the command and args from
imagevalue just like regular deployments and statefulsets. For now (up untill version 2.x) old command and args values fromjobspecandcronjobspecshould take priority, and deprecation warning message should be printed in NOTES.txt if user is still using them.Update deprecation warning in docs and values as well.