mimir-distributed

# The default values specified in this file are enough to deploy all of the

# Grafana Mimir microservices but are not suitable for production load.

# To configure the resources for higher scale, refer to the small.yaml file.

# For production load with high availability, refer to the large.yaml values file.

# Note: The values in this file are not backward compatible. Copying and pasting the values is discouraged, but if you do so,

# make sure to use the values.yaml from the branch or tag that matches the mimir-distributed Helm chart version that you

# want to install. You also can see values.yaml for a specific version by running

# `helm show values grafana/mimir-distributed --version <version>`

# If you want to get the values file from Github, build the URL as follows because we git tag every release:

# `https://github.com/grafana/mimir/blob/mimir-distributed-<chart-version>/operations/helm/charts/mimir-distributed/values.yaml`.

# For example, https://github.com/grafana/mimir/blob/mimir-distributed-release-6.2/operations/helm/charts/mimir-distributed/values.yaml.

# -- Overrides the version used to determine compatibility of resources with the target Kubernetes cluster.

# This is useful when using `helm template`, because then helm will use the client version of kubectl as the Kubernetes version,

# which may or may not match your cluster's server version. Example: 'v1.24.4'. Set to null to use the version that helm

# devises.

kubeVersionOverride: null

# -- Overrides the chart's name. Used to change mimir/enterprise-metrics infix in the resource names. E.g. myRelease-mimir-ingester-1 to myRelease-nameOverride-ingester-1.

# This option is used to align resource names with Cortex, when doing a migration from Cortex to Grafana Mimir.

# Note: Grafana provided dashboards rely on the default naming and will need changes.

nameOverride: null

# -- Overrides the chart's computed fullname. Used to change the full prefix of resource names. E.g. myRelease-mimir-ingester-1 to fullnameOverride-ingester-1.

# Note: Grafana provided dashboards rely on the default naming and will need changes.

fullnameOverride: null

image:

# -- Grafana Mimir container image repository

repository: chainreg.biz/chainguard-private/grafana-mimir

# -- Grafana Mimir container image tag

# When set it takes precedence over what is defined as "appVersion" in Chart.yaml.

# tag: 3.2.0

# -- Container pull policy

pullPolicy: IfNotPresent

# -- Optionally specify an array of imagePullSecrets

# Secrets must be manually created in the namespace.

# ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/

# pullSecrets:

# - myRegistryKeySecretName

tag: 3.2.1-r0@sha256:ca3ae0dca04bc84ba01be3034df9312b3e065383f596b7bd01118c327accdfdb

global:

# -- Definitions to set up nginx resolver

dnsService: kube-dns

dnsNamespace: kube-system

clusterDomain: cluster.local.

dnsConfig: {}

# -- Common environment variables to add to all pods directly managed by this chart.

# scope: alertmanager, compactor, continuous-test, distributor, gateway, ingester, memcached, nginx, overrides-exporter, querier, query-frontend, query-scheduler, ruler, store-gateway, smoke-test

extraEnv: []

# -- Common source of environment injections to add to all pods directly managed by this chart.

# scope: alertmanager, compactor, continuous-test, distributor, gateway, ingester, memcached, nginx, overrides-exporter, querier, query-frontend, query-scheduler, ruler, store-gateway, smoke-test

# For example to inject values from a Secret, use:

# extraEnvFrom:

# - secretRef:

# name: mysecret

extraEnvFrom: []

# -- Common volumes to add to all pods directly managed by this chart.

# scope: alertmanager, compactor, continuous-test, distributor, gateway, ingester, memcached, nginx, overrides-exporter, querier, query-frontend, query-scheduler, ruler, store-gateway, smoke-test

extraVolumes: []

# -- Common mount points to add to all pods directly managed by this chart.

# scope: alertmanager, compactor, continuous-test, distributor, gateway, ingester, memcached, nginx, overrides-exporter, querier, query-frontend, query-scheduler, ruler, store-gateway, smoke-test

extraVolumeMounts: []

# -- Pod annotations for all pods directly managed by this chart. Usable for example to associate a version to 'global.extraEnv' and 'global.extraEnvFrom' and trigger a restart of the affected services.

# scope: alertmanager, compactor, distributor, gateway, ingester, memcached, nginx, overrides-exporter, querier, query-frontend, query-scheduler, ruler, store-gateway

podAnnotations: {}

# -- Pod labels for all pods directly managed by this chart.

# scope: alertmanager, compactor, distributor, gateway, ingester, memcached, nginx, overrides-exporter, querier, query-frontend, query-scheduler, ruler, store-gateway

podLabels: {}

serviceAccount:

# -- Whether to create a service account or not. In case 'create' is false, do set 'name' to an existing service account name.

create: true

# -- Override for the generated service account name.

name:

annotations: {}

labels: {}

# -- Configuration is loaded from the secret called 'externalConfigSecretName'. If 'useExternalConfig' is true, then the configuration is not generated, just consumed.

useExternalConfig: false

# -- Defines what kind of object stores the configuration, a ConfigMap or a Secret.

# In order to move sensitive information (such as credentials) from the ConfigMap/Secret to a more secure location (e.g. vault), it is possible to use [environment variables in the configuration](https://grafana.com/docs/mimir/latest/reference-configuration-parameters/#use-environment-variables-in-the-configuration).

# Such environment variables can be then stored in a separate Secret and injected via the global.extraEnvFrom value. For details about environment injection from a Secret please see [Secrets](https://kubernetes.io/docs/concepts/configuration/secret/#use-case-as-container-environment-variables).

configStorageType: ConfigMap

# -- Name of the Secret or ConfigMap that contains the configuration (used for naming even if config is internal).

externalConfigSecretName: '{{ include "mimir.resourceName" (dict "ctx" . "component" "config") }}'

# -- When 'useExternalConfig' is true, then changing 'externalConfigVersion' triggers restart of services - otherwise changes to the configuration cause a restart.

externalConfigVersion: "0"

# --Vault Agent config to mount secrets to TLS configurable components. This requires Vault and Vault Agent to already be running.

vaultAgent:

enabled: false

# -- Vault Kubernetes Authentication role

roleName: ""

# -- Path to client certificate in Vault

clientCertPath: ""

# -- Path to client key in Vault

clientKeyPath: ""

# -- Path to server certificate in Vault

serverCertPath: ""

# -- Path to server key in Vault

serverKeyPath: ""

# -- Path to client CA certificate in Vault

caCertPath: ""

mimir:

# -- Base config file for Grafana Mimir. Contains Helm templates that are evaulated at install/upgrade.

# To modify the resulting configuration, either copy and alter 'mimir.config' as a whole or use the 'mimir.structuredConfig' to add and modify certain YAML elements.

config: |

usage_stats:

installation_mode: helm

activity_tracker:

filepath: /active-query-tracker/activity.log

alertmanager:

data_dir: /data

enable_api: true

external_url: /alertmanager

{{- if .Values.alertmanager.zoneAwareReplication.enabled }}

sharding_ring:

zone_awareness_enabled: true

{{- end }}

{{- if .Values.alertmanager.fallbackConfig }}

fallback_config_file: /configs/alertmanager_fallback_config.yaml

{{- end }}

{{- if .Values.minio.enabled }}

alertmanager_storage:

backend: s3

s3:

access_key_id: {{ .Values.minio.rootUser }}

bucket_name: {{ include "mimir.minioBucketPrefix" . }}-ruler

endpoint: {{ template "minio.fullname" .Subcharts.minio }}.{{ .Release.Namespace }}.svc:{{ .Values.minio.service.port }}

insecure: true

secret_access_key: {{ .Values.minio.rootPassword }}

{{- end }}

# This configures how the store-gateway synchronizes blocks stored in the bucket. It uses Minio by default for getting started (configured via flags) but this should be changed for production deployments.

blocks_storage:

backend: s3

bucket_store:

{{- if index .Values "chunks-cache" "enabled" }}

chunks_cache:

backend: memcached

memcached:

addresses: {{ include "mimir.chunksCacheAddress" . }}

max_item_size: {{ mul (index .Values "chunks-cache").maxItemMemory 1024 1024 }}

timeout: 750ms

max_idle_connections: 150

{{- end }}

{{- if index .Values "index-cache" "enabled" }}

index_cache:

backend: memcached

memcached:

addresses: {{ include "mimir.indexCacheAddress" . }}

max_item_size: {{ mul (index .Values "index-cache").maxItemMemory 1024 1024 }}

timeout: 750ms

max_idle_connections: 150

{{- end }}

{{- if index .Values "metadata-cache" "enabled" }}

metadata_cache:

backend: memcached

memcached:

addresses: {{ include "mimir.metadataCacheAddress" . }}

max_item_size: {{ mul (index .Values "metadata-cache").maxItemMemory 1024 1024 }}

max_idle_connections: 150

{{- end }}

sync_dir: /data/tsdb-sync

{{- if .Values.minio.enabled }}

s3:

access_key_id: {{ .Values.minio.rootUser }}

bucket_name: {{ include "mimir.minioBucketPrefix" . }}-tsdb

endpoint: {{ template "minio.fullname" .Subcharts.minio }}.{{ .Release.Namespace }}.svc:{{ .Values.minio.service.port }}

insecure: true

secret_access_key: {{ .Values.minio.rootPassword }}

{{- end }}

tsdb:

dir: /data/tsdb

head_compaction_interval: 15m

wal_replay_concurrency: 3

compactor:

compaction_interval: 30m

deletion_delay: 2h

max_closing_blocks_concurrency: 2

max_opening_blocks_concurrency: 4

symbols_flushers_concurrency: 4

first_level_compaction_wait_period: 25m

data_dir: "/data"

sharding_ring:

wait_stability_min_duration: 1m

heartbeat_period: 1m

heartbeat_timeout: 4m

distributor:

# Increase the default remote write timeout (applied to writing to Kafka too) because writing

# to Kafka-compatible backend may be slower than writing directly to ingesters.

remote_timeout: 5s

ring:

heartbeat_period: 1m

heartbeat_timeout: 4m

frontend:

parallelize_shardable_queries: true

{{- if index .Values "results-cache" "enabled" }}

results_cache:

backend: memcached

memcached:

timeout: 500ms

addresses: {{ include "mimir.resultsCacheAddress" . }}

max_item_size: {{ mul (index .Values "results-cache").maxItemMemory 1024 1024 }}

cache_results: true

query_sharding_target_series_per_shard: 2500

{{- end }}

scheduler_address: {{ template "mimir.fullname" . }}-query-scheduler-headless.{{ .Release.Namespace }}.svc:{{ include "mimir.serverGrpcListenPort" . }}

frontend_worker:

grpc_client_config:

max_send_msg_size: 419430400 # 400MiB

scheduler_address: {{ template "mimir.fullname" . }}-query-scheduler-headless.{{ .Release.Namespace }}.svc:{{ include "mimir.serverGrpcListenPort" . }}

ingest_storage:

enabled: true

kafka:

{{- if .Values.kafka.enabled }}

# Address of Kafka broker to bootstrap the connection.

address: {{ template "mimir.fullname" . }}-kafka.{{ .Release.Namespace }}.svc.{{ $.Values.global.clusterDomain }}:{{ $.Values.kafka.service.port }}

{{- end }}

# Topic name.

topic: mimir-ingest

# Mimir will auto-create the topic on start up.

# The topic MUST be provisioned with no fewer partitions than the maximum number of ingester replicas. The value of 100 is for demo purposes.

auto_create_topic_enabled: true

auto_create_topic_default_partitions: 100

ingester:

# Disallow Push gRPC API; everything comes through Kafka in the ingest storage architecture.

push_grpc_method_enabled: false

ring:

final_sleep: 0s

num_tokens: 512

tokens_file_path: /data/tokens

unregister_on_shutdown: false

heartbeat_period: 2m

heartbeat_timeout: 10m

{{- if .Values.ingester.zoneAwareReplication.enabled }}

zone_awareness_enabled: true

{{- end }}

ingester_client:

grpc_client_config:

max_recv_msg_size: 104857600

max_send_msg_size: 104857600

limits:

# Limit queries to 500 days. You can override this on a per-tenant basis.

max_total_query_length: 12000h

# Adjust max query parallelism to 16x sharding, without sharding we can run 15d queries fully in parallel.

