# The reference configuration can be found at https://github.com/bitnami/charts/blob/master/bitnami/redis/values-production.yaml

## Global Docker image parameters
## Please, note that this will override the image parameters, including dependencies, configured to use the global value
## Current available global Docker image parameters: imageRegistry and imagePullSecrets
##
global:
  storageClass: redis-local-storage

## Bitnami Redis image version
## ref: https://hub.docker.com/r/bitnami/redis/tags/
##
image:
  repository: bitnami/redis
  tag: 6.0.9-debian-10-r38
  pullPolicy: IfNotPresent

## Cluster settings
cluster:
  enabled: true
  # With sentinel no dedicated master
  slaveCount: 3

## Use redis sentinel in the redis pod. This will disable the master and slave services and
## create one redis service with ports to the sentinel and the redis instances
sentinel:
  #Adding sentinel requires at least 3 nodes for the quorum
  enabled: True
  ## Require password authentication on the sentinel itself
  ## ref: https://redis.io/topics/sentinel
  usePassword: true
  image:
    repository: bitnami/redis-sentinel
    tag: 6.0.9-debian-10-r38
    pullPolicy: IfNotPresent
  masterSet: testmaster
  initialCheckTimeout: 5
  # quorum is round(n / 2 + 1)
  quorum: 2
  downAfterMilliseconds: 30000
  failoverTimeout: 10000
  parallelSyncs: 1
  staticID: true
  resources:
    requests:
      memory: 256Mi
      cpu: 100m

## Use password authentication
usePassword: False
## Redis password (both master and slave)
## Defaults to a random 10-character alphanumeric string if not set and usePassword is true
## ref: https://github.com/bitnami/bitnami-docker-redis#setting-the-server-password-on-first-run
##
password: "passwordredis"

## Persist data to a persistent volume (Redis Master)
persistence:
  ## A manually managed Persistent Volume and Claim
  ## Requires persistence.enabled: true
  ## If defined, PVC must be created manually before volume will be bound
  existingClaim:

##
## Redis Master parameters
##
master:
  persistence:
    enabled: true
    path: /data
    accessModes:
      - ReadWriteOnce
    size: 10Gi

##
## Redis Slave properties
##
slave:
  ## Kubernetes Spread Constraints for pod assignment
  ## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/
  ##
  # - maxSkew: 1
  #   topologyKey: node
  #   whenUnsatisfiable: DoNotSchedule
  spreadConstraints: {}

  resources:
    requests:
      memory: 256Mi
      cpu: 100m
  persistence:
    enabled: true
    path: /data
    accessModes:
      - ReadWriteOnce
    size: 10Gi

## Prometheus Exporter / Metrics
##
metrics:
  enabled: true
  image:
    repository: bitnami/redis-exporter
    tag: 1.13.1-debian-10-r32
    pullPolicy: IfNotPresent
  ## Metrics exporter pod Annotation and Labels
  podAnnotations:
    prometheus.io/scrape: "true"
    prometheus.io/port: "9121"

##
## Init containers parameters:
## volumePermissions: Change the owner of the persist volume mountpoint to RunAsUser:fsGroup
##
volumePermissions:
  enabled: false
  image:
    repository: bitnami/minideb
    tag: buster
    pullPolicy: IfNotPresent
  resources:
    requests:
      memory: 128Mi
      cpu: 100m

  ## Init container Security Context
  ## Note: the chown of the data folder is done to containerSecurityContext.runAsUser
  ## and not the below volumePermissions.securityContext.runAsUser
  ## When runAsUser is set to special value "auto", init container will try to chwon the
  ## data folder to autodetermined user&group, using commands: `id -u`:`id -G | cut -d" " -f2`
  ## "auto" is especially useful for OpenShift which has scc with dynamic userids (and 0 is not allowed).
  ## You may want to use this volumePermissions.securityContext.runAsUser="auto" in combination with
  ## podSecurityContext.enabled=false,containerSecurityContext.enabled=false
  ##
  securityContext:
    runAsUser: 0

## Redis config file
## ref: https://redis.io/topics/config
##
configmap: |-
  # Enable AOF https://redis.io/topics/persistence#append-only-file
  appendonly yes
  # Disable RDB persistence, AOF persistence already enabled.
  save ""

## Sysctl InitContainer
## used to perform sysctl operation to modify Kernel settings (needed sometimes to avoid warnings)
sysctlImage:
  enabled: false
  repository: bitnami/minideb
  tag: buster
  pullPolicy: IfNotPresent
  mountHostSys: false
  resources:
    requests:
      memory: 128Mi
      cpu: 100m

podSecurityPolicy:
  create: false

podDisruptionBudget:
  enabled: false
  minAvailable: 1
  # maxUnavailable: 1