Upgradejob history limits

[haasad]

Summary

As engineer maintaining many clusters
I want an upgradejob history limit
So that upgradejobs (and its owned resources) don't pile up endlessly

Context

Currently there is no pruning of upgradejobs. Upgradejobs and all its owned resources like jobs triggered by upgradejobhooks etc. accumulate endlessly.

A configurable upgradejob history limit with a sane default would mitigate this.

Out of Scope

No response

Further links

https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#jobs-history-limits

Acceptance Criteria

• Old upgradejobs are pruned based on a configurable upgradejob history limit in the upgradeconfig
• https://kb.vshn.ch/oc4/references/architecture/upgrade_controller.html updated with new fields

Implementation Ideas

Use same approach as job history limit for kubernetes cronjobs