# With sharding we can further shard each day another 16 times. 15 days * 16 shards = 240 subqueries.

max_query_parallelism: 240

# Avoid caching results newer than 10m because some samples can be delayed

# This presents caching incomplete results

max_cache_freshness: 10m

memberlist:

abort_if_cluster_join_fails: false

compression_enabled: false

join_members:

- dns+{{ include "mimir.fullname" . }}-gossip-ring.{{ .Release.Namespace }}.svc.{{ .Values.global.clusterDomain }}:{{ include "mimir.memberlistBindPort" . }}

querier:

max_concurrent: 8

query_scheduler:

# Increase from default of 100 to account for queries created by query sharding

max_outstanding_requests_per_tenant: 800

ruler:

alertmanager_url: dnssrvnoa+http://_http-metrics._tcp.{{ template "mimir.fullname" . }}-alertmanager-headless.{{ .Release.Namespace }}.svc.{{ .Values.global.clusterDomain }}/alertmanager

enable_api: true

rule_path: /data

{{- if .Values.ruler.remoteEvaluationDedicatedQueryPath }}

query_frontend:

address: dns:///{{ template "mimir.fullname" . }}-ruler-query-frontend.{{ .Release.Namespace }}.svc:{{ include "mimir.serverGrpcListenPort" . }}

{{- end }}

{{- if or (.Values.minio.enabled) (index .Values "metadata-cache" "enabled") }}

ruler_storage:

{{- if .Values.minio.enabled }}

backend: s3

s3:

endpoint: {{ template "minio.fullname" .Subcharts.minio }}.{{ .Release.Namespace }}.svc:{{ .Values.minio.service.port }}

bucket_name: {{ include "mimir.minioBucketPrefix" . }}-ruler

access_key_id: {{ .Values.minio.rootUser }}

secret_access_key: {{ .Values.minio.rootPassword }}

insecure: true

{{- end }}

{{- if index .Values "metadata-cache" "enabled" }}

cache:

backend: memcached

memcached:

addresses: {{ include "mimir.metadataCacheAddress" . }}

max_item_size: {{ mul (index .Values "metadata-cache").maxItemMemory 1024 1024 }}

timeout: 500ms

{{- end }}

{{- end }}

runtime_config:

file: /var/{{ include "mimir.name" . }}/runtime.yaml

store_gateway:

sharding_ring:

heartbeat_period: 1m

heartbeat_timeout: 10m

wait_stability_min_duration: 1m

{{- if .Values.store_gateway.zoneAwareReplication.enabled }}

kvstore:

prefix: multi-zone/

{{- end }}

tokens_file_path: /data/tokens

unregister_on_shutdown: false

{{- if .Values.store_gateway.zoneAwareReplication.enabled }}

zone_awareness_enabled: true

{{- end }}

# -- Additional structured values on top of the text based 'mimir.config'. Applied after the text based config is evaluated for templates. Enables adding and modifying YAML elements in the evaulated 'mimir.config'.

#

# Additionally, consider the optional "insecure_skip_verify" key below, it allows you to skip_verify_false in case the s3_endpoint certificate is not trusted.

# For more information see https://grafana.com/docs/mimir/latest/references/configuration-parameters/

#

# Example:

#

# structuredConfig:

# common:

# storage:

# backend: s3

# s3:

# bucket_name: "${BUCKET_NAME}"

# endpoint: "${BUCKET_HOST}:${BUCKET_PORT}"

# access_key_id: "${AWS_ACCESS_KEY_ID}" # This is a secret injected via an environment variable

# secret_access_key: "${AWS_SECRET_ACCESS_KEY}" # This is a secret injected via an environment variable

# http:

# insecure_skip_verify: true

structuredConfig: {}

# -- runtimeConfig provides a reloadable runtime configuration. Changing the runtimeConfig doesn't require a restart of all components.

# For more infromation see https://grafana.com/docs/mimir/latest/configure/about-runtime-configuration/

#

# Example:

#

# runtimeConfig:

# ingester_limits: # limits that each ingester replica enforces

# max_ingestion_rate: 20000

# max_series: 1500000

# max_tenants: 1000

# max_inflight_push_requests: 30000

# distributor_limits: # limits that each distributor replica enforces

# max_ingestion_rate: 20000

# max_inflight_push_requests: 30000

# max_inflight_push_requests_bytes: 50000000

# overrides:

# tenant-1: # limits for tenant-1 that the whole cluster enforces

# ingestion_tenant_shard_size: 9

# max_global_series_per_user: 1500000

# max_fetched_series_per_query: 100000

runtimeConfig: {}

# RBAC configuration

rbac:

# -- If true, PodSecurityPolicy will be rendered by the chart on Kubernetes 1.24.

# By default the PodSecurityPolicy is not rendered on version 1.24.

create: true

# -- PSP configuration

podSecurityPolicy:

seccompProfile: runtime/default

privileged: false

allowPrivilegeEscalation: false

hostNetwork: false

hostIPC: false

hostPID: false

readOnlyRootFilesystem: true

runAsUser:

rule: "MustRunAsNonRoot"

seLinux:

rule: "RunAsAny"

supplementalGroups:

rule: "MustRunAs"

ranges:

- min: 1

max: 65535

fsGroup:

rule: "MustRunAs"

ranges:

- min: 1

max: 65535

additionalVolumes: []

forcePSPOnKubernetes124: false

# -- For GKE/EKS/AKS use 'type: psp'. For OpenShift use 'type: scc'

type: psp

# -- podSecurityContext is the default pod security context for Mimir, gateway, and cache components.

# When installing on OpenShift, override podSecurityContext settings with

#

# rbac:

# podSecurityContext:

# fsGroup: null

# runAsGroup: null

# runAsUser: null

podSecurityContext:

fsGroup: 10001

runAsGroup: 10001

runAsNonRoot: true

runAsUser: 10001

seccompProfile:

type: RuntimeDefault

# -- KEDA Autoscaling configuration

kedaAutoscaling:

# -- A Prometheus-compatible URL. Cadvisor and Mimir metrics for the Mimir pods are expected in this server.

# For more information on the required metrics see [Monitor system health](https://grafana.com/docs/helm-charts/mimir-distributed/latest/run-production-environment-with-helm/monitor-system-health/).

# If empty, the helm chart uses the metamonitoring URL from metaMonitoring.grafanaAgent.metrics.remote.url.

# If that is empty, then the Mimir cluster is used.

prometheusAddress: ""

customHeaders: {}

pollingInterval: 10

ignoreNullValues: true

unsafeSsl: false

# If your metrics are stored in a datasource with multiple mimir instances extra labels to filter the data are required to get the right metric.

toPromQLLabelSelector:

# - cluster!="eu-west"

# - app="foobar"

# -- KEDA fallback configuration. This section specifies fallback options when the scaler fails to get metrics from the source.

# For more information, refer to the [KEDA ScaledObject specification](https://keda.sh/docs/2.18/reference/scaledobject-spec/).

fallback:

# -- Enable fallback behavior when the scaler fails to get metrics.

enabled: false

# failureThreshold: 3 # Number of consecutive failures before activating fallback behavior

# replicas: 6 # Number of replicas to scale to when fallback is triggered

# behavior: "static" # Fallback behavior type. Options: "static", "currentReplicas", "currentReplicasIfHigher", "currentReplicasIfLower"

# # static: Use the fallback.replicas value

# # currentReplicas: Use the current replica count

# # currentReplicasIfHigher: Use current replicas if higher than fallback.replicas, otherwise use fallback.replicas

# # currentReplicasIfLower: Use current replicas if lower than fallback.replicas, otherwise use fallback.replicas

# --KEDA trigger authentication settings.

# ref: https://keda.sh/docs/2.16/scalers/pulsar/#authentication-parameters

authentication:

enabled: false

authModes: ""

secretTargetRef: []

# - key: username

# name: my-secret-name

# parameter: username

# - key: password

# name: my-secret-name

# parameter: password

alertmanager:

enabled: true

# -- Total number of replicas for the alertmanager across all availability zones

# If alertmanager.zoneAwareReplication.enabled=false, this number is taken as is.

# Otherwise each zone starts `ceil(replicas / number_of_zones)` number of pods.

# E.g. if 'replicas' is set to 4 and there are 3 zones, then 4/3=1.33 and after rounding up it means 2 pods per zone are started.

replicas: 1

revisionHistoryLimit: null

# -- Allows to override the container image of the alertmanager component.

# When set it takes precedence over what is defined in global "image".

image:

# repository: grafana/mimir

# tag: 3.2.0

statefulSet:

enabled: true

# -- Dedicated service account for alertmanager pods.

# If not set, the default service account defined at the begining of this file will be used.

# This service account can be used even if the default one is not set.

serviceAccount:

create: false

# -- Alertmanager specific service account name. If not set and create is set to true, the default

# name will be the default mimir service account's name with the "-alertmanager" suffix.

name: ""

annotations: {}

labels: {}

service:

annotations: {}

labels: {}

# -- https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/

internalTrafficPolicy: Cluster

type: ClusterIP

extraPorts: []

# - port: 11811

# protocol: TCP

# name: reverse-proxy

# targetPort: 11811

# -- Optionally set the scheduler for pods of the alertmanager

schedulerName: ""

resources:

requests:

cpu: 10m

memory: 32Mi

# -- Fallback config for alertmanager.

# When a tenant doesn't have an Alertmanager configuration, the Grafana Mimir Alertmanager uses the fallback configuration.

fallbackConfig: |

receivers:

- name: default-receiver

route:

receiver: default-receiver

extraArgs: {}

# Pod Labels

podLabels: {}

# Pod Annotations

podAnnotations: {}

# -- Pod Disruption Budget for alertmanager, this will be applied across availability zones to prevent losing redundancy

podDisruptionBudget:

maxUnavailable: 1

# -- The name of the PriorityClass for alertmanager pods

priorityClassName: null

dnsConfig: {}

# -- NodeSelector to pin alertmanager pods to certain set of nodes. This is ignored when alertmanager.zoneAwareReplication.enabled=true.

nodeSelector: {}

# -- Pod affinity settings for the alertmanager. This is ignored when alertmanager.zoneAwareReplication.enabled=true.

affinity: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints:

maxSkew: 1

topologyKey: kubernetes.io/hostname

whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

annotations: {}

persistence:

# SubPath in emptyDir for persistence, only enabled if alertmanager.statefulSet.enabled is false

subPath:

persistentVolume:

# If true and alertmanager.statefulSet.enabled is true,

# Alertmanager will create/use a Persistent Volume Claim

# If false, use emptyDir

enabled: true

# Alertmanager data Persistent Volume Claim template name

#

name: storage

# Alertmanager data Persistent Volume Claim annotations

#

annotations: {}

# Alertmanager data Persistent Volume Claim labels

#

labels: {}

# Alertmanager data Persistent Volume access modes

# Must match those of existing PV or dynamic provisioner

# Ref: http://kubernetes.io/docs/user-guide/persistent-volumes/

#

accessModes:

- ReadWriteOnce

# Alertmanager data Persistent Volume size

#

size: 1Gi

# Subdirectory of Alertmanager data Persistent Volume to mount

# Useful if the volume's root directory is not empty

#

subPath: ""

# Alertmanager data Persistent Volume Storage Class

# If defined, storageClassName: <storageClass>

# If set to "-", storageClassName: "", which disables dynamic provisioning

# If undefined (the default) or set to null, no storageClassName spec is

# set, choosing the default provisioner.

#

# A per-zone storageClass configuration in `alertmanager.zoneAwareReplication.zones[*].storageClass` takes precedence over this field.

# storageClass: "-"

# Alertmanager data Persistent Volume Attributes Class

# Allows you to dynamically modify a volume's attributes on the fly

# Requires Kubernetes 1.31+ and a CSI driver with ModifyVolume support.

# Must reference an existing cluster VolumeAttributesClass.

# A per-zone volumeAttributesClassName in `alertmanager.zoneAwareReplication.zones[*].volumeAttributesClassName` takes precedence over this field when set.

# volumeAttributesClassName: my-cluster-vac

# -- Enable StatefulSetAutoDeletePVC feature

# https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#persistentvolumeclaim-retention

enableRetentionPolicy: false

whenDeleted: Retain

