--- title: "Install the monolithic Helm chart | Grafana Loki documentation" description: "Installing Loki in monolithic, single binary mode using the Helm chart." --- > For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt). # 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](/auth/sign-up/create-user?pg=docs-loki-next-setup-install-helm-install-monolithic), 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](/docs/loki/next/get-started/deployment-modes/#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](https://github.com/grafana-community/helm-charts). 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](https://github.com/grafana-community/helm-charts/blob/main/charts/loki/README.md#upgrading). > 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 - Helm 3 or above. See [Installing Helm](https://helm.sh/docs/intro/install/). - A running Kubernetes cluster. ## 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, if `minio.enabled=true`) 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. YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```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 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 ``` In this configuration, we are deploying Loki with MinIO as the object storage. We recommend configuring object storage via cloud provider or pointing Loki at a MinIO cluster for production deployments. ### 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, if `minio.enabled=true`) 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. YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```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 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, we need to make sure to update the `commonConfig.replication_factor` and `singleBinary.replicas` to the desired number of replicas. We are deploying Loki with MinIO as the object storage. We recommend configuring object storage via cloud provider or pointing Loki at a MinIO cluster for production deployments. ## Deploying the Helm chart for development and testing 1. Add the [Grafana Community chart repository](https://github.com/grafana-community/helm-charts) to Helm: Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash helm repo add grafana-community https://grafana-community.github.io/helm-charts ``` 2. Update the chart repository: Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash helm repo update ``` 3. Deploy Loki using the configuration file `values.yaml`: Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash helm install loki grafana-community/loki -f values.yaml ``` 4. Install or upgrade the Loki deployment. - To install: Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash helm install --values values.yaml loki grafana-community/loki ``` - To upgrade: Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```bash helm upgrade --values values.yaml loki grafana-community/loki ``` 5. Verify that Loki is running: Bash ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```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](/blog/2024/06/27/grafana-security-update-grafana-loki-and-unintended-data-write-attempts-to-amazon-s3-buckets/). This caution does not apply when you are using MinIO. When using MinIO we recommend using the default bucket names. S3 YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```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 storage_config: aws: region: bucketnames: s3forcepathstyle: false pattern_ingester: enabled: true limits_config: allow_structured_metadata: true volume_enabled: true retention_period: 672h # 28 days retention storage: type: s3 bucketNames: chunks: ruler: admin: s3: # s3 URL can be used to specify the endpoint, access key, secret key, and bucket name this works well for S3 compatible storages or are hosting Loki on-premises and want to use S3 as the storage backend. Either use the s3 URL or the individual fields below (AWS endpoint, region, secret). s3: s3://access_key:secret_access_key@custom_endpoint/bucket_name # AWS endpoint URL endpoint: # AWS region where the S3 bucket is located region: # AWS secret access key secretAccessKey: # AWS access key ID accessKeyId: # AWS signature version (e.g., v2 or v4) signatureVersion: # Forces the path style for S3 (true/false) s3ForcePathStyle: false # Allows insecure (HTTP) connections (true/false) insecure: false # HTTP configuration settings http_config: {} # Disable minio storage minio: enabled: false deploymentMode: Monolithic singleBinary: replicas: 3 persistence: storageClass: gp2 accessModes: - ReadWriteOnce size: 30Gi # 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 ``` Azure YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml loki: schemaConfig: configs: - from: "2024-04-01" store: tsdb object_store: azure schema: v13 index: prefix: loki_index_ period: 24h ingester: chunk_encoding: snappy storage: type: azure azure: # Name of the Azure Blob Storage account accountName: # Key associated with the Azure Blob Storage account accountKey: # Comprehensive connection string for Azure Blob Storage account (Can be used to replace endpoint, accountName, and accountKey) connectionString: # Flag indicating whether to use Azure Managed Identity for authentication useManagedIdentity: false # Flag indicating whether to use a federated token for authentication useFederatedToken: false # Client ID of the user-assigned managed identity (if applicable) userAssignedId: # Timeout duration for requests made to the Azure Blob Storage account (in seconds) requestTimeout: # Domain suffix of the Azure Blob Storage service endpoint (e.g., core.windows.net) endpointSuffix: bucketNames: chunks: "chunks" ruler: "ruler" admin: "admin" # Disable minio storage minio: enabled: false deploymentMode: Monolithic singleBinary: replicas: 3 persistence: storageClass: gp2 accessModes: - ReadWriteOnce size: 30Gi # 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 ``` To configure other storage providers, refer to the [Helm Chart Reference](/docs/loki/next/setup/install/helm/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. - [Deploy Loki on AWS](/docs/loki/next/setup/install/helm/deployment-guides/aws/) ## Next Steps - Configure an agent to [send log data to Loki](/docs/loki/next/send-data/). - Monitor the Loki deployment using the [Meta Monitoring Helm chart](/docs/loki/next/setup/install/helm/monitor-and-alert/)