chore(mimir): update chart/5.4.0 / app/2.13.0

[eyenx]

Description

Updates Mimir Chart to version 5.4.0, Mimir to version 2.13.0

Important Changes

Chart

• A number of timeout settings are improved:

  • Fine-tuned termination grace periods for all components. This helps to ensure that components can shut down gracefully, without interrupting queries or write requests.
  • Continuous test and smoke test containers now use the Mimir image, as the continuous test code is now part of Mimir. As a result, the image section in the values file now replaces smoke_test.image and continuous_test.image, and the latter two are removed.

• Notable enhancements are as follows:

  • Experimental support for a dedicated ruler query path. With a dedicated set of queriers, query-frontends, and query-schedulers, outages and slow-downs on the main query path don’t affect rule evaluations.

Application

• In Grafana Mimir 2.13 the following behavior has changed:
  • The default Docker image grafana/mimir is now based on the distroless image gcr.io/distroless/static-debian12. See Debugging distroless container images for more details on how to work with distroless images.
  • Error logs in the ingester are now sampled at 10% by default. Sampled log lines contain (sampled 1/10). The cortex_discarded_samples_total metric still tracks all discarded samples.
  • Anonymous usage statistics now include actual CPU usage instead of available CPU cores.
  • Continuous-test is no longer a standalone binary and is now part of Mimir as its own target. The published Docker image has been updated to use the new packaging.
  • The following deprecated configuration options are removed in Grafana Mimir 2.13:
  • The configuration option -log.buffered, which was deprecated in 2.11 and is now enabled by default.

Checklist

• This PR contains a description of the changes I'm making
• I updated the version in Chart.yaml
• I updated the changelog with an artifacthub.io/changes annotation in Chart.yaml, check the example in the documentation.
• I updated applicable README.md files using pre-commit run
• I documented any high-level concepts I'm introducing in docs/
• CI is currently green and this is ready for review
• I am ready to test changes after they are applied and released