whenScaled: Retain

readinessProbe:

httpGet:

path: /ready

port: http-metrics

initialDelaySeconds: 45

# -- SecurityContext override for alermeneger pods

securityContext: {}

# -- The SecurityContext for alertmanager containers

containerSecurityContext:

allowPrivilegeEscalation: false

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

# Tolerations for pod assignment

# ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/

tolerations: []

strategy:

type: RollingUpdate

rollingUpdate:

maxSurge: 0

maxUnavailable: 1

# -- updateStrategy of the alertmanager statefulset. This is ignored when alertmanager.zoneAwareReplication.enabled=true.

statefulStrategy:

type: RollingUpdate

terminationGracePeriodSeconds: 900

initContainers: []

# Init containers to be added to the alertmanager pod.

# - name: my-init-container

# image: busybox:latest

# command: ['sh', '-c', 'echo hello']

extraContainers: []

# Additional containers to be added to the alertmanager pod.

# - name: reverse-proxy

# image: angelbarrera92/basic-auth-reverse-proxy:dev

# args:

# - "serve"

# - "--upstream=http://localhost:3100"

# - "--auth-config=/etc/reverse-proxy-conf/authn.yaml"

# ports:

# - name: http

# containerPort: 11811

# protocol: TCP

# volumeMounts:

# - name: reverse-proxy-auth-config

# mountPath: /etc/reverse-proxy-conf

extraVolumes: []

# Additional volumes to the alertmanager pod.

# - name: reverse-proxy-auth-config

# secret:

# secretName: reverse-proxy-auth-config

# Extra volume mounts that will be added to the alertmanager container

extraVolumeMounts: []

# Extra env variables to pass to the alertmanager container

env: []

extraEnvFrom: []

# -- Options to configure zone-aware replication for alertmanager

# Example configuration with full geographical redundancy:

# rollout_operator:

# enabled: true

# alertmanager:

# zoneAwareReplication:

# enabled: true

# topologyKey: 'kubernetes.io/hostname' # This generates default anti-affinity rules

# zones: # Zone list has to be fully redefined for modification. Update with you actual zones or skip to use logical zones only.

# - name: zone-a

# nodeSelector:

# topology.kubernetes.io/zone: us-central1-a

# - name: zone-b

# nodeSelector:

# topology.kubernetes.io/zone: us-central1-b

# - name: zone-c

# nodeSelector:

# topology.kubernetes.io/zone: us-central1-c

#

zoneAwareReplication:

# -- Enable zone-aware replication for alertmanager

enabled: false

# -- Maximum number of alertmanagers that can be unavailable per zone during rollout

maxUnavailable: 2

# -- topologyKey to use in pod anti-affinity. If unset, no anti-affinity rules are generated. If set, the generated anti-affinity rule makes sure that pods from different zones do not mix.

# E.g.: topologyKey: 'kubernetes.io/hostname'

topologyKey: null

# -- Auxiliary values for migration, see https://grafana.com/docs/helm-charts/mimir-distributed/latest/migration-guides/migrate-from-single-zone-with-helm/

migration:

# -- Indicate if migration is ongoing for multi zone alertmanager

enabled: false

# -- Start zone-aware alertmanagers

writePath: false

# -- Zone definitions for alertmanager zones. Note: you have to redefine the whole list to change parts as YAML does not allow to modify parts of a list.

zones:

# -- Name of the zone, used in labels and selectors. Must follow Kubernetes naming restrictions: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/

- name: zone-a

# -- nodeselector to restrict where pods of this zone can be placed. E.g.:

# nodeSelector:

# topology.kubernetes.io/zone: zone-a

nodeSelector: null

# -- extraAffinity adds user defined custom affinity rules (merged with generated rules)

extraAffinity: {}

# -- Alertmanager data Persistent Volume Storage Class

# If defined, storageClassName: <storageClass>

# If set to "-", then use `storageClassName: ""`, which disables dynamic provisioning

# If undefined or set to null (the default), then fall back to the value of `alertmanager.persistentVolume.storageClass`.

storageClass: null

# -- Persistent Volume VolumeAttributesClass for this zone.

# If undefined or set to null (the default), then fall back to the component `persistentVolume.volumeAttributesClassName`.

volumeAttributesClassName: null

# -- noDownscale adds a label that can be used by the rollout-operator as documented in the rollout-operator repo: https://github.com/grafana/rollout-operator#webhooks

noDownscale: false

# -- downscaleLeader is an Annotation used by the rollout-operator to coordinate downscaling across zones.

# Set to the StatefulSet name that should lead downscaling for this component (typically the previous zone).

# Example: "mimir-alertmanager-zone-a" for zone-b, "mimir-alertmanager-zone-b" for zone-c.

# If undefined or set to null (the default), this zone won't be designated as a downscale leader.

downscaleLeader: null

# -- Name of the zone, used in labels and selectors. Must follow Kubernetes naming restrictions: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/

- name: zone-b

# -- nodeselector to restrict where pods of this zone can be placed. E.g.:

# nodeSelector:

# topology.kubernetes.io/zone: zone-b

nodeSelector: null

# -- extraAffinity adds user defined custom affinity rules (merged with generated rules)

extraAffinity: {}

# -- Alertmanager data Persistent Volume Storage Class

# If defined, storageClassName: <storageClass>

# If set to "-", then use `storageClassName: ""`, which disables dynamic provisioning

# If undefined or set to null (the default), then fall back to the value of `alertmanager.persistentVolume.storageClass`.

storageClass: null

# -- Persistent Volume VolumeAttributesClass for this zone.

# If undefined or set to null (the default), then fall back to the component `persistentVolume.volumeAttributesClassName`.

volumeAttributesClassName: null

# -- noDownscale adds a label that can be used by the rollout-operator as documented in the rollout-operator repo: https://github.com/grafana/rollout-operator#webhooks

noDownscale: false

# -- downscaleLeader is an Annotation used by the rollout-operator to coordinate downscaling across zones.

# Set to the StatefulSet name that should lead downscaling for this component (typically the previous zone).

# Example: "mimir-alertmanager-zone-a" for zone-b, "mimir-alertmanager-zone-b" for zone-c.

# If undefined or set to null (the default), this zone won't be designated as a downscale leader.

downscaleLeader: null

# -- Name of the zone, used in labels and selectors. Must follow Kubernetes naming restrictions: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/

- name: zone-c

# -- nodeselector to restrict where pods of this zone can be placed. E.g.:

# nodeSelector:

# topology.kubernetes.io/zone: zone-c

nodeSelector: null

# -- extraAffinity adds user defined custom affinity rules (merged with generated rules)

extraAffinity: {}

# -- Alertmanager data Persistent Volume Storage Class

# If defined, storageClassName: <storageClass>

# If set to "-", then use `storageClassName: ""`, which disables dynamic provisioning

# If undefined or set to null (the default), then fall back to the value of `alertmanager.persistentVolume.storageClass`.

storageClass: null

# -- Persistent Volume VolumeAttributesClass for this zone.

# If undefined or set to null (the default), then fall back to the component `persistentVolume.volumeAttributesClassName`.

volumeAttributesClassName: null

# -- noDownscale adds a label that can be used by the rollout-operator as documented in the rollout-operator repo: https://github.com/grafana/rollout-operator#webhooks

noDownscale: false

# -- downscaleLeader is an Annotation used by the rollout-operator to coordinate downscaling across zones.

# Set to the StatefulSet name that should lead downscaling for this component (typically the previous zone).

# Example: "mimir-alertmanager-zone-a" for zone-b, "mimir-alertmanager-zone-b" for zone-c.

# If undefined or set to null (the default), this zone won't be designated as a downscale leader.

downscaleLeader: null

distributor:

# -- Whether to render the manifests related to the distributor component.

enabled: true

# -- Allows to override the container image of the distributor component.

# When set it takes precedence over what is defined in global "image".

image:

# repository: grafana/mimir

# tag: 3.2.0

# Setting it to null will produce a deployment without replicas set, allowing you to use autoscaling with the deployment

replicas: 1

revisionHistoryLimit: null

# -- [Experimental] Configure autoscaling via KEDA (https://keda.sh). This requires having

# KEDA already installed in the Kubernetes cluster. The metrics for scaling are read

# according to top-level kedaAutoscaling.prometheusAddress (defaulting to metamonitoring remote-write destination).

# Basic auth and extra HTTP headers from metaMonitoring are ignored, please use customHeaders.

# The remote URL is used even if metamonitoring is disabled.

# For more details about migrating to autoscaling, refer to https://grafana.com/docs/helm-charts/mimir-distributed/latest/configure/configure-autoscaling/#migrate-existing-deployments

kedaAutoscaling:

enabled: false

# -- preserveReplicas gives you the option to migrate from non-autoscaled to autoscaled deployments without losing replicas. When set to true, the replica fields in the component will be left intact.

# For more details about migrating to autoscaling, refer to https://grafana.com/docs/helm-charts/mimir-distributed/latest/configure/configure-autoscaling/#migrate-existing-deployments

preserveReplicas: false

minReplicaCount: 1

maxReplicaCount: 10

# -- Target CPU utilization percentage for KEDA autoscaling. This controls the headroom each pod has compared to its current usage.

# targetting lower percentages overprovisions the containers, so they can handle bursts of traffic and tolerate failures without waiting to scale out.

targetCPUUtilizationPercentage: 100

# -- Target memory utilization percentage for KEDA autoscaling. This controls the headroom each pod has compared to its current usage.

# targetting lower percentages overprovisions the containers, so they can handle bursts of traffic and tolerate failures without waiting to scale out.

targetMemoryUtilizationPercentage: 100

behavior:

scaleDown:

policies:

- periodSeconds: 600

type: Percent

value: 10

# -- Fallback configuration for this component. If not set (null), the global kedaAutoscaling.fallback configuration is used.

# fallback: {}

service:

annotations: {}

labels: {}

# -- https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/

internalTrafficPolicy: Cluster

type: ClusterIP

extraPorts: []

# -- https://kubernetes.io/docs/concepts/services-networking/service/#traffic-distribution

trafficDistribution: ""

resources:

requests:

cpu: 100m

memory: 512Mi

# Additional distributor container arguments, e.g. log level (debug, info, warn, error)

extraArgs: {}

# Pod Labels

podLabels: {}

# Pod Annotations

podAnnotations: {}

# Pod Disruption Budget

podDisruptionBudget:

maxUnavailable: 1

# -- The name of the PriorityClass for distributor pods

priorityClassName: null

dnsConfig: {}

nodeSelector: {}

affinity: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints:

maxSkew: 1

topologyKey: kubernetes.io/hostname

whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

annotations: {}

persistence:

subPath:

readinessProbe:

httpGet:

path: /ready

port: http-metrics

initialDelaySeconds: 45

# -- SecurityContext override for distributor pods

securityContext: {}

# -- The SecurityContext for distributor containers

containerSecurityContext:

allowPrivilegeEscalation: false

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

strategy:

type: RollingUpdate

rollingUpdate:

maxUnavailable: 0

maxSurge: 15%

# Keep the termination grace period higher than the -shutdown-delay configured on the distributor.

terminationGracePeriodSeconds: 100

tolerations: []

initContainers: []

extraContainers: []

extraVolumes: []

extraVolumeMounts: []

env: []

extraEnvFrom: []

ingester:

# -- Whether to render the manifests related to the ingester component.

enabled: true

# -- Allows to override the container image of the ingester component.

# When set it takes precedence over what is defined in global "image".

image:

# repository: grafana/mimir

# tag: 3.2.0

# -- Total number of replicas for the ingester across all availability zones

# If ingester.zoneAwareReplication.enabled=false, this number is taken as is.

# Otherwise each zone starts `ceil(replicas / number_of_zones)` number of pods.

# E.g. if 'replicas' is set to 4 and there are 3 zones, then 4/3=1.33 and after rounding up it means 2 pods per zone are started.

replicas: 3

revisionHistoryLimit: null

statefulSet:

enabled: true

service:

annotations: {}

labels: {}

# -- https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/

internalTrafficPolicy: Cluster

type: ClusterIP

extraPorts: []

# -- https://kubernetes.io/docs/concepts/services-networking/service/#traffic-distribution

