Documentationbreadcrumb arrow Grafana Lokibreadcrumb arrow Set upbreadcrumb arrow Installbreadcrumb arrow Install using Helmbreadcrumb arrow Install monolithic Loki
Open source

Install the monolithic Helm chart

You can use Grafana Cloud to avoid installing, maintaining, and scaling your own instance of Grafana Loki. Create a free account to get started, which includes free forever access to 10k metrics, 50GB logs, 50GB traces, 500VUh k6 testing & more.

This Helm Chart installation deploys Grafana Loki in monolithic mode within a Kubernetes cluster.

Note

As of March 16, 2026, the Loki Helm Chart is being maintained by Grafana Champions and the Grafana Community in the Grafana-community/helm-charts repository. Please open issues and pull requests for the chart against the Grafana-community repo.

Tip

With the move to the Grafana-community repository, the chart numbering has changed. Major version updates signal breaking changes in the chart. For more information, refer to the README.

Note

As of the community Helm chart version 12.0.0, SingleBinary has been renamed to Monolithic. If you are using SingleBinary deployment mode, you have to explicitly set deploymentMode: Monolithic in your values file to avoid breaking changes.

Prerequisites

Single Replica or Multiple Replicas

There are two ways to deploy Loki in monolithic mode:

  1. Single Replica: Run Loki with a single replica. This mode is useful for testing and development or if you are planning to run Loki as a meta-monitoring system.
  2. Multiple Replicas: Run Loki with multiple replicas. This mode is useful for high availability. This mode is less economical than microservice mode, but it is simpler to operate. We recommend running at least three replicas for high availability.

Once you have selected how many replicas you would like to deploy, choose the appropriate values.yaml configuration file below and then continue with the deployment steps.

Single Replica

Deploying the Helm chart with a single replica deploys the following components:

  • Loki (1 replica)
  • Loki Canary (1 DaemonSet)
  • Loki Gateway (1 NGINX replica)
  • Chunks cache (1 StatefulSet)
  • Results cache (1 StatefulSet)
  • Minio (optional, deprecated — see warning below)

Create the configuration file values.yaml:

Note

You must specify commonConfig.replication_factor: 1 if you are only using 1 replica, otherwise requests will fail.

Warning

The built-in MinIO subchart is deprecated and will be removed on 2026-10-31. Setting minio.enabled=true without also setting ignoreMinioDeprecation: true causes chart rendering to fail with chart v17+. Use the workaround shown below only for temporary testing. For production, configure an external object storage backend instead.

YAML 
loki:
  commonConfig:
    replication_factor: 1
  schemaConfig:
    configs:
      - from: "2024-04-01"
        store: tsdb
        object_store: s3
        schema: v13
        index:
          prefix: loki_index_
          period: 24h
  pattern_ingester:
    enabled: true
  limits_config:
    allow_structured_metadata: true
    volume_enabled: true
  ruler:
    enable_api: true

ignoreMinioDeprecation: true  # Temporary workaround – MinIO will be removed 2026-10-31
minio:
  enabled: true
      
deploymentMode: Monolithic

singleBinary:
  replicas: 1

# Zero out replica counts of other deployment modes
backend:
  replicas: 0
read:
  replicas: 0
write:
  replicas: 0

ingester:
  replicas: 0
querier:
  replicas: 0
queryFrontend:
  replicas: 0
queryScheduler:
  replicas: 0
distributor:
  replicas: 0
compactor:
  replicas: 0
indexGateway:
  replicas: 0
bloomPlanner:
  replicas: 0
bloomBuilder:
  replicas: 0
bloomGateway:
  replicas: 0

This configuration uses the built-in MinIO subchart for convenience, which is deprecated and will be removed on 2026-10-31. For production deployments, configure an external object storage provider such as AWS S3, GCS, or Azure Blob Storage.

Multiple Replicas

Deploying the Helm chart with multiple replicas deploys the following components:

  • Loki (3 replicas)
  • Loki Canary (1 DaemonSet)
  • Loki Gateway (1 NGINX replica)
  • Chunks cache (1 StatefulSet)
  • Results cache (1 StatefulSet)
  • Minio (optional, deprecated — see warning below)

Create the configuration file values.yaml:

Note

If you set the singleBinary.replicas value to 2 or more, this chart configures Loki to run a single binary in a replicated, highly available mode. When running replicas of a single binary, you must configure object storage.

Warning

The built-in MinIO subchart is deprecated and will be removed on 2026-10-31. Setting minio.enabled=true without also setting ignoreMinioDeprecation: true causes chart rendering to fail with chart v17+. Use the workaround shown below only for temporary testing. For production, configure an external object storage backend instead.

YAML 
loki:
  commonConfig:
    replication_factor: 3
  schemaConfig:
    configs:
      - from: "2024-04-01"
        store: tsdb
        object_store: s3
        schema: v13
        index:
          prefix: loki_index_
          period: 24h
  pattern_ingester:
    enabled: true
  limits_config:
    allow_structured_metadata: true
    volume_enabled: true
  ruler:
    enable_api: true

ignoreMinioDeprecation: true  # Temporary workaround – MinIO will be removed 2026-10-31
minio:
  enabled: true
      
deploymentMode: Monolithic

singleBinary:
  replicas: 3

# Zero out replica counts of other deployment modes
backend:
  replicas: 0
read:
  replicas: 0
write:
  replicas: 0

ingester:
  replicas: 0
querier:
  replicas: 0
queryFrontend:
  replicas: 0
queryScheduler:
  replicas: 0
distributor:
  replicas: 0
compactor:
  replicas: 0
indexGateway:
  replicas: 0
bloomPlanner:
  replicas: 0
bloomBuilder:
  replicas: 0
bloomGateway:
  replicas: 0

In this configuration, update commonConfig.replication_factor and singleBinary.replicas to your desired number of replicas. This configuration uses the built-in MinIO subchart for convenience, which is deprecated and will be removed on 2026-10-31. For production deployments, configure an external object storage provider such as AWS S3, GCS, or Azure Blob Storage.

Deploying the Helm chart for development and testing

  1. Add the Grafana Community chart repository to Helm:

    Bash 
    helm repo add grafana-community https://grafana-community.github.io/helm-charts

  2. Update the chart repository:

    Bash 
    helm repo update

  3. Deploy Loki using the configuration file values.yaml:

    Bash 
     helm install loki grafana-community/loki -f values.yaml

  4. Install or upgrade the Loki deployment.

    • To install:

      Bash 
      helm install --values values.yaml loki grafana-community/loki

    • To upgrade:

      Bash 
      helm upgrade --values values.yaml loki grafana-community/loki

  5. Verify that Loki is running:

    Bash 
    kubectl get pods -n loki

Object Storage Configuration

After testing Loki with MinIO, we recommend configuring Loki with an object storage provider. The following examples shows how to configure Loki with different object storage providers:

Caution

When deploying Loki using S3 Storage DO NOT use the default bucket names; chunk, ruler and admin. Choose a unique name for each bucket. For more information see the following security update. This caution does not apply when you are using MinIO. When using MinIO we recommend using the default bucket names.

To configure other storage providers, refer to the Helm Chart Reference.

Deploying the Loki Helm chart to a Production Environment

Note

We are actively working on providing more guides for deploying Loki in production.

We recommend running Loki at scale within a cloud environment like AWS, Azure, or GCP. The below guides will show you how to deploy a minimally viable production environment.

Next Steps