promtheus-adapter: add configurable revisonHistoryLimit to deployment #6202
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it
Which issue this PR fixes
This PR introduces a new optional value to the
prometheus-adapterHelm chart to allow users to configure therevisionHistoryLimitfield on the Deployment resource.By default, Kubernetes sets
revisionHistoryLimitto10. However, users may wish to increase or decrease this number to suit their rollback or resource retention strategies.Special notes for your reviewer
Checklist
[prometheus-couchdb-exporter])