# Note: This service is only used for admin endpoints like TSDB statistics, not for write or read path traffic.

trafficDistribution: ""

# -- Optionally set the scheduler for pods of the ingester

schedulerName: ""

resources:

requests:

cpu: 100m

memory: 512Mi

# Additional ingester container arguments, e.g. log level (debug, info, warn, error)

extraArgs: {}

# Pod Labels

podLabels: {}

# Pod Annotations

podAnnotations: {}

# -- The name of the PriorityClass for ingester pods

priorityClassName: null

# -- Pod Disruption Budget for ingester, this will be applied across availability zones to prevent losing redundancy

podDisruptionBudget:

maxUnavailable: 1

podManagementPolicy: Parallel

# -- NodeSelector to pin ingester pods to certain set of nodes. This is ignored when ingester.zoneAwareReplication.enabled=true.

nodeSelector: {}

# -- Pod affinity settings for the ingester. This is ignored when ingester.zoneAwareReplication.enabled=true.

affinity: {}

dnsConfig: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

# It is recommended to replace this with requiredDuringSchedulingIgnoredDuringExecution podAntiAffinity rules when

# deploying to production.

topologySpreadConstraints:

maxSkew: 1

topologyKey: kubernetes.io/hostname

whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

annotations: {}

persistentVolume:

# If true and ingester.statefulSet.enabled is true,

# Ingester will create/use a Persistent Volume Claim

# If false, use emptyDir

# It is advisable to enable volume persistence in ingester to avoid losing metrics.

#

enabled: true

# Ingester data Persistent Volume Claim template name

#

name: storage

# Ingester data Persistent Volume Claim annotations

#

annotations: {}

# Ingester data Persistent Volume Claim labels

#

labels: {}

# Ingester data Persistent Volume access modes

# Must match those of existing PV or dynamic provisioner

# Ref: http://kubernetes.io/docs/user-guide/persistent-volumes/

accessModes:

- ReadWriteOnce

# Ingester data Persistent Volume size

size: 2Gi

# Subdirectory of Ingester data Persistent Volume to mount

# Useful if the volume's root directory is not empty

subPath: ""

# -- Enable StatefulSetAutoDeletePVC feature

# https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#persistentvolumeclaim-retention

enableRetentionPolicy: false

whenDeleted: Retain

whenScaled: Retain

# Ingester data Persistent Volume Storage Class

# If defined, storageClassName: <storageClass>

# If set to "-", storageClassName: "", which disables dynamic provisioning

# If undefined (the default) or set to null, no storageClassName spec is

# set, choosing the default provisioner.

#

# A per-zone storageClass configuration in `ingester.zoneAwareReplication.zones[*].storageClass` takes precedence over this field.

#

# storageClass: "-"

# Ingester data Persistent Volume Attributes Class

# Allows you to dynamically modify a volume's attributes on the fly

# Requires Kubernetes 1.31+ and a CSI driver with ModifyVolume support.

# Must reference an existing cluster VolumeAttributesClass.

# A per-zone volumeAttributesClassName in `ingester.zoneAwareReplication.zones[*].volumeAttributesClassName` takes precedence over this field when set.

# volumeAttributesClassName: my-cluster-vac

livenessProbe: null

readinessProbe:

httpGet:

path: /ready

port: http-metrics

initialDelaySeconds: 60

# -- SecurityContext override for ingester pods

securityContext: {}

# -- The SecurityContext for ingester containers

containerSecurityContext:

allowPrivilegeEscalation: false

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

# -- updateStrategy of the ingester statefulset. This is ignored when ingester.zoneAwareReplication.enabled=true.

statefulStrategy:

type: RollingUpdate

terminationGracePeriodSeconds: 1200

tolerations: []

initContainers: []

extraContainers: []

extraVolumes: []

extraVolumeMounts: []

env: []

extraEnvFrom: []

# -- Options to configure zone-aware replication for ingester

# Example configuration with full geographical redundancy:

# rollout_operator:

# enabled: true

# ingester:

# zoneAwareReplication:

# enabled: true

# topologyKey: 'kubernetes.io/hostname' # This generates default anti-affinity rules

# zones: # Zone list has to be fully redefined for modification. Update with you actual zones or skip to use logical zones only.

# - name: zone-a

# nodeSelector:

# topology.kubernetes.io/zone: us-central1-a

# storageClass: storage-class-us-central1-a

# - name: zone-b

# nodeSelector:

# topology.kubernetes.io/zone: us-central1-b

# storageClass: storage-class-us-central1-b

# - name: zone-c

# nodeSelector:

# topology.kubernetes.io/zone: us-central1-c

# storageClass: storage-class-us-central1-c

#

zoneAwareReplication:

# -- Enable zone-aware replication for ingester

enabled: true

# -- Maximum number of ingesters that can be unavailable per zone during rollout

maxUnavailable: 50

# -- Minimum time for the rollout operator to wait between ingester zone down scales

minTimeBetweenZonesDownscale: 12h

# -- topologyKey to use in pod anti-affinity. If unset, no anti-affinity rules are generated. If set, the generated anti-affinity rule makes sure that pods from different zones do not mix.

# E.g.: topologyKey: 'kubernetes.io/hostname'

topologyKey: null

# -- When true and zone-aware replication is enabled, automatically set the

# -ingest-storage.kafka.client-rack flag on each ingester zone to its zone name.

# This enables Kafka rack-aware consumption so that ingesters prefer reading

# from Kafka replicas in the same availability zone, reducing cross-AZ traffic.

# Set to false if you want to manage client-rack manually via extraArgs.

autoIngestStorageClientRack: true

# -- Auxiliary values for migration, see https://grafana.com/docs/helm-charts/mimir-distributed/latest/migration-guides/migrate-from-single-zone-with-helm/

migration:

# -- Indicate if migration is ongoing for multi zone ingester

enabled: false

# -- Exclude default zone on write path

excludeDefaultZone: false

# -- Enable zone-awareness, read path only

readPath: false

# -- Total number of replicas to start in availability zones when migration is enabled

replicas: 0

# -- Scale default zone ingesters to 0

scaleDownDefaultZone: false

# -- Enable zone-awareness, write path only

writePath: false

# -- Zone definitions for ingester zones. Note: you have to redefine the whole list to change parts as YAML does not allow to modify parts of a list.

# When ingest storage is enabled, 2 zones are sufficient since Kafka handles replication. 3 zones are required for classic (non-ingest-storage) architecture.

zones:

# -- Name of the zone, used in labels and selectors. Must follow Kubernetes naming restrictions: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/

- name: zone-a

# -- nodeselector to restrict where pods of this zone can be placed. E.g.:

# nodeSelector:

# topology.kubernetes.io/zone: zone-a

nodeSelector: null

# -- extraAffinity adds user defined custom affinity rules (merged with generated rules)

extraAffinity: {}

# -- Ingester data Persistent Volume Storage Class

# If defined, storageClassName: <storageClass>

# If set to "-", then use `storageClassName: ""`, which disables dynamic provisioning

# If undefined or set to null (the default), then fall back to the value of `ingester.persistentVolume.storageClass`.

storageClass: null

# -- Persistent Volume VolumeAttributesClass for this zone.

# If undefined or set to null (the default), then fall back to the component `persistentVolume.volumeAttributesClassName`.

volumeAttributesClassName: null

# -- noDownscale adds a label that can be used by the rollout-operator as documented in the rollout-operator repo: https://github.com/grafana/rollout-operator#webhooks

noDownscale: false

# -- downscaleLeader is an Annotation used by the rollout-operator to coordinate downscaling across zones.

# Set to the StatefulSet name that should lead downscaling for this component (typically the previous zone).

# Example: "mimir-ingester-zone-a" for zone-b, "mimir-ingester-zone-b" for zone-c.

# If undefined or set to null (the default), this zone won't be designated as a downscale leader.

downscaleLeader: null

# -- prepareDownscale adds labels and annotations for the rollout-operator to prepare downscaling: https://github.com/grafana/rollout-operator#how-scaling-up-and-down-works

prepareDownscale: true

# -- Name of the zone, used in labels and selectors. Must follow Kubernetes naming restrictions: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/

- name: zone-b

# -- nodeselector to restrict where pods of this zone can be placed. E.g.:

# nodeSelector:

# topology.kubernetes.io/zone: zone-b

nodeSelector: null

# -- extraAffinity adds user defined custom affinity rules (merged with generated rules)

extraAffinity: {}

# -- Ingester data Persistent Volume Storage Class

# If defined, storageClassName: <storageClass>

# If set to "-", then use `storageClassName: ""`, which disables dynamic provisioning

# If undefined or set to null (the default), then fall back to the value of `ingester.persistentVolume.storageClass`.

storageClass: null

# -- Persistent Volume VolumeAttributesClass for this zone.

# If undefined or set to null (the default), then fall back to the component `persistentVolume.volumeAttributesClassName`.

volumeAttributesClassName: null

# -- noDownscale adds a label that can be used by the rollout-operator as documented in the rollout-operator repo: https://github.com/grafana/rollout-operator#webhooks

noDownscale: false

# -- downscaleLeader is an Annotation used by the rollout-operator to coordinate downscaling across zones.

# Set to the StatefulSet name that should lead downscaling for this component (typically the previous zone).

# Example: "mimir-ingester-zone-a" for zone-b, "mimir-ingester-zone-b" for zone-c.

# If undefined or set to null (the default), this zone won't be designated as a downscale leader.

downscaleLeader: null

# -- prepareDownscale adds labels and annotations for the rollout-operator to prepare downscaling: https://github.com/grafana/rollout-operator#how-scaling-up-and-down-works

prepareDownscale: true

# -- Name of the zone, used in labels and selectors. Must follow Kubernetes naming restrictions: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/

- name: zone-c

# -- nodeselector to restrict where pods of this zone can be placed. E.g.:

# nodeSelector:

# topology.kubernetes.io/zone: zone-c

nodeSelector: null

# -- extraAffinity adds user defined custom affinity rules (merged with generated rules)

extraAffinity: {}

# -- Ingester data Persistent Volume Storage Class

# If defined, storageClassName: <storageClass>

# If set to "-", then use `storageClassName: ""`, which disables dynamic provisioning

# If undefined or set to null (the default), then fall back to the value of `ingester.persistentVolume.storageClass`.

storageClass: null

# -- Persistent Volume VolumeAttributesClass for this zone.

# If undefined or set to null (the default), then fall back to the component `persistentVolume.volumeAttributesClassName`.

volumeAttributesClassName: null

# -- noDownscale adds a label that can be used by the rollout-operator as documented in the rollout-operator repo: https://github.com/grafana/rollout-operator#webhooks

noDownscale: false

# -- downscaleLeader is an Annotation used by the rollout-operator to coordinate downscaling across zones.

# Set to the StatefulSet name that should lead downscaling for this component (typically the previous zone).

# Example: "mimir-ingester-zone-a" for zone-b, "mimir-ingester-zone-b" for zone-c.

# If undefined or set to null (the default), this zone won't be designated as a downscale leader.

downscaleLeader: null

# -- prepareDownscale adds labels and annotations for the rollout-operator to prepare downscaling: https://github.com/grafana/rollout-operator#how-scaling-up-and-down-works

prepareDownscale: true

overrides_exporter:

enabled: true

# -- Allows to override the container image of the overrides-exporter component.

# When set it takes precedence over what is defined in global "image".

image:

# repository: grafana/mimir

# tag: 3.2.0

replicas: 1

revisionHistoryLimit: null

annotations: {}

initContainers: []

service:

annotations: {}

labels: {}

# -- https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/

internalTrafficPolicy: Cluster

type: ClusterIP

extraPorts: []

strategy:

type: RollingUpdate

rollingUpdate:

maxUnavailable: 0

maxSurge: 15%

podLabels: {}

podAnnotations: {}

# Pod Disruption Budget

podDisruptionBudget:

maxUnavailable: 1

# -- The name of the PriorityClass for overrides-exporter pods

priorityClassName: null

dnsConfig: {}

nodeSelector: {}

affinity: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints: {}

# maxSkew: 1

# topologyKey: kubernetes.io/hostname

# whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

# -- SecurityContext override for overrides-exporter pods

securityContext: {}

# -- The SecurityContext for overrides-exporter containers

containerSecurityContext:

allowPrivilegeEscalation: false

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

extraArgs: {}

persistence:

subPath:

livenessProbe:

httpGet:

path: /ready

port: http-metrics

initialDelaySeconds: 45

readinessProbe:

httpGet:

path: /ready

port: http-metrics

initialDelaySeconds: 45

resources:

requests:

cpu: 100m

memory: 128Mi

terminationGracePeriodSeconds: 30

tolerations: []

extraContainers: []

extraVolumes: []

extraVolumeMounts: []

env: []

extraEnvFrom: []

ruler:

enabled: true

# -- Allows to override the container image of the ruler component.

# When set it takes precedence over what is defined in global "image".

image:

# repository: grafana/mimir

# tag: 3.2.0

replicas: 1

revisionHistoryLimit: null

# -- [Experimental] Configure autoscaling via KEDA (https://keda.sh). This requires having

# KEDA already installed in the Kubernetes cluster. The metrics for scaling are read

# according to top-level kedaAutoscaling.prometheusAddress (defaulting to metamonitoring remote-write destination).

# Basic auth and extra HTTP headers from metaMonitoring are ignored, please use customHeaders.

# The remote URL is used even if metamonitoring is disabled.

# For more details about migrating to autoscaling, refer to https://grafana.com/docs/helm-charts/mimir-distributed/latest/configure/configure-autoscaling/#migrate-existing-deployments

kedaAutoscaling:

enabled: false

# -- preserveReplicas gives you the option to migrate from non-autoscaled to autoscaled deployments without losing replicas. When set to true, the replica fields in the component will be left intact.

# For more details about migrating to autoscaling, refer to https://grafana.com/docs/helm-charts/mimir-distributed/latest/configure/configure-autoscaling/#migrate-existing-deployments

preserveReplicas: false

minReplicaCount: 1

maxReplicaCount: 10

# -- Target CPU utilization percentage for KEDA autoscaling. This controls the headroom each pod has compared to its current usage.

# targetting lower percentages overprovisions the containers, so they can handle bursts of traffic and tolerate failures without waiting to scale out.

targetCPUUtilizationPercentage: 100

# -- Target memory utilization percentage for KEDA autoscaling. This controls the headroom each pod has compared to its current usage.

# targetting lower percentages overprovisions the containers, so they can handle bursts of traffic and tolerate failures without waiting to scale out.

targetMemoryUtilizationPercentage: 100

behavior:

scaleDown:

policies:

- periodSeconds: 600

type: Percent

value: 10

# -- Fallback configuration for this component. If not set (null), the global kedaAutoscaling.fallback configuration is used.

# fallback: {}

service:

annotations: {}

labels: {}

# -- https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/

internalTrafficPolicy: Cluster

type: ClusterIP

extraPorts: []

# -- Dedicated service account for ruler pods.

# If not set, the default service account defined at the begining of this file will be used.

# This service account can be used even if the default one is not set.

serviceAccount:

create: false

# -- Ruler specific service account name. If not set and create is set to true, the default

# name will be the default mimir service account's name with the "-ruler" suffix.

name: ""

annotations: {}

labels: {}

resources:

requests:

cpu: 100m

memory: 128Mi

# Additional ruler container arguments, e.g. log level (debug, info, warn, error)

extraArgs: {}

# log.level: debug

# -- Size in bytes of the memory ballast (-mem-ballast-size-bytes). The ballast reduces GC frequency

# and CPU usage around ruler start and rollouts. It must be smaller than any GOMEMLIMIT set on the

# ruler, otherwise the GC thrashes permanently. Set to 0 to disable the ballast.

memBallastSizeBytes: 1073741824

# Pod Labels

podLabels: {}

# Pod Annotations

podAnnotations: {}

# Pod Disruption Budget

podDisruptionBudget:

maxUnavailable: 1

dnsConfig: {}

nodeSelector: {}

affinity: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints:

maxSkew: 1

topologyKey: kubernetes.io/hostname

whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

annotations: {}

persistence:

subPath:

readinessProbe:

httpGet:

path: /ready

port: http-metrics

initialDelaySeconds: 45

# -- SecurityContext override for ruler pods

securityContext: {}

# -- The SecurityContext for ruler containers

containerSecurityContext:

allowPrivilegeEscalation: false

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

strategy:

type: RollingUpdate

rollingUpdate:

maxSurge: 50%

maxUnavailable: 0

terminationGracePeriodSeconds: 600

tolerations: []

initContainers: []

extraContainers: []

extraVolumes: []

extraVolumeMounts: []

env: []

extraEnvFrom: []

# -- If set to true, a dedicated query path will be deployed for the ruler and operational mode will be set to use remote evaluation. https://grafana.com/docs/mimir/latest/references/architecture/components/ruler/#remote

# -- This is useful for isolating the ruler queries from other queriers (api/grafana).

remoteEvaluationDedicatedQueryPath: false

# -- Only deployed if .Values.ruler.remoteEvaluationDedicatedQueryPath

ruler_querier:

# -- Allows to override the container image of the ruler-querier component.

# When set it takes precedence over what is defined in global "image".

image:

# repository: grafana/mimir

# tag: 3.2.0

replicas: 2

revisionHistoryLimit: null

# -- [Experimental] Configure autoscaling via KEDA (https://keda.sh). This requires having

# KEDA already installed in the Kubernetes cluster. The metrics for scaling are read

# according to top-level kedaAutoscaling.prometheusAddress (defaulting to metamonitoring remote-write destination).

# Basic auth and extra HTTP headers from metaMonitoring are ignored, please use customHeaders.

# The remote URL is used even if metamonitoring is disabled.

# For more details about migrating to autoscaling, refer to https://grafana.com/docs/helm-charts/mimir-distributed/latest/configure/configure-autoscaling/#migrate-existing-deployments

kedaAutoscaling:

enabled: false

# -- preserveReplicas gives you the option to migrate from non-autoscaled to autoscaled deployments without losing replicas. When set to true, the replica fields in the component will be left intact.

# For more details about migrating to autoscaling, refer to https://grafana.com/docs/helm-charts/mimir-distributed/latest/configure/configure-autoscaling/#migrate-existing-deployments

preserveReplicas: false

minReplicaCount: 1

maxReplicaCount: 10

querySchedulerInflightRequestsThreshold: 12

behavior:

scaleDown:

policies:

- periodSeconds: 120

type: Percent

value: 10

stabilizationWindowSeconds: 600

scaleUp:

policies:

- periodSeconds: 120

type: Percent

value: 50

- periodSeconds: 120

type: Pods

value: 15

stabilizationWindowSeconds: 60

# -- Fallback configuration for this component. If not set (null), the global kedaAutoscaling.fallback configuration is used.

# fallback: {}

service:

annotations: {}

labels: {}

# -- https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/

internalTrafficPolicy: Cluster

type: ClusterIP

extraPorts: []

resources:

requests:

cpu: 100m

memory: 128Mi

# Additional ruler-querier container arguments, e.g. log level (debug, info, warn, error)

extraArgs: {}

# Pod Labels

podLabels: {}

# Pod Annotations

podAnnotations: {}

# Pod Disruption Budget

podDisruptionBudget:

maxUnavailable: 1

# -- The name of the PriorityClass for ruler-querier pods

priorityClassName: null

dnsConfig: {}

nodeSelector: {}

affinity: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints:

maxSkew: 1

topologyKey: kubernetes.io/hostname

whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

annotations: {}

persistence:

subPath:

readinessProbe:

httpGet:

path: /ready

port: http-metrics

initialDelaySeconds: 45

# -- SecurityContext override for ruler-querier pods

securityContext: {}

# -- The SecurityContext for ruler-querier containers

containerSecurityContext:

allowPrivilegeEscalation: false

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

strategy:

type: RollingUpdate

rollingUpdate:

maxUnavailable: 0

maxSurge: 15%

terminationGracePeriodSeconds: 180

tolerations: []

initContainers: []

extraContainers: []

extraVolumes: []

extraVolumeMounts: []

env: []

extraEnvFrom: []

# -- Only deployed if .Values.ruler.remoteEvaluationDedicatedQueryPath

ruler_query_frontend:

# -- Allows to override the container image of the ruler-query-frontend component.

# When set it takes precedence over what is defined in global "image".

image:

# repository: grafana/mimir

# tag: 3.2.0

# Setting it to null will produce a deployment without replicas set, allowing you to use autoscaling with the deployment

replicas: 1

revisionHistoryLimit: null

# -- [Experimental] Configure autoscaling via KEDA (https://keda.sh). This requires having

# KEDA already installed in the Kubernetes cluster. The metrics for scaling are read

# according to top-level kedaAutoscaling.prometheusAddress (defaulting to metamonitoring remote-write destination).

# Basic auth and extra HTTP headers from metaMonitoring are ignored, please use customHeaders.

# The remote URL is used even if metamonitoring is disabled.

# For more details about migrating to autoscaling, refer to https://grafana.com/docs/helm-charts/mimir-distributed/latest/configure/configure-autoscaling/#migrate-existing-deployments

kedaAutoscaling:

enabled: false

# -- preserveReplicas gives you the option to migrate from non-autoscaled to autoscaled deployments without losing replicas. When set to true, the replica fields in the component will be left intact.

# For more details about migrating to autoscaling, refer to https://grafana.com/docs/helm-charts/mimir-distributed/latest/configure/configure-autoscaling/#migrate-existing-deployments

preserveReplicas: false

minReplicaCount: 1

maxReplicaCount: 10

# -- Target CPU utilization percentage for KEDA autoscaling. This controls the headroom each pod has compared to its current usage.

# targetting lower percentages overprovisions the containers, so they can handle bursts of traffic and tolerate failures without waiting to scale out.

targetCPUUtilizationPercentage: 75

# -- Target memory utilization percentage for KEDA autoscaling. This controls the headroom each pod has compared to its current usage.

# targetting lower percentages overprovisions the containers, so they can handle bursts of traffic and tolerate failures without waiting to scale out.

targetMemoryUtilizationPercentage: 100

behavior:

scaleDown:

policies:

- periodSeconds: 60

type: Percent

value: 10

# -- Fallback configuration for this component. If not set (null), the global kedaAutoscaling.fallback configuration is used.

# fallback: {}

service:

annotations: {}

labels: {}

# -- https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/

internalTrafficPolicy: Cluster

type: ClusterIP

extraPorts: []

resources:

requests:

cpu: 100m

memory: 128Mi

# Additional ruler-query-frontend container arguments, e.g. log level (debug, info, warn, error)

extraArgs: {}

# Pod Labels

podLabels: {}

# Pod Annotations

podAnnotations: {}

# Pod Disruption Budget

podDisruptionBudget:

maxUnavailable: 1

# -- The name of the PriorityClass for ruler-query-frontend pods

priorityClassName: null

dnsConfig: {}

nodeSelector: {}

affinity: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints:

maxSkew: 1

topologyKey: kubernetes.io/hostname

whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

annotations: {}

persistence:

subPath:

readinessProbe:

httpGet:

path: /ready

port: http-metrics

initialDelaySeconds: 45

# -- SecurityContext override for query-fronted pods

securityContext: {}

# -- The SecurityContext for ruler-query-frontend containers

containerSecurityContext:

allowPrivilegeEscalation: false

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

strategy:

type: RollingUpdate

rollingUpdate:

maxUnavailable: 0

maxSurge: 15%

terminationGracePeriodSeconds: 390

tolerations: []

initContainers: []

extraContainers: []

extraVolumes: []

extraVolumeMounts: []

env: []

extraEnvFrom: []

# -- Only deployed if .Values.ruler.remoteEvaluationDedicatedQueryPath

ruler_query_scheduler:

# -- Allows to override the container image of the ruler-query-scheduler component.

# When set it takes precedence over what is defined in global "image".

image:

# repository: grafana/mimir

# tag: 3.2.0

replicas: 2

revisionHistoryLimit: null

service:

annotations: {}

labels: {}

# -- https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/

internalTrafficPolicy: Cluster

type: ClusterIP

extraPorts: []

resources:

requests:

cpu: 100m

memory: 128Mi

# Additional ruler-query-scheduler container arguments, e.g. log level (debug, info, warn, error)

extraArgs: {}

# Pod Labels

podLabels: {}

# Pod Annotations

podAnnotations: {}

# Pod Disruption Budget

podDisruptionBudget:

maxUnavailable: 1

# -- The name of the PriorityClass for ruler-query-scheduler pods

priorityClassName: null

dnsConfig: {}

nodeSelector: {}

affinity: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints:

maxSkew: 1

topologyKey: kubernetes.io/hostname

whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

annotations: {}

persistence:

subPath:

readinessProbe:

httpGet:

path: /ready

port: http-metrics

initialDelaySeconds: 45

# -- SecurityContext override for ruler-query-scheduler pods

securityContext: {}

# -- The SecurityContext for ruler-query-scheduler containers

containerSecurityContext:

allowPrivilegeEscalation: false

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

strategy:

type: RollingUpdate

rollingUpdate:

maxUnavailable: 0

maxSurge: 1

terminationGracePeriodSeconds: 180

tolerations: []

initContainers: []

extraContainers: []

extraVolumes: []

extraVolumeMounts: []

env: []

extraEnvFrom: []

querier:

# -- Whether to render the manifests related to the querier component.

enabled: true

# -- Allows to override the container image of the querier component.

# When set it takes precedence over what is defined in global "image".

image:

# repository: grafana/mimir

# tag: 3.2.0

replicas: 2

revisionHistoryLimit: null

# -- [Experimental] Configure autoscaling via KEDA (https://keda.sh). This requires having

# KEDA already installed in the Kubernetes cluster. The metrics for scaling are read

# according to top-level kedaAutoscaling.prometheusAddress (defaulting to metamonitoring remote-write destination).

# Basic auth and extra HTTP headers from metaMonitoring are ignored, please use customHeaders.

# The remote URL is used even if metamonitoring is disabled.

# For more details about migrating to autoscaling, refer to https://grafana.com/docs/helm-charts/mimir-distributed/latest/configure/configure-autoscaling/#migrate-existing-deployments

kedaAutoscaling:

enabled: false

# -- preserveReplicas gives you the option to migrate from non-autoscaled to autoscaled deployments without losing replicas. When set to true, the replica fields in the component will be left intact.

# For more details about migrating to autoscaling, refer to https://grafana.com/docs/helm-charts/mimir-distributed/latest/configure/configure-autoscaling/#migrate-existing-deployments

preserveReplicas: false

minReplicaCount: 1

maxReplicaCount: 10

querySchedulerInflightRequestsThreshold: 12

# -- predictiveScalingEnabled scales up the querier based on the inflight requests in the past.

# This helps with scaling up for predictable traffic patterns and minimizing HTTP 429 responses due to filled query queues.

# Due to false positive items it can increase the querier TCO.

predictiveScalingEnabled: false

# -- The period to consider when considering scheduler metrics for predictive scaling.

# This is usually slightly lower than the period of the repeating query events to give scaling up lead time.

predictiveScalingPeriod: 6d23h30m

# -- The time range to consider when considering scheduler metrics for predictive scaling.

# For example: if lookback is 30m and period is 6d23h30m,

# the querier will scale based on the maximum inflight queries between 6d23h30m and 7d ago.

predictiveScalingLookback: 30m

behavior:

scaleDown:

policies:

- periodSeconds: 120

type: Percent

value: 10

stabilizationWindowSeconds: 600

scaleUp:

policies:

- periodSeconds: 120

type: Percent

value: 50

- periodSeconds: 120

type: Pods

value: 15

stabilizationWindowSeconds: 60

# -- Fallback configuration for this component. If not set (null), the global kedaAutoscaling.fallback configuration is used.

# fallback: {}

service:

annotations: {}

labels: {}

# -- https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/

internalTrafficPolicy: Cluster

type: ClusterIP

extraPorts: []

# -- https://kubernetes.io/docs/concepts/services-networking/service/#traffic-distribution

trafficDistribution: ""

resources:

requests:

cpu: 100m

memory: 128Mi

# Additional querier container arguments, e.g. log level (debug, info, warn, error)

extraArgs: {}

# Pod Labels

podLabels: {}

# Pod Annotations

podAnnotations: {}

# Pod Disruption Budget

podDisruptionBudget:

maxUnavailable: 1

# -- The name of the PriorityClass for querier pods

priorityClassName: null

dnsConfig: {}

nodeSelector: {}

affinity: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints:

maxSkew: 1

topologyKey: kubernetes.io/hostname

whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

annotations: {}

persistence:

subPath:

readinessProbe:

httpGet:

path: /ready

port: http-metrics

initialDelaySeconds: 45

# -- SecurityContext override for querier pods

securityContext: {}

# -- The SecurityContext for querier containers

containerSecurityContext:

allowPrivilegeEscalation: false

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

strategy:

type: RollingUpdate

rollingUpdate:

maxUnavailable: 0

maxSurge: 15%

terminationGracePeriodSeconds: 180

tolerations: []

initContainers: []

extraContainers: []

extraVolumes: []

extraVolumeMounts: []

env: []

extraEnvFrom: []

query_frontend:

# -- Whether to render the manifests related to the query-frontend component.

enabled: true

# -- Allows to override the container image of the query-frontend component.

# When set it takes precedence over what is defined in global "image".

image:

# repository: grafana/mimir

# tag: 3.2.0

# Setting it to null will produce a deployment without replicas set, allowing you to use autoscaling with the deployment

replicas: 1

revisionHistoryLimit: null

# -- [Experimental] Configure autoscaling via KEDA (https://keda.sh). This requires having

# KEDA already installed in the Kubernetes cluster. The metrics for scaling are read

# according to top-level kedaAutoscaling.prometheusAddress (defaulting to metamonitoring remote-write destination).

# Basic auth and extra HTTP headers from metaMonitoring are ignored, please use customHeaders.

# The remote URL is used even if metamonitoring is disabled.

# For more details about migrating to autoscaling, refer to https://grafana.com/docs/helm-charts/mimir-distributed/latest/configure/configure-autoscaling/#migrate-existing-deployments

kedaAutoscaling:

enabled: false

# -- preserveReplicas gives you the option to migrate from non-autoscaled to autoscaled deployments without losing replicas. When set to true, the replica fields in the component will be left intact.

# For more details about migrating to autoscaling, refer to https://grafana.com/docs/helm-charts/mimir-distributed/latest/configure/configure-autoscaling/#migrate-existing-deployments

preserveReplicas: false

minReplicaCount: 1

maxReplicaCount: 10

# -- Target CPU utilization percentage for KEDA autoscaling. This controls the headroom each pod has compared to its current usage.

# targetting lower percentages overprovisions the containers, so they can handle bursts of traffic and tolerate failures without waiting to scale out.

targetCPUUtilizationPercentage: 75

# -- Target memory utilization percentage for KEDA autoscaling. This controls the headroom each pod has compared to its current usage.

# targetting lower percentages overprovisions the containers, so they can handle bursts of traffic and tolerate failures without waiting to scale out.

targetMemoryUtilizationPercentage: 100

behavior:

scaleDown:

policies:

- periodSeconds: 60

type: Percent

value: 10

# -- Fallback configuration for this component. If not set (null), the global kedaAutoscaling.fallback configuration is used.

# fallback: {}

service:

annotations: {}

labels: {}

# -- https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/

internalTrafficPolicy: Cluster

type: ClusterIP

extraPorts: []

# -- https://kubernetes.io/docs/concepts/services-networking/service/#traffic-distribution

trafficDistribution: ""

resources:

requests:

cpu: 100m

memory: 128Mi

# Additional query-frontend container arguments, e.g. log level (debug, info, warn, error)

extraArgs: {}

# Pod Labels

podLabels: {}

# Pod Annotations

podAnnotations: {}

# Pod Disruption Budget

podDisruptionBudget:

maxUnavailable: 1

# -- The name of the PriorityClass for query-frontend pods

priorityClassName: null

dnsConfig: {}

nodeSelector: {}

affinity: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints:

maxSkew: 1

topologyKey: kubernetes.io/hostname

whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

annotations: {}

persistence:

subPath:

readinessProbe:

httpGet:

path: /ready

port: http-metrics

initialDelaySeconds: 45

# -- SecurityContext override for query-fronted pods

securityContext: {}

# -- The SecurityContext for query-frontend containers

containerSecurityContext:

allowPrivilegeEscalation: false

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

strategy:

type: RollingUpdate

rollingUpdate:

maxUnavailable: 0

maxSurge: 15%

terminationGracePeriodSeconds: 390

tolerations: []

initContainers: []

extraContainers: []

extraVolumes: []

extraVolumeMounts: []

env: []

extraEnvFrom: []

query_scheduler:

enabled: true

# -- Allows to override the container image of the query-scheduler component.

# When set it takes precedence over what is defined in global "image".

image:

# repository: grafana/mimir

# tag: 3.2.0

replicas: 2

revisionHistoryLimit: null

service:

annotations: {}

labels: {}

# -- https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/

internalTrafficPolicy: Cluster

type: ClusterIP

extraPorts: []

# -- https://kubernetes.io/docs/concepts/services-networking/service/#traffic-distribution

trafficDistribution: ""

resources:

requests:

cpu: 100m

memory: 128Mi

# Additional query-scheduler container arguments, e.g. log level (debug, info, warn, error)

extraArgs: {}

# Pod Labels

podLabels: {}

# Pod Annotations

podAnnotations: {}

# Pod Disruption Budget

podDisruptionBudget:

maxUnavailable: 1

# -- The name of the PriorityClass for query-scheduler pods

priorityClassName: null

dnsConfig: {}

nodeSelector: {}

affinity: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints:

maxSkew: 1

topologyKey: kubernetes.io/hostname

whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

annotations: {}

persistence:

subPath:

readinessProbe:

httpGet:

path: /ready

port: http-metrics

initialDelaySeconds: 45

# -- SecurityContext override for query-scheduler pods

securityContext: {}

# -- The SecurityContext for query-scheduler containers

containerSecurityContext:

allowPrivilegeEscalation: false

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

strategy:

type: RollingUpdate

rollingUpdate:

maxUnavailable: 0

maxSurge: 1

terminationGracePeriodSeconds: 180

tolerations: []

initContainers: []

extraContainers: []

extraVolumes: []

extraVolumeMounts: []

env: []

extraEnvFrom: []

store_gateway:

# -- Whether to render the manifests related to the store-gateway component.

enabled: true

# -- Allows to override the container image of the store-gateway component.

# When set it takes precedence over what is defined in global "image".

image:

# repository: grafana/mimir

# tag: 3.2.0

# -- Total number of replicas for the store-gateway across all availability zones

# If store_gateway.zoneAwareReplication.enabled=false, this number is taken as is.

# Otherwise each zone starts `ceil(replicas / number_of_zones)` number of pods.

# E.g. if 'replicas' is set to 4 and there are 3 zones, then 4/3=1.33 and after rounding up it means 2 pods per zone are started.

replicas: 1

revisionHistoryLimit: null

service:

annotations: {}

labels: {}

# -- https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/

internalTrafficPolicy: Cluster

type: ClusterIP

extraPorts: []

# -- https://kubernetes.io/docs/concepts/services-networking/service/#traffic-distribution

# Note: This service is not responsible for read path traffic.

trafficDistribution: ""

# -- Optionally set the scheduler for pods of the store-gateway

schedulerName: ""

resources:

requests:

cpu: 100m

memory: 512Mi

# Additional store-gateway container arguments, e.g. log level (debug, info, warn, error)

extraArgs: {}

# Pod Labels

podLabels: {}

# Pod Annotations

podAnnotations: {}

# -- Management policy for store-gateway pods

# New variable introduced with Helm chart version 5.1.0. For backwards compatibility it is set to `OrderedReady`

# On new deployments it is highly recommended to switch it to `Parallel` as this will be the new default from 6.0.0

podManagementPolicy: OrderedReady

# -- Pod Disruption Budget for store-gateway, this will be applied across availability zones to prevent losing redundancy

podDisruptionBudget:

maxUnavailable: 1

# -- The name of the PriorityClass for store-gateway pods

priorityClassName: null

dnsConfig: {}

# -- NodeSelector to pin store-gateway pods to certain set of nodes. This is ignored when store_gateway.zoneAwareReplication.enabled=true.

