change to upgrade job values

[soumyapattnaik]

Special notes for your reviewer:

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

• [x] DCO signed
• [x] Chart Version bumped
• [ ] Variables are documented in the values.yaml or README.md
• [ ] Title of the PR starts with chart name (e.g. [velero])

[jenting]

Why do we require to increase the memory limits?

[soumyapattnaik]

Why do we require to increase the memory limits?

Please refer to below PR by my team member who did it for azure backup. In some customer we observed that upgradejob were getting OOMKilled after the maintenance window, they only got mitigated after they increased the limits to 512

earlier PR- https://github.com/vmware-tanzu/helm-charts/pull/514

[anshulahuja98]

@jenting can we uncomment https://github.com/vmware-tanzu/helm-charts/pull/524/files and bump up memory based on this PR. This number has worked well for us in downstream usage.

[anshulahuja98]

CC @qiuming-best

[qiuming-best]

@jenting lint-test failed with checking the chart version, should we bump up the version? or could someone approve it directly?

As I've committed to this PR, I cannot approve it now.

[jenting]

@qiuming-best yez, the Chart version should upgrade as well.

[anshulahuja98]

@qiuming-best what are your thoughts on uncommenting the values?

[anshulahuja98]

For version bump I'll ask @soumyapattnaik

[jenting]

Please don't uncomment, user could overwrite the value by their own. The comment value is the suggestion, not the mandatory value.

[anshulahuja98]

Alright sure Have pinged @soumyapattnaik to bump the chart version, we can approve post that and checkin.

[soumyapattnaik]

updated chart.yaml to 6.0.1

[jenting]

Could you please help bump the version?