Bug: jobConfigs.suspend: true doesn't works in case of helm devtron apps

[prakarsh-dt]

📜 Description

The following configurations do not include suspend: true when manifest generation is done for comparison while editing deployment template as well as when it is deployed to the target cluster.
The issue seems to be from the KubeVersion condition as it works fine after removal of this line, however the helm template works fine with it

devtron/scripts/devtron-reference-helm-charts/cronjob-chart_1-5-0/templates/_job_template_spec.yaml

Line 15 in 4874646

{{- if semverCompare ">1.20" .Capabilities.KubeVersion.GitVersion }}

Deployment template config

jobConfigs
  suspend: true 

Affected areas

CD

Additional affected areas

None

Prod/Non-prod environments?

Non-prod

Is User unblocked?

Yes

How was the user un-blocked?

TEMPORARILY - By doing some changes from the backend/DB

Impact on Enterprise

Users were unable to suspend the execution of job which affected the execution of dependent jobs.

👟 Steps to replicate the Issue

1. Create a devtron application selecting chart type as Job and Cronjob.
2. Create a Helm CD pipeline.
3. Set jobConfigs.suspend: true and kind: Job
4. Deploy it, suspend: true would not reflect in the Job manifest deployed.
5. Check manifest generation in the deployment template, suspend: true will not appear there as well in the generated manifest.

👍 Expected behavior

suspend: true should reflect in the job manifest as well as generated manifest in deployment template.

👎 Actual Behavior

suspend: true not reflecting in the job manifest as well as generated manifest in deployment template.

☸ Kubernetes version

EKS 1.27, EKS 1.28

Cloud provider

AWS, GCP

🌍 Browser

Chrome

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[github-actions]

Final Score: 50