Documentation Grafana Enterprise Logs Set up Upgrade Upgrade the Helm chart to 3.0

Upgrading from v2.x

v3.x represents a major milestone for this chart, showing a commitment by the Loki team to provide a better supported, scalable helm chart. In addition to moving the source code for this helm chart into the Loki repo itself, it also combines what were previously two separate charts, grafana/loki and grafana/loki-simple-scalable into one chart. This chart will automatically assume the “Single Binary” mode previously deployed by the grafana/loki chart if you are using a filesystem backend, and will assume the “Scalable” mode previously deployed by the grafana/loki-simple-scalable chart if you are using an object storage backend.

As a result of this major change, upgrades from the charts this replaces might be difficult. We are attempting to support the 3 most common upgrade paths.

1. Upgrade from grafana/loki using local filesystem storage
2. Upgrade from grafana/loki-simple-scalable using a cloud based object storage such as S3 or GCS, or an api compatible equivalent like MinIO.

Upgrading from grafana/loki

The default installation of grafana/loki is a single instance backed by filesystem storage that is not highly available. As a result, this upgrade method will involve downtime. The upgrade will involve deleting the previously deployed loki stateful set, the running the helm upgrade which will create the new one with the same name, which should attach to the existing PVC or ephemeral storage, thus preserving you data. We still highly recommend backing up all data before conducting the upgrade.

To upgrade, you will need at least the following in your values.yaml:

yaml Copy

loki:
  commonConfig:
    replication_factor: 1
  storage:
    type: 'filesystem'

You will need to 1. Update the grafana helm repo, 2. delete the existing stateful set, and 3. upgrade making sure to have the values above included in your values.yaml. If you installed grafana/loki as loki in namespace loki, the commands would be:

console Copy

helm repo update grafana
kubectl -n loki delete statefulsets.apps loki
helm upgrade loki grafana/loki \
  --values values.yaml \
  --namespace loki

You will need to manually delete the existing stateful set for the above command to work.

Notable changes

The grafana/loki chart used Secret as storage for configuration. You can set .loki.existingSecretForConfig to continue using Secret or migrate your configuration to a ConfigMap. Specifying the Loki config in values.yaml is still available. In the old chart it was under .config, the new chart allows specifying either .loki.config or .loki.structuredConfig which takes precedence.

Similarly when using extraVolumes, the configuration is now nested under .singleBinary.extraVolumes or .read.extraVolumes + .write.extraVolumes if you decide to migrate to the Loki scalable deployment mode.

Dependencies

The grafana/loki chart was only used to install Loki. New charts since v3.x also bundle two dependencies - minio and grafana-agent-operator. If you have already installed either of these independently and wish to continue managing them separately, you can explicitly disable these dependencies in your values.yaml as shown in the following examples:

yaml Copy

minio:
  enabled: false

yaml Copy

monitoring:
  selfMonitoring:
    enabled: false
    grafanaAgent:
      installOperator: false

Upgrading from grafana/loki-simple-scalable

As this chart is largely based off the grafana/loki-simple-scalable chart, you should be able to use your existing values.yaml file and just upgrade to the new chart name. For example, if you installed the grafana/loki-simple-scalable chart as loki in the namespace loki, your upgrade would be:

console Copy

helm repo update grafana
helm upgrade loki grafana/loki \
  --values values.yaml \
  --namespace loki