Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[kube-prometheus-stack] fix the retentionSize value #4533

Closed
wants to merge 2 commits into from

Conversation

karloramone
Copy link
Contributor

What this PR does / why we need it

There is a bug in the chart related to the prometheus.prometheusSpec.retentionSize value.

In the default values currently there is specified value for prometheus.prometheusSpec.retention: 10d.
When you try to add the value prometheus.prometheusSpec.retentionSize it will also generate the prometheus.prometheusSpec.retention: 10d from those default values.

This is a problem because according to the docs only one of those values can be configured.

If both time and size retention policies are specified, whichever triggers first will be used.

Checklist

  • [ x] DCO signed
  • [x ] Chart Version bumped
  • [ x] Title of the PR starts with chart name (e.g. [prometheus-couchdb-exporter])

Signed-off-by: karloramone <karlo.krupljan@gmail.com>
Signed-off-by: Quentin Bisson <quentin.bisson@gmail.com>
@QuentinBisson
Copy link
Member

@karloramone where in the docs does it state that you can only configure one or the other? You can define both and Prometheus makes it an or between retention time and retention size. You can set the value to nil in your values if you do not want it

@QuentinBisson
Copy link
Member

I'm closing here as this is not a bug, feel free to reopen otherwise

@karloramone
Copy link
Contributor Author

@QuentinBisson Yes, looks like I misunderstood the docs and had some other problem. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants