Especially when using GitOps approach to deploy DexIdP it makes not real sense to keep revisions of the deployments as those are actually kind of persisted inside the underlying SCM, which drives the deployment and its history.
What this PR does / why we need it
It simply adds the possibility to configure the revisionHistoryLimit property of the Deployment resource template, but keeps the default to 10.
Checklist
[x] Change log updated in Chart.yaml (see the contributing guide for details)
[x] Chart version bumped in Chart.yaml (see the contributing guide for details)
[x] Documentation regenerated by running make docs
Overview
Especially when using GitOps approach to deploy DexIdP it makes not real sense to keep revisions of the deployments as those are actually kind of persisted inside the underlying SCM, which drives the deployment and its history.
What this PR does / why we need it
It simply adds the possibility to configure the
revisionHistoryLimit
property of theDeployment
resource template, but keeps the default to10
.Checklist
Chart.yaml
(see the contributing guide for details)Chart.yaml
(see the contributing guide for details)make docs