Open source

Upgrading to v6.x

v6.x of this chart introduces distributed mode but also introduces breaking changes from v5x.


BREAKING: deploymentMode setting

This only breaks you if you are running the chart in Single Binary mode, you will need to set

deploymentMode: SingleBinary

BREAKING: lokiCanary section was moved

This section was moved from within the monitoring section to the root level of the values file.

BREAKING: topologySpreadConstraints and podAffinity converted to objects

Previously they were strings which were passed through tpl now they are normal objects which will be added to deployments.

Also we removed the soft constraint on zone.

BREAKING: externalConfigSecretName was removed and replaced.

Instead you can now provide configObjectName which is used by Loki components for loading the config.

generatedConfigObjectName also can be used to control the name of the config object created by the chart.

This gives greater flexibility in using the chart to still generate a config object but allowing for another process to load and mutate this config into a new object which can be loaded by Loki and configObjectName


After some consideration of how this chart works with other charts provided by Grafana, we decided to deprecate the monitoring sections of this chart and take a new approach entirely to monitoring Loki, Mimir and Tempo with the Meta Monitoring Chart.


  • There were conflicts with this chart and the Mimir chart both installing the Agent Operator.
  • The Agent Operator is deprecated.
  • The dependency on the Prometheus operator is not one we are able to support well.

The Meta Monitoring Chart is an improvement over the the previous approach because it allows for installing a clustered Grafana Agent which can send metrics, logs, and traces to Grafana Cloud, or letting you install a monitoring-only local installation of Loki, Mimir, Tempo, and Grafana.

The monitoring sections of this chart still exist but are disabled by default.

If you wish to continue using the self monitoring features you should use the following configuration, but please do note a future version of this chart will remove this capability completely:

  enabled: true
    enabled: true
      installOperator: true

Memcached is included and enabled by default

Caching is crucial to the proper operation of Loki and Memcached is now included in this chart and enabled by default for the chunksCache and resultsCache.

If you are already running Memcached separately you can remove your existing installation and use the Memcached deployments built into this chart.

Single Binary

Memcached also deploys for the Single Binary, but this may not be desired in resource constrained environments.

You can disable it with the following configuration:

  enabled: false
  enabled: false

With these caches disabled, Loki will return to defaults which enables an in-memory results and chunks cache, so you will still get some caching.

Distributed mode

This chart introduces the ability to run Loki in distributed, or microservices mode. Separate instructions on how to enable this as well as how to migrate from the existing community chart will be coming shortly.