nodeSelector: {}

# -- Pod affinity settings for the store_gateway. This is ignored when store_gateway.zoneAwareReplication.enabled=true.

affinity: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

# It is recommended to replace this with requiredDuringSchedulingIgnoredDuringExecution podAntiAffinity rules when

# deploying to production.

topologySpreadConstraints:

maxSkew: 1

topologyKey: kubernetes.io/hostname

whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

annotations: {}

persistentVolume:

# If true Store-gateway will create/use a Persistent Volume Claim

# If false, use emptyDir

#

enabled: true

# additional settings for emptyDir like medium or sizeLimit

#

emptyDir: {}

# medium: Memory

# sizeLimit: 1Gi

# Store-gateway data Persistent Volume Claim template name

#

name: storage

# Store-gateway data Persistent Volume Claim annotations

#

annotations: {}

# Store-gateway data Persistent Volume Claim labels

#

labels: {}

# Store-gateway data Persistent Volume access modes

# Must match those of existing PV or dynamic provisioner

# Ref: http://kubernetes.io/docs/user-guide/persistent-volumes/

#

accessModes:

- ReadWriteOnce

# Store-gateway data Persistent Volume size

#

size: 2Gi

# Subdirectory of Store-gateway data Persistent Volume to mount

# Useful if the volume's root directory is not empty

#

subPath: ""

# Store-gateway data Persistent Volume Storage Class

# If defined, storageClassName: <storageClass>

# If set to "-", storageClassName: "", which disables dynamic provisioning

# If undefined (the default) or set to null, no storageClassName spec is

# set, choosing the default provisioner.

#

# A per-zone storageClass configuration in `store_gateway.zoneAwareReplication.zones[*].storageClass` takes precedence over this field.

# storageClass: "-"

# volumeAttributesClassName: my-cluster-vac

# Requires Kubernetes 1.31+ and a CSI driver with ModifyVolume support.

# Must reference an existing cluster VolumeAttributesClass.

# A per-zone volumeAttributesClassName in `store_gateway.zoneAwareReplication.zones[*].volumeAttributesClassName` takes precedence over this field when set.

# -- Enable StatefulSetAutoDeletePVC feature

# https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#persistentvolumeclaim-retention

enableRetentionPolicy: false

whenDeleted: Retain

whenScaled: Retain

readinessProbe:

httpGet:

path: /ready

port: http-metrics

initialDelaySeconds: 60

# -- SecurityContext override for store-gateway pods

securityContext: {}

# -- The SecurityContext for store-gateway containers

containerSecurityContext:

allowPrivilegeEscalation: false

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

# -- updateStrategy of the store-gateway statefulset. This is ignored when store_gateway.zoneAwareReplication.enabled=true.

strategy:

type: RollingUpdate

terminationGracePeriodSeconds: 120

# -- The maximum size of a query response in bytes. Sets max send size for store-gateway and receive size for queriers.

grpcMaxQueryResponseSizeBytes: "209715200"

tolerations: []

initContainers: []

extraContainers: []

extraVolumes: []

extraVolumeMounts: []

env: []

extraEnvFrom: []

# -- Options to configure zone-aware replication for store-gateway

# Example configuration with full geographical redundancy:

# rollout_operator:

# enabled: true

# store_gateway:

# zoneAwareReplication:

# enabled: true

# topologyKey: 'kubernetes.io/hostname' # This generates default anti-affinity rules

# zones: # Zone list has to be fully redefined for modification. Update with you actual zones or skip to use logical zones only.

# - name: zone-a

# nodeSelector:

# topology.kubernetes.io/zone: us-central1-a

# - name: zone-b

# nodeSelector:

# topology.kubernetes.io/zone: us-central1-b

# - name: zone-c

# nodeSelector:

# topology.kubernetes.io/zone: us-central1-c

#

zoneAwareReplication:

# -- Enable zone-aware replication for store-gateway

enabled: true

# -- Maximum number of store-gateways that can be unavailable per zone during rollout

maxUnavailable: 50

# -- Minimum time for the rollout operator to wait between store-gateway zone down scales

minTimeBetweenZonesDownscale: 30m

# -- topologyKey to use in pod anti-affinity. If unset, no anti-affinity rules are generated. If set, the generated anti-affinity rule makes sure that pods from different zones do not mix.

# E.g.: topologyKey: 'kubernetes.io/hostname'

topologyKey: null

# -- Auxiliary values for migration, see https://grafana.com/docs/helm-charts/mimir-distributed/latest/migration-guides/migrate-from-single-zone-with-helm/

migration:

# -- Indicate if migration is ongoing for multi zone store-gateway

enabled: false

# -- Enable zone-awareness on the readPath

readPath: false

# -- Zone definitions for store-gateway zones. Note: you have to redefine the whole list to change parts as YAML does not allow to modify parts of a list.

zones:

# -- Name of the zone, used in labels and selectors. Must follow Kubernetes naming restrictions: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/

- name: zone-a

# -- nodeselector to restrict where pods of this zone can be placed. E.g.:

# nodeSelector:

# topology.kubernetes.io/zone: zone-a

nodeSelector: null

# -- extraAffinity adds user defined custom affinity rules (merged with generated rules)

extraAffinity: {}

# -- StoreGateway data Persistent Volume Storage Class

# If defined, storageClassName: <storageClass>

# If set to "-", then use `storageClassName: ""`, which disables dynamic provisioning

# If undefined or set to null (the default), then fall back to the value of `store_gateway.persistentVolume.storageClass`.

storageClass: null

# -- Persistent Volume VolumeAttributesClass for this zone.

# If undefined or set to null (the default), then fall back to the component `persistentVolume.volumeAttributesClassName`.

volumeAttributesClassName: null

# -- noDownscale adds a label that can be used by the rollout-operator as documented in the rollout-operator repo: https://github.com/grafana/rollout-operator#webhooks

noDownscale: false

# -- downscaleLeader is an Annotation used by the rollout-operator to coordinate downscaling across zones.

# Set to the StatefulSet name that should lead downscaling for this component (typically the previous zone).

# Example: "mimir-store-gateway-zone-a" for zone-b, "mimir-store-gateway-zone-b" for zone-c.

# If undefined or set to null (the default), this zone won't be designated as a downscale leader.

downscaleLeader: null

# -- prepareDownscale adds labels and annotations for the rollout-operator to prepare downscaling: https://github.com/grafana/rollout-operator#how-scaling-up-and-down-works

prepareDownscale: true

# -- Name of the zone, used in labels and selectors. Must follow Kubernetes naming restrictions: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/

- name: zone-b

# -- nodeselector to restrict where pods of this zone can be placed. E.g.:

# nodeSelector:

# topology.kubernetes.io/zone: zone-b

nodeSelector: null

# -- extraAffinity adds user defined custom affinity rules (merged with generated rules)

extraAffinity: {}

# -- StoreGateway data Persistent Volume Storage Class

# If defined, storageClassName: <storageClass>

# If set to "-", then use `storageClassName: ""`, which disables dynamic provisioning

# If undefined or set to null (the default), then fall back to the value of `store_gateway.persistentVolume.storageClass`.

storageClass: null

# -- Persistent Volume VolumeAttributesClass for this zone.

# If undefined or set to null (the default), then fall back to the component `persistentVolume.volumeAttributesClassName`.

volumeAttributesClassName: null

# -- noDownscale adds a label that can be used by the rollout-operator as documented in the rollout-operator repo: https://github.com/grafana/rollout-operator#webhooks

noDownscale: false

# -- downscaleLeader is an Annotation used by the rollout-operator to coordinate downscaling across zones.

# Set to the StatefulSet name that should lead downscaling for this component (typically the previous zone).

# Example: "mimir-store-gateway-zone-a" for zone-b, "mimir-store-gateway-zone-b" for zone-c.

# If undefined or set to null (the default), this zone won't be designated as a downscale leader.

downscaleLeader: null

# -- prepareDownscale adds labels and annotations for the rollout-operator to prepare downscaling: https://github.com/grafana/rollout-operator#how-scaling-up-and-down-works

prepareDownscale: true

# -- Name of the zone, used in labels and selectors. Must follow Kubernetes naming restrictions: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/

- name: zone-c

# -- nodeselector to restrict where pods of this zone can be placed. E.g.:

# nodeSelector:

# topology.kubernetes.io/zone: zone-c

nodeSelector: null

# -- extraAffinity adds user defined custom affinity rules (merged with generated rules)

extraAffinity: {}

# -- StoreGateway data Persistent Volume Storage Class

# If defined, storageClassName: <storageClass>

# If set to "-", then use `storageClassName: ""`, which disables dynamic provisioning

# If undefined or set to null (the default), then fall back to the value of `store_gateway.persistentVolume.storageClass`.

storageClass: null

# -- Persistent Volume VolumeAttributesClass for this zone.

# If undefined or set to null (the default), then fall back to the component `persistentVolume.volumeAttributesClassName`.

volumeAttributesClassName: null

# -- noDownscale adds a label that can be used by the rollout-operator as documented in the rollout-operator repo: https://github.com/grafana/rollout-operator#webhooks

noDownscale: false

# -- downscaleLeader is an Annotation used by the rollout-operator to coordinate downscaling across zones.

# Set to the StatefulSet name that should lead downscaling for this component (typically the previous zone).

# Example: "mimir-store-gateway-zone-a" for zone-b, "mimir-store-gateway-zone-b" for zone-c.

# If undefined or set to null (the default), this zone won't be designated as a downscale leader.

downscaleLeader: null

# -- prepareDownscale adds labels and annotations for the rollout-operator to prepare downscaling: https://github.com/grafana/rollout-operator#how-scaling-up-and-down-works

prepareDownscale: true

compactor:

# -- Whether to render the manifests related to the compactor component.

enabled: true

# -- Allows to override the container image of the compactor component.

# When set it takes precedence over what is defined in global "image".

image:

# repository: grafana/mimir

# tag: 3.2.0

replicas: 1

revisionHistoryLimit: null

service:

annotations: {}

labels: {}

# -- https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/

internalTrafficPolicy: Cluster

type: ClusterIP

extraPorts: []

# -- Optionally set the scheduler for pods of the compactor

schedulerName: ""

resources:

requests:

cpu: 100m

memory: 512Mi

# Additional compactor container arguments, e.g. log level (debug, info, warn, error)

extraArgs: {}

# Pod Labels

podLabels: {}

# Pod Annotations

podAnnotations: {}

# Pod Disruption Budget

podDisruptionBudget:

maxUnavailable: 1

podManagementPolicy: OrderedReady

# -- The name of the PriorityClass for compactor pods

priorityClassName: null

dnsConfig: {}

nodeSelector: {}

affinity: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints:

maxSkew: 1

topologyKey: kubernetes.io/hostname

whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

annotations: {}

persistentVolume:

# If true compactor will create/use a Persistent Volume Claim

# If false, use emptyDir

#

enabled: true

# compactor data Persistent Volume Claim template name

#

name: storage

# compactor data Persistent Volume Claim annotations

#

annotations: {}

# compactor data Persistent Volume Claim labels

#

labels: {}

# compactor data Persistent Volume access modes

# Must match those of existing PV or dynamic provisioner

# Ref: http://kubernetes.io/docs/user-guide/persistent-volumes/

#

accessModes:

- ReadWriteOnce

# compactor data Persistent Volume size

#

size: 2Gi

# Subdirectory of compactor data Persistent Volume to mount

# Useful if the volume's root directory is not empty

#

subPath: ""

# compactor data Persistent Volume Storage Class

# If defined, storageClassName: <storageClass>

# If set to "-", storageClassName: "", which disables dynamic provisioning

# If undefined (the default) or set to null, no storageClassName spec is

# set, choosing the default provisioner.

#

# storageClass: "-"

# compactor Persistent Volume Attributes Class

# Allows you to dynamically modify a volume's attributes on the fly

# Requires Kubernetes 1.31+ and a CSI driver with ModifyVolume support.

# Must reference an existing cluster VolumeAttributesClass.

# volumeAttributesClassName: my-cluster-vac

# -- Enable StatefulSetAutoDeletePVC feature

# https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#persistentvolumeclaim-retention

enableRetentionPolicy: false

whenDeleted: Retain

whenScaled: Retain

