This is documentation for the next version of Loki. For the latest stable release, go to the latest version.
Migrate to three scalable targets
This guide will walk you through migrating from the old, two target, scalable configuration to the new, three target, scalable configuration. This new configuration introduces a
backend component, and reduces the
read component to running just a
QueryFrontend, allowing it to be run as a kubernetes
Deployment rather than a
Before you begin:
We recommend having a Grafana instance available to monitor both the existing and new clusters, to make sure there is no data loss during the migration process. The
loki chart ships with self-monitoring features, including dashboards. These are useful for monitoring the health of the cluster during migration.
To Migrate from a “read and write” to a “backend, read and write” deployment
- Make sure your deployment is using a new enough version of Loki
This feature landed as an option in the helm chart while still in the
main branch of Loki. As a result, depending on when you run this migration, you may neeed to manually override the Loki or GEL image being used to one that has the third,
backend target available. For Loki, add the following to your
loki: image: repository: "grafana/loki" tag: "main-f5fbfab-amd64"
For GEL, you’ll need to add:
enterprise: image: repository: "grafana/enterprise-logs" tag: "main-96f32b9f"
- Set the
legacyReadTargetflag to false
Set the value
read.legacyReadTarget to false. In your
read: legacyReadTarget: false
- Upgrade the helm installation
helm upgrade on your installation with your updated