--- title: "Install the simple scalable Helm chart | Grafana Loki documentation" description: "Installing Loki in simple scalable mode using the Helm chart." --- # Install the simple scalable 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-latest-setup-install-helm-install-scalable), which includes free forever access to 10k metrics, 50GB logs, 50GB traces, 500VUh k6 testing & more. This Helm Chart deploys Grafana Loki in [simple scalable mode](/docs/loki/latest/get-started/deployment-modes/#simple-scalable) 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. Simple Scalable Deployment (SSD) mode is being deprecated. The timeline for the deprecation is to be determined (TBD), but will happen before Loki 4.0 is released. > 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). This chart configures Loki to run `read`, `write`, and `backend` targets in a [scalable mode](/docs/loki/latest/get-started/deployment-modes/#simple-scalable). Loki’s simple scalable deployment mode separates execution paths into read, write, and backend targets. The default Helm chart deploys the following components: - Read component (3 replicas) - Write component (3 replicas) - Backend component (3 replicas) - Loki Canary (1 DaemonSet) - Gateway (1 NGINX replica) - Minio (optional, if `minio.enabled=true`) - Chunks cache (1 replica) - Results cache (1 replica) > Note > > We do not recommended running scalable mode with `filesystem` storage. For the purpose of this guide, we will use MinIO as the object storage to provide a complete example. ## Prerequisites - Helm 3 or above. See [Installing Helm](https://helm.sh/docs/intro/install/). - A running Kubernetes cluster (must have at least 3 nodes). ## Deploying the Helm chart for development and testing The following steps show how to deploy the Loki Helm chart in simple scalable mode using the included MinIO as the storage backend. Our recommendation is to start here for development and testing purposes. Then configure Loki with an object storage provider when moving to production. 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. Create the configuration file `values.yaml`. The example below illustrates how to deploy Loki in test mode using MinIO as storage: 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: s3 schema: v13 index: prefix: loki_index_ period: 24h ingester: chunk_encoding: snappy querier: # Default is 4, if you have enough memory and CPU you can increase, reduce if OOMing max_concurrent: 4 pattern_ingester: enabled: true limits_config: allow_structured_metadata: true volume_enabled: true deploymentMode: SimpleScalable backend: replicas: 2 read: replicas: 2 write: replicas: 3 # To ensure data durability with replication # Enable minio for storage minio: enabled: true gateway: service: type: LoadBalancer ``` 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 ``` ## 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: 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 querier: max_concurrent: 4 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 if you 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: {} deploymentMode: SimpleScalable backend: replicas: 3 read: replicas: 3 write: replicas: 3 # Disable minio storage minio: enabled: false ``` 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 tracing: enabled: true querier: max_concurrent: 4 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" deploymentMode: SimpleScalable backend: replicas: 3 read: replicas: 3 write: replicas: 3 # Disable minio storage minio: enabled: false ``` To configure other storage providers, refer to the [Helm Chart Reference](/docs/loki/latest/setup/install/helm/reference/). ## Next Steps - Configure an agent to [send log data to Loki](/docs/loki/latest/send-data/). - Monitor the Loki deployment using the [Meta Monitoring Helm chart](/docs/loki/latest/setup/install/helm/monitor-and-alert/)