OTK installation on ephemeral GW requires db maintenance schedule job to be run as k8s CronJob. Added ability to configure the success and failure history limit which controls the number of success and failure jobs to be kept.
Benefits
Customers will be able to keep the desired history of the jobs.
Drawbacks
None
Applicable issues
fixes #
Additional information
Checklist
[x] Chart version bumped in Chart.yaml according to semver.
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [charts/gateway])
[x] If the chart contains a values-production.yaml apart from values.yaml, ensure that you implement the changes in both files
Description of the change
OTK installation on ephemeral GW requires db maintenance schedule job to be run as k8s CronJob. Added ability to configure the success and failure history limit which controls the number of success and failure jobs to be kept.
Benefits
Customers will be able to keep the desired history of the jobs.
Drawbacks
None
Applicable issues
Additional information
Checklist
Chart.yamlaccording to semver.[charts/gateway])values-production.yamlapart fromvalues.yaml, ensure that you implement the changes in both files