readinessProbe:

httpGet:

path: /ready

port: http-metrics

initialDelaySeconds: 60

# -- SecurityContext override for compactor pods

securityContext: {}

# -- The SecurityContext for compactor containers

containerSecurityContext:

allowPrivilegeEscalation: false

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

strategy:

type: RollingUpdate

terminationGracePeriodSeconds: 900

tolerations: []

initContainers: []

extraContainers: []

extraVolumes: []

extraVolumeMounts: []

env: []

extraEnvFrom: []

gossip_ring:

service:

annotations: {}

memcached:

image:

# -- Memcached Docker image repository

repository: chainreg.biz/chainguard-private/memcached

# -- Memcached Docker image tag

tag: 1.6.45-r3@sha256:3905846a49548e6c72928c992a512d14e7f33a13338febea10b9be16cccc3049

# -- Memcached Docker image pull policy

pullPolicy: IfNotPresent

# -- The SecurityContext override for memcached pods

podSecurityContext: {}

# -- The name of the PriorityClass for memcached pods

priorityClassName: null

# -- The SecurityContext for memcached containers

containerSecurityContext:

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

allowPrivilegeEscalation: false

memcachedExporter:

# -- Whether memcached metrics should be exported

enabled: true

image:

repository: chainreg.biz/chainguard-private/memcached-exporter

tag: 0.17.0-r3@sha256:e9a5267b225f17dbd3617e60c31dd41791ea1e7009704de82a577035c073a897

pullPolicy: IfNotPresent

resources:

requests:

cpu: 50m

memory: 50Mi

limits:

memory: 250Mi

# -- The SecurityContext for memcached exporter containers

containerSecurityContext:

readOnlyRootFilesystem: true

capabilities:

drop: [ALL]

allowPrivilegeEscalation: false

# -- Extra args to add to the exporter container.

# Example:

# extraArgs:

# memcached.tls.enable: true

# memcached.tls.cert-file: /certs/cert.crt

# memcached.tls.key-file: /certs/cert.key

# memcached.tls.ca-file: /certs/ca.crt

# memcached.tls.insecure-skip-verify: false

# memcached.tls.server-name: memcached

extraArgs: {}

chunks-cache:

# -- Specifies whether memcached based chunks-cache should be enabled

enabled: false

# -- How long each pod must be ready for before the next one is started/restarted

minReadySeconds: 60

# -- Total number of chunks-cache replicas

replicas: 1

# -- Number of old ReplicaSets to retain to allow rollback (if not set, the default Kubernetes value is set to 10)

revisionHistoryLimit: null

# -- Port of the chunks-cache service

port: 11211

# -- Amount of memory allocated to chunks-cache for object storage (in MB).

allocatedMemory: 8192

# -- Maximum item memory for chunks-cache (in MB).

maxItemMemory: 1

# -- Maximum number of connections allowed

connectionLimit: 16384

# -- Extra init containers for chunks-cache pods

initContainers: []

# -- Annotations for the chunks-cache pods

annotations: {}

# -- Node selector for chunks-cache pods

nodeSelector: {}

# -- Affinity for chunks-cache pods

affinity: {}

dnsConfig: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints: {}

# maxSkew: 1

# topologyKey: kubernetes.io/hostname

# whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

# -- Tolerations for chunks-cache pods

tolerations: []

# -- Pod Disruption Budget

podDisruptionBudget:

maxUnavailable: 1

# -- The name of the PriorityClass for chunks-cache pods

priorityClassName: null

# -- Labels for chunks-cache pods

podLabels: {}

# -- Annotations for chunks-cache pods

podAnnotations: {}

# -- Management policy for chunks-cache pods

podManagementPolicy: Parallel

# -- Grace period to allow the chunks-cache to shutdown before it is killed

terminationGracePeriodSeconds: 30

# -- Stateful chunks-cache strategy

statefulStrategy:

type: RollingUpdate

# -- Add extended options for chunks-cache memcached container. The format is the same as for the memcached -o/--extend flag.

# Example:

# extraExtendedOptions: 'tls,no_hashexpand'

extraExtendedOptions: ""

# -- Additional CLI args for chunks-cache

extraArgs: {}

# -- Additional containers to be added to the chunks-cache pod.

extraContainers: []

# -- Additional volumes to be added to the chunks-cache pod (applies to both memcached and exporter containers).

# Example:

# extraVolumes:

# - name: extra-volume

# secret:

# secretName: extra-volume-secret

extraVolumes: []

# -- Additional volume mounts to be added to the chunks-cache pod (applies to both memcached and exporter containers).

# Example:

# extraVolumeMounts:

# - name: extra-volume

# mountPath: /etc/extra-volume

# readOnly: true

extraVolumeMounts: []

# -- List of additional PVCs to be created for the chunks-cache statefulset

volumeClaimTemplates: []

# -- Resource requests and limits for the chunks-cache

# By default a safe memory limit will be requested based on allocatedMemory value (floor (* 1.2 allocatedMemory)).

resources: null

# -- Service annotations and labels

service:

annotations: {}

labels: {}

extraPorts: []

index-cache:

# -- Specifies whether memcached based index-cache should be enabled

enabled: false

# -- How long each pod must be ready for before the next one is started/restarted

minReadySeconds: 60

# -- Total number of index-cache replicas

replicas: 1

# -- Number of old ReplicaSets to retain to allow rollback (if not set, the default Kubernetes value is set to 10)

revisionHistoryLimit: null

# -- Port of the index-cache service

port: 11211

# -- Amount of memory allocated to index-cache for object storage (in MB).

allocatedMemory: 2048

# -- Maximum item index-cache for memcached (in MB).

maxItemMemory: 5

# -- Maximum number of connections allowed

connectionLimit: 16384

# -- Extra init containers for index-cache pods

initContainers: []

# -- Annotations for the index-cache pods

annotations: {}

# -- Node selector for index-cache pods

nodeSelector: {}

# -- Affinity for index-cache pods

affinity: {}

dnsConfig: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints: {}

# maxSkew: 1

# topologyKey: kubernetes.io/hostname

# whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

# -- Tolerations for index-cache pods

tolerations: []

# -- Pod Disruption Budget

podDisruptionBudget:

maxUnavailable: 1

# -- The name of the PriorityClass for index-cache pods

priorityClassName: null

# -- Labels for index-cache pods

podLabels: {}

# -- Annotations for index-cache pods

podAnnotations: {}

# -- Management policy for index-cache pods

podManagementPolicy: Parallel

# -- Grace period to allow the index-cache to shutdown before it is killed

terminationGracePeriodSeconds: 30

# -- Stateful index-cache strategy

statefulStrategy:

type: RollingUpdate

# -- Add extended options for index-cache memcached container. The format is the same as for the memcached -o/--extend flag.

# Example:

# extraExtendedOptions: 'tls,modern,track_sizes'

extraExtendedOptions: ""

# -- Additional CLI args for index-cache

extraArgs: {}

# -- Additional containers to be added to the index-cache pod.

extraContainers: []

# -- Additional volumes to be added to the index-cache pod (applies to both memcached and exporter containers).

# Example:

# extraVolumes:

# - name: extra-volume

# secret:

# secretName: extra-volume-secret

extraVolumes: []

# -- Additional volume mounts to be added to the index-cache pod (applies to both memcached and exporter containers).

# Example:

# extraVolumeMounts:

# - name: extra-volume

# mountPath: /etc/extra-volume

# readOnly: true

extraVolumeMounts: []

# -- List of additional PVCs to be created for the index-cache statefulset

volumeClaimTemplates: []

# -- Resource requests and limits for the index-cache

# By default a safe memory limit will be requested based on allocatedMemory value (floor (* 1.2 allocatedMemory)).

resources: null

# -- Service annotations and labels

service:

annotations: {}

labels: {}

extraPorts: []

metadata-cache:

# -- Specifies whether memcached based metadata-cache should be enabled

enabled: false

# -- How long each pod must be ready for before the next one is started/restarted

minReadySeconds: 60

# -- Total number of metadata-cache replicas

replicas: 1

# -- Number of old ReplicaSets to retain to allow rollback (if not set, the default Kubernetes value is set to 10)

revisionHistoryLimit: null

# -- Port of the metadata-cache service

port: 11211

# -- Amount of memory allocated to metadata-cache for object storage (in MB).

allocatedMemory: 512

# -- Maximum item metadata-cache for memcached (in MB).

maxItemMemory: 1

# -- Maximum number of connections allowed

connectionLimit: 16384

# -- Extra init containers for metadata-cache pods

initContainers: []

# -- Annotations for the metadata-cache pods

annotations: {}

# -- Node selector for metadata-cache pods

nodeSelector: {}

# -- Affinity for metadata-cache pods

affinity: {}

dnsConfig: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints: {}

# maxSkew: 1

# topologyKey: kubernetes.io/hostname

# whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

# -- Tolerations for metadata-cache pods

tolerations: []

# -- Pod Disruption Budget

podDisruptionBudget:

maxUnavailable: 1

# -- The name of the PriorityClass for metadata-cache pods

priorityClassName: null

# -- Labels for metadata-cache pods

podLabels: {}

# -- Annotations for metadata-cache pods

podAnnotations: {}

# -- Management policy for metadata-cache pods

podManagementPolicy: Parallel

# -- Grace period to allow the metadata-cache to shutdown before it is killed

terminationGracePeriodSeconds: 30

# -- Stateful metadata-cache strategy

statefulStrategy:

type: RollingUpdate

# -- Add extended options for metadata-cache memcached container. The format is the same as for the memcached -o/--extend flag.

# Example:

# extraExtendedOptions: 'tls,modern,track_sizes'

extraExtendedOptions: ""

# -- Additional CLI args for metadata-cache

extraArgs: {}

# -- Additional containers to be added to the metadata-cache pod.

extraContainers: []

# -- Additional volumes to be added to the metadata-cache pod (applies to both memcached and exporter containers).

# Example:

# extraVolumes:

# - name: extra-volume

# secret:

# secretName: extra-volume-secret

extraVolumes: []

# -- Additional volume mounts to be added to the metadata-cache pod (applies to both memcached and exporter containers).

# Example:

# extraVolumeMounts:

# - name: extra-volume

# mountPath: /etc/extra-volume

# readOnly: true

extraVolumeMounts: []

# -- List of additional PVCs to be created for the metadata-cache statefulset

volumeClaimTemplates: []

# -- Resource requests and limits for the metadata-cache

# By default a safe memory limit will be requested based on allocatedMemory value (floor (* 1.2 allocatedMemory)).

resources: null

# -- Service annotations and labels

service:

annotations: {}

labels: {}

extraPorts: []

results-cache:

# -- Specifies whether memcached based results-cache should be enabled

enabled: false

# -- How long each pod must be ready for before the next one is started/restarted

minReadySeconds: 60

# -- Total number of results-cache replicas

replicas: 1

# -- Number of old ReplicaSets to retain to allow rollback (if not set, the default Kubernetes value is set to 10)

revisionHistoryLimit: null

# -- Port of the results-cache service

port: 11211

# -- Amount of memory allocated to results-cache for object storage (in MB).

allocatedMemory: 512

# -- Maximum item results-cache for memcached (in MB).

maxItemMemory: 25

# -- Maximum number of connections allowed

connectionLimit: 16384

# -- Extra init containers for results-cache pods

initContainers: []

# -- Annotations for the results-cache pods

annotations: {}

# -- Node selector for results-cache pods

nodeSelector: {}

# -- Affinity for results-cache pods

affinity: {}

dnsConfig: {}

# -- topologySpreadConstraints allows to customize the default topologySpreadConstraints. This can be either a single dict as shown below or a slice of topologySpreadConstraints.

# labelSelector is taken from the constraint itself (if it exists) or is generated by the chart using the same selectors as for services.

topologySpreadConstraints: {}

# maxSkew: 1

# topologyKey: kubernetes.io/hostname

# whenUnsatisfiable: ScheduleAnyway

# minDomains: 1

# nodeAffinityPolicy: Honor

# nodeTaintsPolicy: Honor

# matchLabelKeys:

# - pod-template-hash

# -- Tolerations for results-cache pods

tolerations: []

# -- Pod Disruption Budget

podDisruptionBudget:

maxUnavailable: 1