目录
一、Helm介绍
1、三大概念
2、基本命令
二、NFS的安装和使用
1、安装NFS
2、NFS在K8s上使用
三、PV和PVC
1、定义
2、PV和PVC的生命周期
2.1、资源供应
2.2、资源绑定
2.3、资源使用
2.4、资源回收
3、创建PV
4、创建PVC
5、创建测试使用PVC的Pod
四、StorageClass
1、概念
2、动态创建NFS
2.1、创建RBAC
2.2、创建StorageClass资源
2.3、创建provisioner
2.4、创建测试的statefulset
五、安装Redis
1、安装redis
2、测试Redis
六、附录
1、nfs-provisioner-rbac.yaml
2、nfs-provisioner-deploy.yaml
3、redis value.yaml
一、Helm介绍
1、三大概念
Chart 代表着 Helm 包。它包含在 Kubernetes 集群内部运行应用程序，工具或服务所需的所有资源定义。
Repository（仓库） 是用来存放和共享 charts 的地方，供 Kubernetes 包所使用的。
Release 是运行在 Kubernetes 集群中的 chart 的实例。一个 chart 通常可以在同一个集群中安装多次。每一次安装都会创建一个新的 release。以 MySQL chart为例，如果你想在你的集群中运行两个数据库，你可以安装该chart两次。每一个数据库都会拥有它自己的 release 和 release name。
在了解了上述这些概念以后，我们就可以这样来解释 Helm：Helm 安装 charts 到 Kubernetes 集群中，每次安装都会创建一个新的 release。你可以在 Helm 的 chart repositories 中寻找新的 chart。
2、基本命令
# 列出仓库
helm repo list
#添加仓库
helm repo add bitnami https://charts.bitnami.com/bitnami
helm repo add brigade https://brigadecore.github.io/charts
#搜索仓库
helm search repo bitnami
#关键字搜索
helm search repo redis
helm search hubredis
#更新仓库
helm repo update
#删除仓库
helm repo remove brigade
#安装helm包
helm install happy-panda bitnami/wordpress
#跟踪状态
helm status happy-panda
#回滚
helm rollback happy-panda 1
#卸载一个版本
helm uninstall happy-panda
#保留历史记录
helm uninstall happy-panda --keep-history
#显示卸载记录
helm list --uninstalled
#验证格式
helm lint
#打包
helm package <n>
二、NFS的安装和使用
1、安装NFS
#安装 每个节点都安装
yum install nfs-utils -y
#启动 每个节点都执行
systemctl start nfs-server
systemctl start nfs && systemctl enable nfs
#查看版本
cat /proc/fs/nfsd/versions
#创建共享目录 在node1节点上
mkdir -p /data/nfs/{ro,rw}
#设置共享目录 在node1节点上
vim /etc/exports
#添加如下内容
/data/nfs/rw 192.168.139.0/24(rw,sync,no_subtree_check,no_root_squash)
/data/nfs/ro 192.168.139.0/24(ro,sync,no_subtree_check,no_root_squash)
#重新加载配置文件 在node1节点上
exportfs -f
#重启服务 在node1节点上
systemctl reload nfs-server
#进入ro只读目录 在node1节点上
cd /data/nfs/ro
#创建文件 在node1节点上
echo "hello nfs" > test.txt
#在master节点执行以下命令
mkdir -p /mnt/nfs/rw
mkdir -p /mnt/nfs/ro
#加载nfs服务（node1的ip）的文件到目标目录下
mount -t nfs 192.168.139.207:/data/nfs/rw /mnt/nfs/rw
mount -t nfs 192.168.139.207:/data/nfs/ro /mnt/nfs/ro
#进入到/mnt/hgfs/ro目录发现文件同步过来了，并且不支持修改
#进入/mnt/hgfs/rw 添加文件然后到node1节点 /root/data/nfs/rw 目录下查看文件
touch Readme
echo "hello nfs" >> Readme
2、NFS在K8s上使用
#在nfs所在的服务上创建目录
mkdir /root/data/nfs/rw/www/html -p
#进入路径创建文件
echo '<h1>hello world</h1>' > index.htmlapiVersion: v1
kind: Pod
metadata:
name: nfs-pod1
spec:
containers:
- name: nfs-pod1
image: nginx:1.21.6
imagePullPolicy: IfNotPresent
ports:
- name: nginx-port
containerPort: 80
protocol: TCP
volumeMounts: #容器内数据加载卷
- mountPath: /usr/share/nginx/html #容器内的目录
name: test-volume #与下面的name一致
volumes: #数据挂载卷
- name: test-volume
nfs:
path: /data/nfs/rw/www/html #nfs服务的地址路径，没有的话需要手动创建
server: 192.168.139.207 #nfs服务地址
readOnly: false #只读模式false 可读可写
restartPolicy: Always
#创建资源
kubectl create -f nfs-pod1.yaml
#查看pod
kubectl get po -o wide 
三、PV和PVC
1、定义
PV（持久卷）是对资源存储的抽象，将存储定义为一种容器应用可以使用的资源。PV由管理员穿件和配置，它与存储供应商的具体实现直接相关，共享存储通过插件式的机制进行管理，供应用访问和使用。
PVC (持久卷申领)则是用户对存储资源的一个申请。比如我的Mysql需要100个Gi的存储空间，那么PVC就会通过PV向存储供应申请100Gi的资源。然后存储供应提供这些存储空间。
2、PV和PVC的生命周期
2.1、资源供应
- 静态模式：集群管理员预先创建许多PV，在PV的定义中能够体现存储资源的特性。
- 动态模式：集群管理员无需预先创建PV，而是通过StorageClass的设置对后端存储资源进行描述，标记存储的类型和特性。用户通过PVC对存储类型进行申请，系统会自动完成PV的创建及与PVC的绑定。
2.2、资源绑定
在用户定义好PVC之后，系统会根据PVC对存储资源的请求在已存在的PV中选择满足PVC要求的PV，找到后绑定之后，应用就可以使用这个PVC了。PV与PVC一旦绑定完成，PVC就会独占这个PV了，绑定关系是一对一的。如果资源供应使用的是动态模式，则系统在为PVC找到合适的StorageClass之后，将自动创建一个PV并完成与PVC的绑定。
2.3、资源使用
Pod需要使用存储资源时，需要在Volume的定义中引用PVC类型的存储卷，将PVC挂载到容器内的某个路径下使用。Pod在挂载PVC后，就能使用存储资源了，同一个PVC还可以被多个Pod同时挂载使用。PV、PVC相对于Pod是独立管理的资源，可以单独删除，在删除的时候会检测资源是否正在使用，如果正在使用则删除操作会延迟，直到没被使用才会执行删除。这个机制被称为存储对象的保护机制。
2.4、资源回收
用户在使用完存储资源后，可以删除PVC。与该PVC绑定的PV会被标记为“已释放”状态，但还不能立即与其他PVC 进行绑定，只有清除这些数据之后该PV才能被再次使用。有三种回收策略
- Retain：保留数据。Retain策略表示在删除PVC之后，与之绑定的PV不会被删除，仅标记为已释放（released）状态。PV中的数据仍然存在在，在清空之前不能被其他PVC使用，需要手动清除数据后才能使用。
- Delete:删除数据 。Delete表示自动删除PV资源对象和相关的后端存储。
- Recycle(弃用) ，该策略已被弃用，原理相当于执行rm-rf。
3、创建PV
apiVersion: v1
kind: PersistentVolume #资源类型
metadata:
name: pv01 #pv名字
spec: #描述
capacity:
storage: 5Gi #容量大小
volumeMode: Filesystem #存储类型为文件系统
accessModes:
# - ReadOnlyMany #可以被多个Node挂载，只读
- ReadWriteMany #可以被多个Node挂载 读写
# - ReadWriteOnce #只能被单个Node挂载
persistentVolumeReclaimPolicy: Retain #资源回收策略
storageClassName: slow #类名
mountOptions:
- nfsvers=4.2
nfs:
path: /data/nfs/rw/test-pv #nfs路径
server: 192.168.139.207 #nfs服务地址
#创建
kubectl create -f pv-demo.yaml
#查看
kubectl get pv 
PV在生命周期有4个阶段
- Available：可用状态，还未与PVC绑定。
- Bound:已与某个PVC绑定。
- Released：与之绑定的PVC已被删除，但未完成资源回收，不能被其他PVC使用。
- Failed：自动资源回收失败。
4、创建PVC
apiVersion: v1
kind: PersistentVolumeClaim #资源类型 pvc
metadata:
name: pvc01 #pvc名字
spec: #描述
accessModes: #与Pv保持一致
- ReadOnlyMany #可以被多个Node挂载，只读
- ReadWriteMany #可以被多个Node挂载 读写
- ReadWriteOnce #只能被单个Node挂载
volumeMode: Filesystem
storageClassName: slow #类名 与PV保持一致才会绑定上
resources:
requests:
storage: 100Mi
# selector: #支持标签匹配
# matchLabels:
# release: "true" #创建资源
kubectl create -f pvc-demo.yaml
#查看，状态显示绑定
kubectl get pvc 
5、创建测试使用PVC的Pod
apiVersion: v1
kind: Pod
metadata:
name: test-pvc-pod #名称
spec:
containers:
- name: test-pvc-pod
image: nginx:1.21.6
imagePullPolicy: IfNotPresent
ports:
- name: test-pvc-pod
containerPort: 80
protocol: TCP
volumeMounts: #数据加载卷
- mountPath: /usr/share/nginx/html #容器内目录
name: test-volume #名称，与下面一致
volumes: #数据加载卷，从pvc加载数据
- name: test-volume #与spec.containers.volumeMounts[].name一致
persistentVolumeClaim: # 关联pvc
claimName: pvc01 # 与创建的PVC名称相同。填写使用的pvc名称
restartPolicy: Always
#创建资源
kubectl create -f test-pvc-pod.yaml
#查看资源
kubectl get po -o wide
#进入node1节点在/data/nfs/rw/test-pv
echo "hello" > index.html
#访问pod创建的nginx
curl 10.244.1.171
四、StorageClass
1、概念
每个 StorageClass 都包含 制备器（Provisioner）、Parameters(这是服务提供商特定的) 和 回收策略（Reclaim Policy ）字段， 这些字段会在 StorageClass 需要动态制备 PV（PersistentVolume） 以满足 PVC (PersistentVolumeClaim ) 时使用到。StorageClass的动态创建可以避免频繁的手动创建PV和PVC。
存储制备器（Provisioner）：存储制备器描述存储资源的提供者，用于提供具体的PV资源。、
资源回收策略（Reclain Policy）:资源回收策略，可选值为Delete(删除)和Retain（保留），默认为Delete。
2、动态创建NFS
2.1、创建RBAC
#创建目录
mkdir storageclass
#下载文件 重命名 下载不下来的见附录
wget -O nfs-provisioner-rbac.yaml https://raw.githubusercontent.com/kubernetes-sigs/nfs-subdir-external-provisioner/master/deploy/rbac.yaml
#创建资源
kubectl apply -f nfs-provisioner-rbac.yaml
2.2、创建StorageClass资源
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: manager-nfs-storage
provisioner: fuseim.pri/ifs
parameters:
archiveOnDelete: "false" #是否存档，false表示不存档会删除oldPath，true存档，会重命名路径
reclaimPolicy: Retain #回收策略
volumeBindingMode: Immediate # Immediate模式表示一旦创建了 PersistentVolumeClaim 也就完成了卷绑定和动态制备;WaitForFirstConsumer模式将延迟 PersistentVolume 的绑定和制备，直到使用该 PersistentVolumeClaim 的 Pod 被创建
#创建资源
kubectl create -f nfs-storage-class.yaml
#查看资源
kubectl get storageclass
kubectl get sc 
2.3、创建provisioner
#下载资源
wget -O nfs-provisioner-deploy.yaml https://raw.githubusercontent.com/kubernetes-sigs/nfs-subdir-external-provisioner/master/deploy/deployment.yaml
#根据需要修改资源（镜像地址），然后创建，完整文件见附录
kubectl create -f nfs-provisioner-deploy.yaml
#查看资源
kubectl get deploy
2.4、创建测试的statefulset
apiVersion: v1
kind: Service
metadata:
name: nginx-sc
labels:
app: nginx-sc
spec:
selector:
app: nginx-sc
ports:
- protocol: TCP
port: 80
name: web
type: NodePort
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: nginx-sc
spec:
replicas: 1
selector:
matchLabels:
app: nginx-sc
serviceName: nginx-sc
template:
metadata:
labels:
app: nginx-sc
spec:
containers:
- name: nginx-sc
image: nginx:1.21.6
imagePullPolicy: IfNotPresent
volumeMounts:
- mountPath: /usr/share/nginx/html
name: nginx-sc-test-pvc
volumeClaimTemplates: #加载pvc的模板
- metadata:
name: nginx-sc-test-pvc #加载的pvc的名字
spec:
storageClassName: manager-nfs-storage #同nfs-storage-class.yaml文件中metadata.name保持一致
accessModes:
- ReadWriteMany
resources:
requests:
storage: 1Gi
五、安装Redis
1、安装redis
#搜索仓库
helm search repo redis
#显示配置的说明
helm show readme bitnami/redis
#拉取到本地,https://artifacthub.io/ 所有chart仓库地址,可以在这看到所有的版本，后面可以指定CHART VERSION版本号
helm pull bitnami/redis --version 20.1.0
#创建一个redis文件夹。将安装包移动到该文件并解压，修改后的文件见附录
tar -xf redis-20.1.0.tgz
#创建命名空间
kubectl create ns redis-test
#安装redis，中间有个点 . 语法为 helm install <自己取的名字> . -n <namespace>
helm install redis . -n redis-test
#查看资源
kubectl get all -n redis-test
#版本更新
helm upgrade redis . -n redis-test
#查看版本
helm history redis -n redis-test
#回滚版本 1为指定版本号，不写则默认回滚到上一个版本
helm rollback redis 1 -n redis-test
2、测试Redis
六、附录
1、nfs-provisioner-rbac.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
name: nfs-client-provisioner
# replace with namespace where provisioner is deployed
namespace: default
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: nfs-client-provisioner-runner
rules:
- apiGroups: [""]
resources: ["nodes"]
verbs: ["get", "list", "watch"]
- apiGroups: [""]
resources: ["persistentvolumes"]
verbs: ["get", "list", "watch", "create", "delete"]
- apiGroups: [""]
resources: ["persistentvolumeclaims"]
verbs: ["get", "list", "watch", "update"]
- apiGroups: ["storage.k8s.io"]
resources: ["storageclasses"]
verbs: ["get", "list", "watch"]
- apiGroups: [""]
resources: ["events"]
verbs: ["create", "update", "patch"]
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: run-nfs-client-provisioner
subjects:
- kind: ServiceAccount
name: nfs-client-provisioner
# replace with namespace where provisioner is deployed
namespace: default
roleRef:
kind: ClusterRole
name: nfs-client-provisioner-runner
apiGroup: rbac.authorization.k8s.io
---
kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: leader-locking-nfs-client-provisioner
# replace with namespace where provisioner is deployed
namespace: default
rules:
- apiGroups: [""]
resources: ["endpoints"]
verbs: ["get", "list", "watch", "create", "update", "patch"]
---
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: leader-locking-nfs-client-provisioner
# replace with namespace where provisioner is deployed
namespace: default
subjects:
- kind: ServiceAccount
name: nfs-client-provisioner
# replace with namespace where provisioner is deployed
namespace: default
roleRef:
kind: Role
name: leader-locking-nfs-client-provisioner
apiGroup: rbac.authorization.k8s.io2、nfs-provisioner-deploy.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: nfs-client-provisioner
labels:
app: nfs-client-provisioner
# replace with namespace where provisioner is deployed
namespace: default #命名空间
spec:
replicas: 1 #副本数
strategy: #deploy策略
type: Recreate
selector:
matchLabels:
app: nfs-client-provisioner
template:
metadata:
labels:
app: nfs-client-provisioner
spec:
serviceAccountName: nfs-client-provisioner #对应rbac中的账户
containers:
- name: nfs-client-provisioner
image: registry.cn-beijing.aliyuncs.com/pylixm/nfs-subdir-external-provisioner:v4.0.0 #这里镜像改为阿里镜像
volumeMounts: #容器内数据加载
- name: nfs-client-root #跟spec.template.spec.volumes.name保持一致
mountPath: /persistentvolumes #容器内路径
env:
- name: PROVISIONER_NAME #provisioner的名字
value: fuseim.pri/ifs #对应nfs-storage-class.yaml文件下的provisioner的值
- name: NFS_SERVER
value: 192.168.139.207 #nfs服务器地址
- name: NFS_PATH
value: /data/nfs/rw #路径
volumes:
- name: nfs-client-root
nfs:
server: 192.168.139.207
path: /data/nfs/rw #路径
3、redis value.yaml
# Copyright Broadcom, Inc. All Rights Reserved.
# SPDX-License-Identifier: APACHE-2.0
## @section Global parameters
## 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, imagePullSecrets and storageClass
##
## @param global.imageRegistry Global Docker image registry
## @param global.imagePullSecrets Global Docker registry secret names as an array
## @param global.defaultStorageClass Global default StorageClass for Persistent Volume(s)
## @param global.storageClass DEPRECATED: use global.defaultStorageClass instead
## @param global.redis.password Global Redis® password (overrides `auth.password`)
##
global:
imageRegistry: ""
## E.g.
## imagePullSecrets:
## - myRegistryKeySecretName
##
imagePullSecrets: []
defaultStorageClass: ""
storageClass: "manager-nfs-storage" #配置创建的storageclass
redis:
password: "123456" #redis的密码，默认是空值
## Compatibility adaptations for Kubernetes platforms
##
compatibility:
## Compatibility adaptations for Openshift
##
openshift:
## @param global.compatibility.openshift.adaptSecurityContext Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation)
##
adaptSecurityContext: auto
## @section Common parameters
##
## @param kubeVersion Override Kubernetes version
##
kubeVersion: ""
## @param nameOverride String to partially override common.names.fullname
##
nameOverride: ""
## @param fullnameOverride String to fully override common.names.fullname
##
fullnameOverride: ""
## @param namespaceOverride String to fully override common.names.namespace
##
namespaceOverride: ""
## @param commonLabels Labels to add to all deployed objects
##
commonLabels: {}
## @param commonAnnotations Annotations to add to all deployed objects
##
commonAnnotations: {}
## @param secretAnnotations Annotations to add to secret
##
secretAnnotations: {}
## @param clusterDomain Kubernetes cluster domain name
##
clusterDomain: cluster.local
## @param extraDeploy Array of extra objects to deploy with the release
##
extraDeploy: []
## @param useHostnames Use hostnames internally when announcing replication. If false, the hostname will be resolved to an IP address
##
useHostnames: true
## @param nameResolutionThreshold Failure threshold for internal hostnames resolution
##
nameResolutionThreshold: 5
## @param nameResolutionTimeout Timeout seconds between probes for internal hostnames resolution
##
nameResolutionTimeout: 5
## Enable diagnostic mode in the deployment
##
diagnosticMode:
## @param diagnosticMode.enabled Enable diagnostic mode (all probes will be disabled and the command will be overridden)
##
enabled: false
## @param diagnosticMode.command Command to override all containers in the deployment
##
command:
- sleep
## @param diagnosticMode.args Args to override all containers in the deployment
##
args:
- infinity
## @section Redis® Image parameters
##
## Bitnami Redis® image
## ref: https://hub.docker.com/r/bitnami/redis/tags/
## @param image.registry [default: REGISTRY_NAME] Redis® image registry
## @param image.repository [default: REPOSITORY_NAME/redis] Redis® image repository
## @skip image.tag Redis® image tag (immutable tags are recommended)
## @param image.digest Redis® image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag
## @param image.pullPolicy Redis® image pull policy
## @param image.pullSecrets Redis® image pull secrets
## @param image.debug Enable image debug mode
##
image:
registry: docker.io
repository: bitnami/redis
tag: 7.4.0-debian-12-r2
digest: ""
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: https://kubernetes.io/docs/concepts/containers/images/#pre-pulled-images
##
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/
## e.g:
## pullSecrets:
## - myRegistryKeySecretName
##
pullSecrets: []
## Enable debug mode
##
debug: false
## @section Redis® common configuration parameters
## https://github.com/bitnami/containers/tree/main/bitnami/redis#configuration
##
## @param architecture Redis® architecture. Allowed values: `standalone` or `replication`
##
architecture: replication #主从复制
## Redis® Authentication parameters
## ref: https://github.com/bitnami/containers/tree/main/bitnami/redis#setting-the-server-password-on-first-run
##
auth:
## @param auth.enabled Enable password authentication
##
enabled: true
## @param auth.sentinel Enable password authentication on sentinels too
##
sentinel: true #哨兵
## @param auth.password Redis® password
## Defaults to a random 10-character alphanumeric string if not set
##
password: ""
## @param auth.existingSecret The name of an existing secret with Redis® credentials
## NOTE: When it's set, the previous `auth.password` parameter is ignored
##
existingSecret: ""
## @param auth.existingSecretPasswordKey Password key to be retrieved from existing secret
## NOTE: ignored unless `auth.existingSecret` parameter is set
##
existingSecretPasswordKey: ""
## @param auth.usePasswordFiles Mount credentials as files instead of using an environment variable
##
usePasswordFiles: false
## @param auth.usePasswordFileFromSecret Mount password file from secret
##
usePasswordFileFromSecret: true
## @param commonConfiguration [string] Common configuration to be added into the ConfigMap
## ref: https://redis.io/topics/config
##
commonConfiguration: |-
# Enable AOF https://redis.io/topics/persistence#append-only-file
appendonly yes
# Disable RDB persistence, AOF persistence already enabled.
save ""
## @param existingConfigmap The name of an existing ConfigMap with your custom configuration for Redis® nodes
##
existingConfigmap: ""
## @section Redis® master configuration parameters
##
master:
## @param master.count Number of Redis® master instances to deploy (experimental, requires additional configuration)
##
count: 1
## @param master.revisionHistoryLimit The number of old history to retain to allow rollback
## NOTE: Explicitly setting this field to 0, will result in cleaning up all the history, breaking ability to rollback
revisionHistoryLimit: 10
## @param master.configuration Configuration for Redis® master nodes
## ref: https://redis.io/topics/config
##
configuration: ""
## @param master.disableCommands Array with Redis® commands to disable on master nodes
## Commands will be completely disabled by renaming each to an empty string.
## ref: https://redis.io/topics/security#disabling-of-specific-commands
##
disableCommands:
- FLUSHDB
- FLUSHALL
## @param master.command Override default container command (useful when using custom images)
##
command: []
## @param master.args Override default container args (useful when using custom images)
##
args: []
## @param master.enableServiceLinks Whether information about services should be injected into pod's environment variable
##
enableServiceLinks: true
## @param master.preExecCmds Additional commands to run prior to starting Redis® master
##
preExecCmds: []
## @param master.extraFlags Array with additional command line flags for Redis® master
## e.g:
## extraFlags:
## - "--maxmemory-policy volatile-ttl"
## - "--repl-backlog-size 1024mb"
##
extraFlags: []
## @param master.extraEnvVars Array with extra environment variables to add to Redis® master nodes
## e.g:
## extraEnvVars:
## - name: FOO
## value: "bar"
##
extraEnvVars: []
## @param master.extraEnvVarsCM Name of existing ConfigMap containing extra env vars for Redis® master nodes
##
extraEnvVarsCM: ""
## @param master.extraEnvVarsSecret Name of existing Secret containing extra env vars for Redis® master nodes
##
extraEnvVarsSecret: ""
## @param master.containerPorts.redis Container port to open on Redis® master nodes
##
containerPorts:
redis: 6379
## Configure extra options for Redis® containers' liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes
## @param master.startupProbe.enabled Enable startupProbe on Redis® master nodes
## @param master.startupProbe.initialDelaySeconds Initial delay seconds for startupProbe
## @param master.startupProbe.periodSeconds Period seconds for startupProbe
## @param master.startupProbe.timeoutSeconds Timeout seconds for startupProbe
## @param master.startupProbe.failureThreshold Failure threshold for startupProbe
## @param master.startupProbe.successThreshold Success threshold for startupProbe
##
startupProbe:
enabled: false
initialDelaySeconds: 20
periodSeconds: 5
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 5
## @param master.livenessProbe.enabled Enable livenessProbe on Redis® master nodes
## @param master.livenessProbe.initialDelaySeconds Initial delay seconds for livenessProbe
## @param master.livenessProbe.periodSeconds Period seconds for livenessProbe
## @param master.livenessProbe.timeoutSeconds Timeout seconds for livenessProbe
## @param master.livenessProbe.failureThreshold Failure threshold for livenessProbe
## @param master.livenessProbe.successThreshold Success threshold for livenessProbe
##
livenessProbe:
enabled: true
initialDelaySeconds: 20
periodSeconds: 5
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 5
## @param master.readinessProbe.enabled Enable readinessProbe on Redis® master nodes
## @param master.readinessProbe.initialDelaySeconds Initial delay seconds for readinessProbe
## @param master.readinessProbe.periodSeconds Period seconds for readinessProbe
## @param master.readinessProbe.timeoutSeconds Timeout seconds for readinessProbe
## @param master.readinessProbe.failureThreshold Failure threshold for readinessProbe
## @param master.readinessProbe.successThreshold Success threshold for readinessProbe
##
readinessProbe:
enabled: true
initialDelaySeconds: 20
periodSeconds: 5
timeoutSeconds: 1
successThreshold: 1
failureThreshold: 5
## @param master.customStartupProbe Custom startupProbe that overrides the default one
##
customStartupProbe: {}
## @param master.customLivenessProbe Custom livenessProbe that overrides the default one
##
customLivenessProbe: {}
## @param master.customReadinessProbe Custom readinessProbe that overrides the default one
##
customReadinessProbe: {}
## Redis® master resource requests and limits
## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
## @param master.resourcesPreset Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if master.resources is set (master.resources is recommended for production).
## More information: https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15
##
resourcesPreset: "nano"
## @param master.resources Set container requests and limits for different resources like CPU or memory (essential for production workloads)
## Example:
## resources:
## requests:
## cpu: 2
## memory: 512Mi
## limits:
## cpu: 3
## memory: 1024Mi
##
resources: {}
## Configure Pods Security Context
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
## @param master.podSecurityContext.enabled Enabled Redis® master pods' Security Context
## @param master.podSecurityContext.fsGroupChangePolicy Set filesystem group change policy
## @param master.podSecurityContext.sysctls Set kernel settings using the sysctl interface
## @param master.podSecurityContext.supplementalGroups Set filesystem extra groups
## @param master.podSecurityContext.fsGroup Set Redis® master pod's Security Context fsGroup
##
podSecurityContext:
enabled: true
fsGroupChangePolicy: Always
sysctls: []
supplementalGroups: []
fsGroup: 1001
## Configure Container Security Context
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
## @param master.containerSecurityContext.enabled Enabled Redis® master containers' Security Context
## @param master.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container
## @param master.containerSecurityContext.runAsUser Set Redis® master containers' Security Context runAsUser
## @param master.containerSecurityContext.runAsGroup Set Redis® master containers' Security Context runAsGroup
## @param master.containerSecurityContext.runAsNonRoot Set Redis® master containers' Security Context runAsNonRoot
## @param master.containerSecurityContext.allowPrivilegeEscalation Is it possible to escalate Redis® pod(s) privileges
## @param master.containerSecurityContext.readOnlyRootFilesystem Set container's Security Context read-only root filesystem
## @param master.containerSecurityContext.seccompProfile.type Set Redis® master containers' Security Context seccompProfile
## @param master.containerSecurityContext.capabilities.drop Set Redis® master containers' Security Context capabilities to drop
##
containerSecurityContext:
enabled: true
seLinuxOptions: {}
runAsUser: 1001
runAsGroup: 1001
runAsNonRoot: true
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
seccompProfile:
type: RuntimeDefault
capabilities:
drop: ["ALL"]
## @param master.kind Use either Deployment, StatefulSet (default) or DaemonSet
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/
##
kind: StatefulSet
## @param master.schedulerName Alternate scheduler for Redis® master pods
## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
##
schedulerName: ""
## @param master.updateStrategy.type Redis® master statefulset strategy type
## @skip master.updateStrategy.rollingUpdate
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#update-strategies
##
updateStrategy:
## StrategyType
## Can be set to RollingUpdate, OnDelete (statefulset), Recreate (deployment)
##
type: RollingUpdate
## @param master.minReadySeconds How many seconds a pod needs to be ready before killing the next, during update
##
minReadySeconds: 0
## @param master.priorityClassName Redis® master pods' priorityClassName
##
priorityClassName: ""
## @param master.automountServiceAccountToken Mount Service Account token in pod
##
automountServiceAccountToken: false
## @param master.hostAliases Redis® master pods host aliases
## https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/
##
hostAliases: []
## @param master.podLabels Extra labels for Redis® master pods
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
##
podLabels: {}
## @param master.podAnnotations Annotations for Redis® master pods
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/
##
podAnnotations: {}
## @param master.shareProcessNamespace Share a single process namespace between all of the containers in Redis® master pods
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/
##
shareProcessNamespace: false
## @param master.podAffinityPreset Pod affinity preset. Ignored if `master.affinity` is set. Allowed values: `soft` or `hard`
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity
##
podAffinityPreset: ""
## @param master.podAntiAffinityPreset Pod anti-affinity preset. Ignored if `master.affinity` is set. Allowed values: `soft` or `hard`
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity
##
podAntiAffinityPreset: soft
## Node master.affinity preset
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity
##
nodeAffinityPreset:
## @param master.nodeAffinityPreset.type Node affinity preset type. Ignored if `master.affinity` is set. Allowed values: `soft` or `hard`
##
type: ""
## @param master.nodeAffinityPreset.key Node label key to match. Ignored if `master.affinity` is set
##
key: ""
## @param master.nodeAffinityPreset.values Node label values to match. Ignored if `master.affinity` is set
## E.g.
## values:
## - e2e-az1
## - e2e-az2
##
values: []
## @param master.affinity Affinity for Redis® master pods assignment
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
## NOTE: `master.podAffinityPreset`, `master.podAntiAffinityPreset`, and `master.nodeAffinityPreset` will be ignored when it's set
##
affinity: {}
## @param master.nodeSelector Node labels for Redis® master pods assignment
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/
##
nodeSelector: {}
## @param master.tolerations Tolerations for Redis® master pods assignment
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
##
tolerations: []
## @param master.topologySpreadConstraints Spread Constraints for Redis® master pod assignment
## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/
## E.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: node
## whenUnsatisfiable: DoNotSchedule
##
topologySpreadConstraints: []
## @param master.dnsPolicy DNS Policy for Redis® master pod
## ref: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/
## E.g.
## dnsPolicy: ClusterFirst
##
dnsPolicy: ""
## @param master.dnsConfig DNS Configuration for Redis® master pod
## ref: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/
## E.g.
## dnsConfig:
## options:
## - name: ndots
## value: "4"
## - name: single-request-reopen
##
dnsConfig: {}
## @param master.lifecycleHooks for the Redis® master container(s) to automate configuration before or after startup
##
lifecycleHooks: {}
## @param master.extraVolumes Optionally specify extra list of additional volumes for the Redis® master pod(s)
##
extraVolumes: []
## @param master.extraVolumeMounts Optionally specify extra list of additional volumeMounts for the Redis® master container(s)
##
extraVolumeMounts: []
## @param master.sidecars Add additional sidecar containers to the Redis® master pod(s)
## e.g:
## sidecars:
## - name: your-image-name
## image: your-image
## imagePullPolicy: Always
## ports:
## - name: portname
## containerPort: 1234
##
sidecars: []
## @param master.initContainers Add additional init containers to the Redis® master pod(s)
## ref: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
## e.g:
## initContainers:
## - name: your-image-name
## image: your-image
## imagePullPolicy: Always
## command: ['sh', '-c', 'echo "hello world"']
##
initContainers: []
## Persistence parameters
## ref: https://kubernetes.io/docs/concepts/storage/persistent-volumes/
##
persistence:
## @param master.persistence.enabled Enable persistence on Redis® master nodes using Persistent Volume Claims
##
enabled: true
## @param master.persistence.medium Provide a medium for `emptyDir` volumes.
##
medium: ""
## @param master.persistence.sizeLimit Set this to enable a size limit for `emptyDir` volumes.
##
sizeLimit: ""
## @param master.persistence.path The path the volume will be mounted at on Redis® master containers
## NOTE: Useful when using different Redis® images
##
path: /data
## @param master.persistence.subPath The subdirectory of the volume to mount on Redis® master containers
## NOTE: Useful in dev environments
##
subPath: ""
## @param master.persistence.subPathExpr Used to construct the subPath subdirectory of the volume to mount on Redis® master containers
##
subPathExpr: ""
## @param master.persistence.storageClass 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: ""
## @param master.persistence.accessModes Persistent Volume access modes
##
accessModes:
- ReadWriteOnce
## @param master.persistence.size Persistent Volume size
##
size: 1Gi #主节点存储大小
## @param master.persistence.annotations Additional custom annotations for the PVC
##
annotations: {}
## @param master.persistence.labels Additional custom labels for the PVC
##
labels: {}
## @param master.persistence.selector Additional labels to match for the PVC
## e.g:
## selector:
## matchLabels:
## app: my-app
##
selector: {}
## @param master.persistence.dataSource Custom PVC data source
##
dataSource: {}
## @param master.persistence.existingClaim Use a existing PVC which must be created manually before bound
## NOTE: requires master.persistence.enabled: true
##
existingClaim: ""
## persistentVolumeClaimRetentionPolicy
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#persistentvolumeclaim-retention
## @param master.persistentVolumeClaimRetentionPolicy.enabled Controls if and how PVCs are deleted during the lifecycle of a StatefulSet
## @param master.persistentVolumeClaimRetentionPolicy.whenScaled Volume retention behavior when the replica count of the StatefulSet is reduced
## @param master.persistentVolumeClaimRetentionPolicy.whenDeleted Volume retention behavior that applies when the StatefulSet is deleted
##
persistentVolumeClaimRetentionPolicy:
enabled: false
whenScaled: Retain
whenDeleted: Retain
## Redis® master service parameters
##
service:
## @param master.service.type Redis® master service type
##
type: NodePort #默认为ClusterIP，这里我们改为NodePort,方便外面访问
## @param master.service.portNames.redis Redis® master service port name
##
portNames:
redis: "tcp-redis"
## @param master.service.ports.redis Redis® master service port
##
ports:
redis: 6379
## @param master.service.nodePorts.redis Node port for Redis® master
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
## NOTE: choose port between <30000-32767>
##
nodePorts:
redis: "" #端口范围为30000-32767
## @param master.service.externalTrafficPolicy Redis® master service external traffic policy
## ref: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
##
externalTrafficPolicy: Cluster
## @param master.service.extraPorts Extra ports to expose (normally used with the `sidecar` value)
##
extraPorts: []
## @param master.service.internalTrafficPolicy Redis® master service internal traffic policy (requires Kubernetes v1.22 or greater to be usable)
## ref: https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/
##
internalTrafficPolicy: Cluster
## @param master.service.clusterIP Redis® master service Cluster IP
##
clusterIP: ""
## @param master.service.loadBalancerIP Redis® master service Load Balancer IP
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
##
loadBalancerIP: ""
## @param master.service.loadBalancerClass master service Load Balancer class if service type is `LoadBalancer` (optional, cloud specific)
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-loadbalancer
##
loadBalancerClass: ""
## @param master.service.loadBalancerSourceRanges Redis® master service Load Balancer sources
## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service
## e.g.
## loadBalancerSourceRanges:
## - 10.10.10.0/24
##
loadBalancerSourceRanges: []
## @param master.service.externalIPs Redis® master service External IPs
## https://kubernetes.io/docs/concepts/services-networking/service/#external-ips
## e.g.
## externalIPs:
## - 10.10.10.1
## - 201.22.30.1
##
externalIPs: []
## @param master.service.annotations Additional custom annotations for Redis® master service
##
annotations: {}
## @param master.service.sessionAffinity Session Affinity for Kubernetes service, can be "None" or "ClientIP"
## If "ClientIP", consecutive client requests will be directed to the same Pod
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
##
sessionAffinity: None
## @param master.service.sessionAffinityConfig Additional settings for the sessionAffinity
## sessionAffinityConfig:
## clientIP:
## timeoutSeconds: 300
##
sessionAffinityConfig: {}
## @param master.terminationGracePeriodSeconds Integer setting the termination grace period for the redis-master pods
##
terminationGracePeriodSeconds: 30
## ServiceAccount configuration
##
serviceAccount:
## @param master.serviceAccount.create Specifies whether a ServiceAccount should be created
##
create: true
## @param master.serviceAccount.name The name of the ServiceAccount to use.
## If not set and create is true, a name is generated using the common.names.fullname template
##
name: ""
## @param master.serviceAccount.automountServiceAccountToken Whether to auto mount the service account token
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#use-the-default-service-account-to-access-the-api-server
##
automountServiceAccountToken: false
## @param master.serviceAccount.annotations Additional custom annotations for the ServiceAccount
##
annotations: {}
## Pod Disruption Budget configuration
## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb
## @param master.pdb.create Enable/disable a Pod Disruption Budget creation
## @param master.pdb.minAvailable [object] Minimum number/percentage of pods that should remain scheduled
## @param master.pdb.maxUnavailable [object] Maximum number/percentage of pods that may be made unavailable. Defaults to `1` if both `master.pdb.minAvailable` and `master.pdb.maxUnavailable` are empty.
##
pdb:
create: true
minAvailable: ""
maxUnavailable: ""
## @section Redis® replicas configuration parameters
##
replica:
## @param replica.kind Use either DaemonSet or StatefulSet (default)
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/
##
kind: StatefulSet
## @param replica.replicaCount Number of Redis® replicas to deploy
##
replicaCount: 3
## @param replica.revisionHistoryLimit The number of old history to retain to allow rollback
## NOTE: Explicitly setting this field to 0, will result in cleaning up all the history, breaking ability to rollback
revisionHistoryLimit: 10
## @param replica.configuration Configuration for Redis® replicas nodes
## ref: https://redis.io/topics/config
##
configuration: ""
## @param replica.disableCommands Array with Redis® commands to disable on replicas nodes
## Commands will be completely disabled by renaming each to an empty string.
## ref: https://redis.io/topics/security#disabling-of-specific-commands
##
disableCommands:
- FLUSHDB
- FLUSHALL
## @param replica.command Override default container command (useful when using custom images)
##
command: []
## @param replica.args Override default container args (useful when using custom images)
##
args: []
## @param replica.enableServiceLinks Whether information about services should be injected into pod's environment variable
##
enableServiceLinks: true
## @param replica.preExecCmds Additional commands to run prior to starting Redis® replicas
##
preExecCmds: []
## @param replica.extraFlags Array with additional command line flags for Redis® replicas
## e.g:
## extraFlags:
## - "--maxmemory-policy volatile-ttl"
## - "--repl-backlog-size 1024mb"
##
extraFlags: []
## @param replica.extraEnvVars Array with extra environment variables to add to Redis® replicas nodes
## e.g:
## extraEnvVars:
## - name: FOO
## value: "bar"
##
extraEnvVars: []
## @param replica.extraEnvVarsCM Name of existing ConfigMap containing extra env vars for Redis® replicas nodes
##
extraEnvVarsCM: ""
## @param replica.extraEnvVarsSecret Name of existing Secret containing extra env vars for Redis® replicas nodes
##
extraEnvVarsSecret: ""
## @param replica.externalMaster.enabled Use external master for bootstrapping
## @param replica.externalMaster.host External master host to bootstrap from
## @param replica.externalMaster.port Port for Redis service external master host
##
externalMaster:
enabled: false
host: ""
port: 6379
## @param replica.containerPorts.redis Container port to open on Redis® replicas nodes
##
containerPorts:
redis: 6379
## Configure extra options for Redis® containers' liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes
## @param replica.startupProbe.enabled Enable startupProbe on Redis® replicas nodes
## @param replica.startupProbe.initialDelaySeconds Initial delay seconds for startupProbe
## @param replica.startupProbe.periodSeconds Period seconds for startupProbe
## @param replica.startupProbe.timeoutSeconds Timeout seconds for startupProbe
## @param replica.startupProbe.failureThreshold Failure threshold for startupProbe
## @param replica.startupProbe.successThreshold Success threshold for startupProbe
##
startupProbe:
enabled: true
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 22
## @param replica.livenessProbe.enabled Enable livenessProbe on Redis® replicas nodes
## @param replica.livenessProbe.initialDelaySeconds Initial delay seconds for livenessProbe
## @param replica.livenessProbe.periodSeconds Period seconds for livenessProbe
## @param replica.livenessProbe.timeoutSeconds Timeout seconds for livenessProbe
## @param replica.livenessProbe.failureThreshold Failure threshold for livenessProbe
## @param replica.livenessProbe.successThreshold Success threshold for livenessProbe
##
livenessProbe:
enabled: true
initialDelaySeconds: 20
periodSeconds: 5
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 5
## @param replica.readinessProbe.enabled Enable readinessProbe on Redis® replicas nodes
## @param replica.readinessProbe.initialDelaySeconds Initial delay seconds for readinessProbe
## @param replica.readinessProbe.periodSeconds Period seconds for readinessProbe
## @param replica.readinessProbe.timeoutSeconds Timeout seconds for readinessProbe
## @param replica.readinessProbe.failureThreshold Failure threshold for readinessProbe
## @param replica.readinessProbe.successThreshold Success threshold for readinessProbe
##
readinessProbe:
enabled: true
initialDelaySeconds: 20
periodSeconds: 5
timeoutSeconds: 1
successThreshold: 1
failureThreshold: 5
## @param replica.customStartupProbe Custom startupProbe that overrides the default one
##
customStartupProbe: {}
## @param replica.customLivenessProbe Custom livenessProbe that overrides the default one
##
customLivenessProbe: {}
## @param replica.customReadinessProbe Custom readinessProbe that overrides the default one
##
customReadinessProbe: {}
## Redis® replicas resource requests and limits
## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
## @param replica.resourcesPreset Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if replica.resources is set (replica.resources is recommended for production).
## More information: https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15
##
resourcesPreset: "nano"
## @param replica.resources Set container requests and limits for different resources like CPU or memory (essential for production workloads)
## Example:
## resources:
## requests:
## cpu: 2
## memory: 512Mi
## limits:
## cpu: 3
## memory: 1024Mi
##
resources: {}
## Configure Pods Security Context
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
## @param replica.podSecurityContext.enabled Enabled Redis® replicas pods' Security Context
## @param replica.podSecurityContext.fsGroupChangePolicy Set filesystem group change policy
## @param replica.podSecurityContext.sysctls Set kernel settings using the sysctl interface
## @param replica.podSecurityContext.supplementalGroups Set filesystem extra groups
## @param replica.podSecurityContext.fsGroup Set Redis® replicas pod's Security Context fsGroup
##
podSecurityContext:
enabled: true
fsGroupChangePolicy: Always
sysctls: []
supplementalGroups: []
fsGroup: 1001
## Configure Container Security Context
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
## @param replica.containerSecurityContext.enabled Enabled Redis® replicas containers' Security Context
## @param replica.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container
## @param replica.containerSecurityContext.runAsUser Set Redis® replicas containers' Security Context runAsUser
## @param replica.containerSecurityContext.runAsGroup Set Redis® replicas containers' Security Context runAsGroup
## @param replica.containerSecurityContext.runAsNonRoot Set Redis® replicas containers' Security Context runAsNonRoot
## @param replica.containerSecurityContext.allowPrivilegeEscalation Set Redis® replicas pod's Security Context allowPrivilegeEscalation
## @param replica.containerSecurityContext.readOnlyRootFilesystem Set container's Security Context read-only root filesystem
## @param replica.containerSecurityContext.seccompProfile.type Set Redis® replicas containers' Security Context seccompProfile
## @param replica.containerSecurityContext.capabilities.drop Set Redis® replicas containers' Security Context capabilities to drop
##
containerSecurityContext:
enabled: true
seLinuxOptions: {}
runAsUser: 1001
runAsGroup: 1001
runAsNonRoot: true
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
seccompProfile:
type: RuntimeDefault
capabilities:
drop: ["ALL"]
## @param replica.schedulerName Alternate scheduler for Redis® replicas pods
## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
##
schedulerName: ""
## @param replica.updateStrategy.type Redis® replicas statefulset strategy type
## @skip replica.updateStrategy.rollingUpdate
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#update-strategies
##
updateStrategy:
## StrategyType
## Can be set to RollingUpdate, OnDelete (statefulset), Recreate (deployment)
##
type: RollingUpdate
## @param replica.minReadySeconds How many seconds a pod needs to be ready before killing the next, during update
##
minReadySeconds: 0
## @param replica.priorityClassName Redis® replicas pods' priorityClassName
##
priorityClassName: ""
## @param replica.podManagementPolicy podManagementPolicy to manage scaling operation of %%MAIN_CONTAINER_NAME%% pods
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#pod-management-policies
##
podManagementPolicy: ""
## @param replica.automountServiceAccountToken Mount Service Account token in pod
##
automountServiceAccountToken: false
## @param replica.hostAliases Redis® replicas pods host aliases
## https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/
##
hostAliases: []
## @param replica.podLabels Extra labels for Redis® replicas pods
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
##
podLabels: {}
## @param replica.podAnnotations Annotations for Redis® replicas pods
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/
##
podAnnotations: {}
## @param replica.shareProcessNamespace Share a single process namespace between all of the containers in Redis® replicas pods
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/
##
shareProcessNamespace: false
## @param replica.podAffinityPreset Pod affinity preset. Ignored if `replica.affinity` is set. Allowed values: `soft` or `hard`
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity
##
podAffinityPreset: ""
## @param replica.podAntiAffinityPreset Pod anti-affinity preset. Ignored if `replica.affinity` is set. Allowed values: `soft` or `hard`
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity
##
podAntiAffinityPreset: soft
## Node affinity preset
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity
##
nodeAffinityPreset:
## @param replica.nodeAffinityPreset.type Node affinity preset type. Ignored if `replica.affinity` is set. Allowed values: `soft` or `hard`
##
type: ""
## @param replica.nodeAffinityPreset.key Node label key to match. Ignored if `replica.affinity` is set
##
key: ""
## @param replica.nodeAffinityPreset.values Node label values to match. Ignored if `replica.affinity` is set
## E.g.
## values:
## - e2e-az1
## - e2e-az2
##
values: []
## @param replica.affinity Affinity for Redis® replicas pods assignment
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
## NOTE: `replica.podAffinityPreset`, `replica.podAntiAffinityPreset`, and `replica.nodeAffinityPreset` will be ignored when it's set
##
affinity: {}
## @param replica.nodeSelector Node labels for Redis® replicas pods assignment
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/
##
nodeSelector: {}
## @param replica.tolerations Tolerations for Redis® replicas pods assignment
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
##
tolerations: []
## @param replica.topologySpreadConstraints Spread Constraints for Redis® replicas pod assignment
## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/
## E.g.
## topologySpreadConstraints:
## - maxSkew: 1
## topologyKey: node
## whenUnsatisfiable: DoNotSchedule
##
topologySpreadConstraints: []
## @param replica.dnsPolicy DNS Policy for Redis® replica pods
## ref: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/
## E.g.
## dnsPolicy: ClusterFirst
##
dnsPolicy: ""
## @param replica.dnsConfig DNS Configuration for Redis® replica pods
## ref: https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/
## E.g.
## dnsConfig:
## options:
## - name: ndots
## value: "4"
## - name: single-request-reopen
##
dnsConfig: {}
## @param replica.lifecycleHooks for the Redis® replica container(s) to automate configuration before or after startup
##
lifecycleHooks: {}
## @param replica.extraVolumes Optionally specify extra list of additional volumes for the Redis® replicas pod(s)
##
extraVolumes: []
## @param replica.extraVolumeMounts Optionally specify extra list of additional volumeMounts for the Redis® replicas container(s)
##
extraVolumeMounts: []
## @param replica.sidecars Add additional sidecar containers to the Redis® replicas pod(s)
## e.g:
## sidecars:
## - name: your-image-name
## image: your-image
## imagePullPolicy: Always
## ports:
## - name: portname
## containerPort: 1234
##
sidecars: []
## @param replica.initContainers Add additional init containers to the Redis® replicas pod(s)
## ref: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
## e.g:
## initContainers:
## - name: your-image-name
## image: your-image
## imagePullPolicy: Always
## command: ['sh', '-c', 'echo "hello world"']
##
initContainers: []
## Persistence Parameters
## ref: https://kubernetes.io/docs/concepts/storage/persistent-volumes/
##
persistence:
## @param replica.persistence.enabled Enable persistence on Redis® replicas nodes using Persistent Volume Claims
##
enabled: true
## @param replica.persistence.medium Provide a medium for `emptyDir` volumes.
##
medium: ""
## @param replica.persistence.sizeLimit Set this to enable a size limit for `emptyDir` volumes.
##
sizeLimit: ""
## @param replica.persistence.path The path the volume will be mounted at on Redis® replicas containers
## NOTE: Useful when using different Redis® images
##
path: /data
## @param replica.persistence.subPath The subdirectory of the volume to mount on Redis® replicas containers
## NOTE: Useful in dev environments
##
subPath: ""
## @param replica.persistence.subPathExpr Used to construct the subPath subdirectory of the volume to mount on Redis® replicas containers
##
subPathExpr: ""
## @param replica.persistence.storageClass 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: ""
## @param replica.persistence.accessModes Persistent Volume access modes
##
accessModes:
- ReadWriteOnce
## @param replica.persistence.size Persistent Volume size
##
size: 1Gi #副本存储大小
## @param replica.persistence.annotations Additional custom annotations for the PVC
##
annotations: {}
## @param replica.persistence.labels Additional custom labels for the PVC
##
labels: {}
## @param replica.persistence.selector Additional labels to match for the PVC
## e.g:
## selector:
## matchLabels:
## app: my-app
##
selector: {}
## @param replica.persistence.dataSource Custom PVC data source
##
dataSource: {}
## @param replica.persistence.existingClaim Use a existing PVC which must be created manually before bound
## NOTE: requires replica.persistence.enabled: true
##
existingClaim: ""
## persistentVolumeClaimRetentionPolicy
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#persistentvolumeclaim-retention
## @param replica.persistentVolumeClaimRetentionPolicy.enabled Controls if and how PVCs are deleted during the lifecycle of a StatefulSet
## @param replica.persistentVolumeClaimRetentionPolicy.whenScaled Volume retention behavior when the replica count of the StatefulSet is reduced
## @param replica.persistentVolumeClaimRetentionPolicy.whenDeleted Volume retention behavior that applies when the StatefulSet is deleted
##
persistentVolumeClaimRetentionPolicy:
enabled: false
whenScaled: Retain
whenDeleted: Retain
## Redis® replicas service parameters
##
service:
## @param replica.service.type Redis® replicas service type
##
type: NodePort #默认为ClusterIP，这里我们改为NodePort
## @param replica.service.ports.redis Redis® replicas service port
##
ports:
redis: 6379
## @param replica.service.nodePorts.redis Node port for Redis® replicas
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
## NOTE: choose port between <30000-32767>
##
nodePorts:
redis: "" #端口范围为30000-32767 不写 则默认分配
## @param replica.service.externalTrafficPolicy Redis® replicas service external traffic policy
## ref: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
##
externalTrafficPolicy: Cluster
## @param replica.service.internalTrafficPolicy Redis® replicas service internal traffic policy (requires Kubernetes v1.22 or greater to be usable)
## ref: https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/
##
internalTrafficPolicy: Cluster
## @param replica.service.extraPorts Extra ports to expose (normally used with the `sidecar` value)
##
extraPorts: []
## @param replica.service.clusterIP Redis® replicas service Cluster IP
##
clusterIP: ""
## @param replica.service.loadBalancerIP Redis® replicas service Load Balancer IP
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
##
loadBalancerIP: ""
## @param replica.service.loadBalancerClass replicas service Load Balancer class if service type is `LoadBalancer` (optional, cloud specific)
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-loadbalancer
##
loadBalancerClass: ""
## @param replica.service.loadBalancerSourceRanges Redis® replicas service Load Balancer sources
## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service
## e.g.
## loadBalancerSourceRanges:
## - 10.10.10.0/24
##
loadBalancerSourceRanges: []
## @param replica.service.annotations Additional custom annotations for Redis® replicas service
##
annotations: {}
## @param replica.service.sessionAffinity Session Affinity for Kubernetes service, can be "None" or "ClientIP"
## If "ClientIP", consecutive client requests will be directed to the same Pod
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
##
sessionAffinity: None
## @param replica.service.sessionAffinityConfig Additional settings for the sessionAffinity
## sessionAffinityConfig:
## clientIP:
## timeoutSeconds: 300
##
sessionAffinityConfig: {}
## @param replica.terminationGracePeriodSeconds Integer setting the termination grace period for the redis-replicas pods
##
terminationGracePeriodSeconds: 30
## Autoscaling configuration
##
autoscaling:
## @param replica.autoscaling.enabled Enable replica autoscaling settings
##
enabled: false
## @param replica.autoscaling.minReplicas Minimum replicas for the pod autoscaling
##
minReplicas: 1
## @param replica.autoscaling.maxReplicas Maximum replicas for the pod autoscaling
##
maxReplicas: 11
## @param replica.autoscaling.targetCPU Percentage of CPU to consider when autoscaling
##
targetCPU: ""
## @param replica.autoscaling.targetMemory Percentage of Memory to consider when autoscaling
##
targetMemory: ""
## ServiceAccount configuration
##
serviceAccount:
## @param replica.serviceAccount.create Specifies whether a ServiceAccount should be created
##
create: true
## @param replica.serviceAccount.name The name of the ServiceAccount to use.
## If not set and create is true, a name is generated using the common.names.fullname template
##
name: ""
## @param replica.serviceAccount.automountServiceAccountToken Whether to auto mount the service account token
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#use-the-default-service-account-to-access-the-api-server
##
automountServiceAccountToken: false
## @param replica.serviceAccount.annotations Additional custom annotations for the ServiceAccount
##
annotations: {}
## Pod Disruption Budget configuration
## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb
## @param replica.pdb.create Enable/disable a Pod Disruption Budget creation
## @param replica.pdb.minAvailable [object] Minimum number/percentage of pods that should remain scheduled
## @param replica.pdb.maxUnavailable [object] Maximum number/percentage of pods that may be made unavailable. Defaults to `1` if both `replica.pdb.minAvailable` and `replica.pdb.maxUnavailable` are empty.
##
pdb:
create: true
minAvailable: ""
maxUnavailable: ""
## @section Redis® Sentinel configuration parameters
##
sentinel:
## @param sentinel.enabled Use Redis® Sentinel on Redis® pods.
## IMPORTANT: this will disable the master and replicas services and
## create a single Redis® service exposing both the Redis and Sentinel ports
##
enabled: false
## Bitnami Redis® Sentinel image version
## ref: https://hub.docker.com/r/bitnami/redis-sentinel/tags/
## @param sentinel.image.registry [default: REGISTRY_NAME] Redis® Sentinel image registry
## @param sentinel.image.repository [default: REPOSITORY_NAME/redis-sentinel] Redis® Sentinel image repository
## @skip sentinel.image.tag Redis® Sentinel image tag (immutable tags are recommended)
## @param sentinel.image.digest Redis® Sentinel image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag
## @param sentinel.image.pullPolicy Redis® Sentinel image pull policy
## @param sentinel.image.pullSecrets Redis® Sentinel image pull secrets
## @param sentinel.image.debug Enable image debug mode
##
image:
registry: docker.io
repository: bitnami/redis-sentinel
tag: 7.4.0-debian-12-r1
digest: ""
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: https://kubernetes.io/docs/concepts/containers/images/#pre-pulled-images
##
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/
## e.g:
## pullSecrets:
## - myRegistryKeySecretName
##
pullSecrets: []
## Enable debug mode
##
debug: false
## @param sentinel.annotations Additional custom annotations for Redis® Sentinel resource
##
annotations: {}
## @param sentinel.masterSet Master set name
##
masterSet: mymaster
## @param sentinel.quorum Sentinel Quorum
##
quorum: 2
## @param sentinel.getMasterTimeout Amount of time to allow before get_sentinel_master_info() times out.
##
getMasterTimeout: 90
## @param sentinel.automateClusterRecovery Automate cluster recovery in cases where the last replica is not considered a good replica and Sentinel won't automatically failover to it.
## This also prevents any new replica from starting until the last remaining replica is elected as master to guarantee that it is the one to be elected by Sentinel, and not a newly started replica with no data.
## NOTE: This feature requires a "downAfterMilliseconds" value less or equal to 2000.
##
automateClusterRecovery: false
## @param sentinel.redisShutdownWaitFailover Whether the Redis® master container waits for the failover at shutdown (in addition to the Redis® Sentinel container).
##
redisShutdownWaitFailover: true
## Sentinel timing restrictions
## @param sentinel.downAfterMilliseconds Timeout for detecting a Redis® node is down
## @param sentinel.failoverTimeout Timeout for performing a election failover
##
downAfterMilliseconds: 60000
failoverTimeout: 180000
## @param sentinel.parallelSyncs Number of replicas that can be reconfigured in parallel to use the new master after a failover
##
parallelSyncs: 1
## @param sentinel.configuration Configuration for Redis® Sentinel nodes
## ref: https://redis.io/topics/sentinel
##
configuration: ""
## @param sentinel.command Override default container command (useful when using custom images)
##
command: []
## @param sentinel.args Override default container args (useful when using custom images)
##
args: []
## @param sentinel.enableServiceLinks Whether information about services should be injected into pod's environment variable
##
enableServiceLinks: true
## @param sentinel.preExecCmds Additional commands to run prior to starting Redis® Sentinel
##
preExecCmds: []
## @param sentinel.extraEnvVars Array with extra environment variables to add to Redis® Sentinel nodes
## e.g:
## extraEnvVars:
## - name: FOO
## value: "bar"
##
extraEnvVars: []
## @param sentinel.extraEnvVarsCM Name of existing ConfigMap containing extra env vars for Redis® Sentinel nodes
##
extraEnvVarsCM: ""
## @param sentinel.extraEnvVarsSecret Name of existing Secret containing extra env vars for Redis® Sentinel nodes
##
extraEnvVarsSecret: ""
## @param sentinel.externalMaster.enabled Use external master for bootstrapping
## @param sentinel.externalMaster.host External master host to bootstrap from
## @param sentinel.externalMaster.port Port for Redis service external master host
##
externalMaster:
enabled: false
host: ""
port: 6379
## @param sentinel.containerPorts.sentinel Container port to open on Redis® Sentinel nodes
##
containerPorts:
sentinel: 26379
## Configure extra options for Redis® containers' liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes
## @param sentinel.startupProbe.enabled Enable startupProbe on Redis® Sentinel nodes
## @param sentinel.startupProbe.initialDelaySeconds Initial delay seconds for startupProbe
## @param sentinel.startupProbe.periodSeconds Period seconds for startupProbe
## @param sentinel.startupProbe.timeoutSeconds Timeout seconds for startupProbe
## @param sentinel.startupProbe.failureThreshold Failure threshold for startupProbe
## @param sentinel.startupProbe.successThreshold Success threshold for startupProbe
##
startupProbe:
enabled: true
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 22
## @param sentinel.livenessProbe.enabled Enable livenessProbe on Redis® Sentinel nodes
## @param sentinel.livenessProbe.initialDelaySeconds Initial delay seconds for livenessProbe
## @param sentinel.livenessProbe.periodSeconds Period seconds for livenessProbe
## @param sentinel.livenessProbe.timeoutSeconds Timeout seconds for livenessProbe
## @param sentinel.livenessProbe.failureThreshold Failure threshold for livenessProbe
## @param sentinel.livenessProbe.successThreshold Success threshold for livenessProbe
##
livenessProbe:
enabled: true
initialDelaySeconds: 20
periodSeconds: 10
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 6
## @param sentinel.readinessProbe.enabled Enable readinessProbe on Redis® Sentinel nodes
## @param sentinel.readinessProbe.initialDelaySeconds Initial delay seconds for readinessProbe
## @param sentinel.readinessProbe.periodSeconds Period seconds for readinessProbe
## @param sentinel.readinessProbe.timeoutSeconds Timeout seconds for readinessProbe
## @param sentinel.readinessProbe.failureThreshold Failure threshold for readinessProbe
## @param sentinel.readinessProbe.successThreshold Success threshold for readinessProbe
##
readinessProbe:
enabled: true
initialDelaySeconds: 20
periodSeconds: 5
timeoutSeconds: 1
successThreshold: 1
failureThreshold: 6
## @param sentinel.customStartupProbe Custom startupProbe that overrides the default one
##
customStartupProbe: {}
## @param sentinel.customLivenessProbe Custom livenessProbe that overrides the default one
##
customLivenessProbe: {}
## @param sentinel.customReadinessProbe Custom readinessProbe that overrides the default one
##
customReadinessProbe: {}
## Persistence parameters
## ref: https://kubernetes.io/docs/concepts/storage/persistent-volumes/
##
persistence:
## @param sentinel.persistence.enabled Enable persistence on Redis® sentinel nodes using Persistent Volume Claims (Experimental)
##
enabled: false
## @param sentinel.persistence.storageClass 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: ""
## @param sentinel.persistence.accessModes Persistent Volume access modes
##
accessModes:
- ReadWriteOnce
## @param sentinel.persistence.size Persistent Volume size
##
size: 100Mi
## @param sentinel.persistence.annotations Additional custom annotations for the PVC
##
annotations: {}
## @param sentinel.persistence.labels Additional custom labels for the PVC
##
labels: {}
## @param sentinel.persistence.selector Additional labels to match for the PVC
## e.g:
## selector:
## matchLabels:
## app: my-app
##
selector: {}
## @param sentinel.persistence.dataSource Custom PVC data source
##
dataSource: {}
## @param sentinel.persistence.medium Provide a medium for `emptyDir` volumes.
##
medium: ""
## @param sentinel.persistence.sizeLimit Set this to enable a size limit for `emptyDir` volumes.
##
sizeLimit: ""
## persistentVolumeClaimRetentionPolicy
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#persistentvolumeclaim-retention
## @param sentinel.persistentVolumeClaimRetentionPolicy.enabled Controls if and how PVCs are deleted during the lifecycle of a StatefulSet
## @param sentinel.persistentVolumeClaimRetentionPolicy.whenScaled Volume retention behavior when the replica count of the StatefulSet is reduced
## @param sentinel.persistentVolumeClaimRetentionPolicy.whenDeleted Volume retention behavior that applies when the StatefulSet is deleted
##
persistentVolumeClaimRetentionPolicy:
enabled: false
whenScaled: Retain
whenDeleted: Retain
## Redis® Sentinel resource requests and limits
## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
## @param sentinel.resourcesPreset Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if sentinel.resources is set (sentinel.resources is recommended for production).
## More information: https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15
##
resourcesPreset: "nano"
## @param sentinel.resources Set container requests and limits for different resources like CPU or memory (essential for production workloads)
## Example:
## resources:
## requests:
## cpu: 2
## memory: 512Mi
## limits:
## cpu: 3
## memory: 1024Mi
##
resources: {}
## Configure Container Security Context
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
## @param sentinel.containerSecurityContext.enabled Enabled Redis® Sentinel containers' Security Context
## @param sentinel.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container
## @param sentinel.containerSecurityContext.runAsUser Set Redis® Sentinel containers' Security Context runAsUser
## @param sentinel.containerSecurityContext.runAsGroup Set Redis® Sentinel containers' Security Context runAsGroup
## @param sentinel.containerSecurityContext.runAsNonRoot Set Redis® Sentinel containers' Security Context runAsNonRoot
## @param sentinel.containerSecurityContext.readOnlyRootFilesystem Set container's Security Context read-only root filesystem
## @param sentinel.containerSecurityContext.allowPrivilegeEscalation Set Redis® Sentinel containers' Security Context allowPrivilegeEscalation
## @param sentinel.containerSecurityContext.seccompProfile.type Set Redis® Sentinel containers' Security Context seccompProfile
## @param sentinel.containerSecurityContext.capabilities.drop Set Redis® Sentinel containers' Security Context capabilities to drop
##
containerSecurityContext:
enabled: true
seLinuxOptions: {}
runAsUser: 1001
runAsGroup: 1001
runAsNonRoot: true
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
seccompProfile:
type: RuntimeDefault
capabilities:
drop: ["ALL"]
## @param sentinel.lifecycleHooks for the Redis® sentinel container(s) to automate configuration before or after startup
##
lifecycleHooks: {}
## @param sentinel.extraVolumes Optionally specify extra list of additional volumes for the Redis® Sentinel
##
extraVolumes: []
## @param sentinel.extraVolumeMounts Optionally specify extra list of additional volumeMounts for the Redis® Sentinel container(s)
##
extraVolumeMounts: []
## Redis® Sentinel service parameters
## Note: values passed in this section also configure the master service, unless the sentinel.masterService is explicitly overridden.
service:
## @param sentinel.service.type Redis® Sentinel service type
##
type: ClusterIP
## @param sentinel.service.ports.redis Redis® service port for Redis®
## @param sentinel.service.ports.sentinel Redis® service port for Redis® Sentinel
##
ports:
redis: 6379
sentinel: 26379
## @param sentinel.service.nodePorts.redis Node port for Redis®
## @param sentinel.service.nodePorts.sentinel Node port for Sentinel
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
## NOTE: choose port between <30000-32767>
## NOTE: By leaving these values blank, they will be generated by ports-configmap
## If setting manually, please leave at least replica.replicaCount + 1 in between sentinel.service.nodePorts.redis and sentinel.service.nodePorts.sentinel to take into account the ports that will be created while incrementing that base port
##
nodePorts:
redis: ""
sentinel: ""
## @param sentinel.service.externalTrafficPolicy Redis® Sentinel service external traffic policy
## ref: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
##
externalTrafficPolicy: Cluster
## @param sentinel.service.extraPorts Extra ports to expose (normally used with the `sidecar` value)
##
extraPorts: []
## @param sentinel.service.clusterIP Redis® Sentinel service Cluster IP
##
clusterIP: ""
## @param sentinel.service.createMaster Enable master service pointing to the current master (experimental)
## NOTE: rbac.create need to be set to true
##
createMaster: false
## @param sentinel.service.loadBalancerIP Redis® Sentinel service Load Balancer IP
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
##
loadBalancerIP: ""
## @param sentinel.service.loadBalancerClass sentinel service Load Balancer class if service type is `LoadBalancer` (optional, cloud specific)
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-loadbalancer
##
loadBalancerClass: ""
## @param sentinel.service.loadBalancerSourceRanges Redis® Sentinel service Load Balancer sources
## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service
## e.g.
## loadBalancerSourceRanges:
## - 10.10.10.0/24
##
loadBalancerSourceRanges: []
## @param sentinel.service.annotations Additional custom annotations for Redis® Sentinel service
##
annotations: {}
## @param sentinel.service.sessionAffinity Session Affinity for Kubernetes service, can be "None" or "ClientIP"
## If "ClientIP", consecutive client requests will be directed to the same Pod
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
##
sessionAffinity: None
## @param sentinel.service.sessionAffinityConfig Additional settings for the sessionAffinity
## sessionAffinityConfig:
## clientIP:
## timeoutSeconds: 300
##
sessionAffinityConfig: {}
## Headless service properties
##
headless:
## @param sentinel.service.headless.annotations Annotations for the headless service.
##
annotations: {}
## Redis® master service parameters
##
masterService:
## @param sentinel.masterService.enabled Enable master service pointing to the current master (experimental)
## NOTE: rbac.create need to be set to true
##
enabled: false
## @param sentinel.masterService.type Redis® Sentinel master service type
##
type: ClusterIP
## @param sentinel.masterService.ports.redis Redis® service port for Redis®
##
ports:
redis: 6379
## @param sentinel.masterService.nodePorts.redis Node port for Redis®
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
## NOTE: choose port between <30000-32767>
## NOTE: By leaving these values blank, they will be generated by ports-configmap
## If setting manually, please leave at least replica.replicaCount + 1 in between sentinel.service.nodePorts.redis and sentinel.service.nodePorts.sentinel to take into account the ports that will be created while incrementing that base port
##
nodePorts:
redis: ""
## @param sentinel.masterService.externalTrafficPolicy Redis® master service external traffic policy
## ref: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
##
externalTrafficPolicy: ""
## @param sentinel.masterService.extraPorts Extra ports to expose (normally used with the `sidecar` value)
##
extraPorts: []
## @param sentinel.masterService.clusterIP Redis® master service Cluster IP
##
clusterIP: ""
## @param sentinel.masterService.loadBalancerIP Redis® master service Load Balancer IP
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
##
loadBalancerIP: ""
## @param sentinel.masterService.loadBalancerClass master service Load Balancer class if service type is `LoadBalancer` (optional, cloud specific)
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-loadbalancer
##
loadBalancerClass: ""
## @param sentinel.masterService.loadBalancerSourceRanges Redis® master service Load Balancer sources
## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service
## e.g.
## loadBalancerSourceRanges:
## - 10.10.10.0/24
##
loadBalancerSourceRanges: []
## @param sentinel.masterService.annotations Additional custom annotations for Redis® master service
##
annotations: {}
## @param sentinel.masterService.sessionAffinity Session Affinity for Kubernetes service, can be "None" or "ClientIP"
## If "ClientIP", consecutive client requests will be directed to the same Pod
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
##
sessionAffinity: None
## @param sentinel.masterService.sessionAffinityConfig Additional settings for the sessionAffinity
## sessionAffinityConfig:
## clientIP:
## timeoutSeconds: 300
##
sessionAffinityConfig: {}
## @param sentinel.terminationGracePeriodSeconds Integer setting the termination grace period for the redis-node pods
##
terminationGracePeriodSeconds: 30
## @section Other Parameters
##
## @param serviceBindings.enabled Create secret for service binding (Experimental)
## Ref: https://servicebinding.io/service-provider/
##
serviceBindings:
enabled: false
## Network Policy configuration
## ref: https://kubernetes.io/docs/concepts/services-networking/network-policies/
##
networkPolicy:
## @param networkPolicy.enabled Enable creation of NetworkPolicy resources
##
enabled: true
## @param networkPolicy.allowExternal Don't require client label for connections
## When set to false, only pods with the correct client label will have network access to the ports
## Redis® is listening on. When true, Redis® will accept connections from any source
## (with the correct destination port).
##
allowExternal: true
## @param networkPolicy.allowExternalEgress Allow the pod to access any range of port and all destinations.
##
allowExternalEgress: true
## @param networkPolicy.extraIngress Add extra ingress rules to the NetworkPolicy
## e.g:
## extraIngress:
## - ports:
## - port: 1234
## from:
## - podSelector:
## - matchLabels:
## - role: frontend
## - podSelector:
## - matchExpressions:
## - key: role
## operator: In
## values:
## - frontend
##
extraIngress: []
## @param networkPolicy.extraEgress Add extra egress rules to the NetworkPolicy
## e.g:
## extraEgress:
## - ports:
## - port: 1234
## to:
## - podSelector:
## - matchLabels:
## - role: frontend
## - podSelector:
## - matchExpressions:
## - key: role
## operator: In
## values:
## - frontend
##
extraEgress: []
## @param networkPolicy.ingressNSMatchLabels Labels to match to allow traffic from other namespaces
## @param networkPolicy.ingressNSPodMatchLabels Pod labels to match to allow traffic from other namespaces
##
ingressNSMatchLabels: {}
ingressNSPodMatchLabels: {}
metrics:
## @param networkPolicy.metrics.allowExternal Don't require client label for connections for metrics endpoint
## When set to false, only pods with the correct client label will have network access to the metrics port
##
allowExternal: true
## @param networkPolicy.metrics.ingressNSMatchLabels Labels to match to allow traffic from other namespaces to metrics endpoint
## @param networkPolicy.metrics.ingressNSPodMatchLabels Pod labels to match to allow traffic from other namespaces to metrics endpoint
##
ingressNSMatchLabels: {}
ingressNSPodMatchLabels: {}
## PodSecurityPolicy configuration
## ref: https://kubernetes.io/docs/concepts/policy/pod-security-policy/
##
podSecurityPolicy:
## @param podSecurityPolicy.create Whether to create a PodSecurityPolicy. WARNING: PodSecurityPolicy is deprecated in Kubernetes v1.21 or later, unavailable in v1.25 or later
##
create: false
## @param podSecurityPolicy.enabled Enable PodSecurityPolicy's RBAC rules
##
enabled: false
## RBAC configuration
##
rbac:
## @param rbac.create Specifies whether RBAC resources should be created
##
create: false
## @param rbac.rules Custom RBAC rules to set
## e.g:
## rules:
## - apiGroups:
## - ""
## resources:
## - pods
## verbs:
## - get
## - list
##
rules: []
## ServiceAccount configuration
##
serviceAccount:
## @param serviceAccount.create Specifies whether a ServiceAccount should be created
##
create: true
## @param serviceAccount.name The name of the ServiceAccount to use.
## If not set and create is true, a name is generated using the common.names.fullname template
##
name: ""
## @param serviceAccount.automountServiceAccountToken Whether to auto mount the service account token
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#use-the-default-service-account-to-access-the-api-server
##
automountServiceAccountToken: false
## @param serviceAccount.annotations Additional custom annotations for the ServiceAccount
##
annotations: {}
## Redis® Pod Disruption Budget configuration
## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb/
## @param pdb DEPRECATED Please use `master.pdb` and `replica.pdb` values instead
##
pdb: {}
## TLS configuration
##
tls:
## @param tls.enabled Enable TLS traffic
##
enabled: false
## @param tls.authClients Require clients to authenticate
##
authClients: true
## @param tls.autoGenerated Enable autogenerated certificates
##
autoGenerated: false
## @param tls.existingSecret The name of the existing secret that contains the TLS certificates
##
existingSecret: ""
## @param tls.certificatesSecret DEPRECATED. Use existingSecret instead.
##
certificatesSecret: ""
## @param tls.certFilename Certificate filename
##
certFilename: ""
## @param tls.certKeyFilename Certificate Key filename
##
certKeyFilename: ""
## @param tls.certCAFilename CA Certificate filename
##
certCAFilename: ""
## @param tls.dhParamsFilename File containing DH params (in order to support DH based ciphers)
##
dhParamsFilename: ""
## @section Metrics Parameters
##
metrics:
## @param metrics.enabled Start a sidecar prometheus exporter to expose Redis® metrics
##
enabled: false
## Bitnami Redis® Exporter image
## ref: https://hub.docker.com/r/bitnami/redis-exporter/tags/
## @param metrics.image.registry [default: REGISTRY_NAME] Redis® Exporter image registry
## @param metrics.image.repository [default: REPOSITORY_NAME/redis-exporter] Redis® Exporter image repository
## @skip metrics.image.tag Redis® Exporter image tag (immutable tags are recommended)
## @param metrics.image.digest Redis® Exporter image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag
## @param metrics.image.pullPolicy Redis® Exporter image pull policy
## @param metrics.image.pullSecrets Redis® Exporter image pull secrets
##
image:
registry: docker.io
repository: bitnami/redis-exporter
tag: 1.62.0-debian-12-r3
digest: ""
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/
## e.g:
## pullSecrets:
## - myRegistryKeySecretName
##
pullSecrets: []
## @param metrics.containerPorts.http Metrics HTTP container port
##
containerPorts:
http: 9121
## Configure extra options for Redis® containers' liveness, readiness & startup probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
## @param metrics.startupProbe.enabled Enable startupProbe on Redis® replicas nodes
## @param metrics.startupProbe.initialDelaySeconds Initial delay seconds for startupProbe
## @param metrics.startupProbe.periodSeconds Period seconds for startupProbe
## @param metrics.startupProbe.timeoutSeconds Timeout seconds for startupProbe
## @param metrics.startupProbe.failureThreshold Failure threshold for startupProbe
## @param metrics.startupProbe.successThreshold Success threshold for startupProbe
##
startupProbe:
enabled: false
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 5
## @param metrics.livenessProbe.enabled Enable livenessProbe on Redis® replicas nodes
## @param metrics.livenessProbe.initialDelaySeconds Initial delay seconds for livenessProbe
## @param metrics.livenessProbe.periodSeconds Period seconds for livenessProbe
## @param metrics.livenessProbe.timeoutSeconds Timeout seconds for livenessProbe
## @param metrics.livenessProbe.failureThreshold Failure threshold for livenessProbe
## @param metrics.livenessProbe.successThreshold Success threshold for livenessProbe
##
livenessProbe:
enabled: true
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 5
## @param metrics.readinessProbe.enabled Enable readinessProbe on Redis® replicas nodes
## @param metrics.readinessProbe.initialDelaySeconds Initial delay seconds for readinessProbe
## @param metrics.readinessProbe.periodSeconds Period seconds for readinessProbe
## @param metrics.readinessProbe.timeoutSeconds Timeout seconds for readinessProbe
## @param metrics.readinessProbe.failureThreshold Failure threshold for readinessProbe
## @param metrics.readinessProbe.successThreshold Success threshold for readinessProbe
##
readinessProbe:
enabled: true
initialDelaySeconds: 5
periodSeconds: 10
timeoutSeconds: 1
successThreshold: 1
failureThreshold: 3
## @param metrics.customStartupProbe Custom startupProbe that overrides the default one
##
customStartupProbe: {}
## @param metrics.customLivenessProbe Custom livenessProbe that overrides the default one
##
customLivenessProbe: {}
## @param metrics.customReadinessProbe Custom readinessProbe that overrides the default one
##
customReadinessProbe: {}
## @param metrics.command Override default metrics container init command (useful when using custom images)
##
command: []
## @param metrics.redisTargetHost A way to specify an alternative Redis® hostname
## Useful for certificate CN/SAN matching
##
redisTargetHost: "localhost"
## @param metrics.extraArgs Extra arguments for Redis® exporter, for example:
## e.g.:
## extraArgs:
## check-keys: myKey,myOtherKey
##
extraArgs: {}
## @param metrics.extraEnvVars Array with extra environment variables to add to Redis® exporter
## e.g:
## extraEnvVars:
## - name: FOO
## value: "bar"
##
extraEnvVars: []
## Configure Container Security Context
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
## @param metrics.containerSecurityContext.enabled Enabled Redis® exporter containers' Security Context
## @param metrics.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container
## @param metrics.containerSecurityContext.runAsUser Set Redis® exporter containers' Security Context runAsUser
## @param metrics.containerSecurityContext.runAsGroup Set Redis® exporter containers' Security Context runAsGroup
## @param metrics.containerSecurityContext.runAsNonRoot Set Redis® exporter containers' Security Context runAsNonRoot
## @param metrics.containerSecurityContext.allowPrivilegeEscalation Set Redis® exporter containers' Security Context allowPrivilegeEscalation
## @param metrics.containerSecurityContext.readOnlyRootFilesystem Set container's Security Context read-only root filesystem
## @param metrics.containerSecurityContext.seccompProfile.type Set Redis® exporter containers' Security Context seccompProfile
## @param metrics.containerSecurityContext.capabilities.drop Set Redis® exporter containers' Security Context capabilities to drop
##
containerSecurityContext:
enabled: true
seLinuxOptions: {}
runAsUser: 1001
runAsGroup: 1001
runAsNonRoot: true
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
seccompProfile:
type: RuntimeDefault
capabilities:
drop: ["ALL"]
## @param metrics.extraVolumes Optionally specify extra list of additional volumes for the Redis® metrics sidecar
##
extraVolumes: []
## @param metrics.extraVolumeMounts Optionally specify extra list of additional volumeMounts for the Redis® metrics sidecar
##
extraVolumeMounts: []
## Redis® exporter resource requests and limits
## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
## @param metrics.resourcesPreset Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if metrics.resources is set (metrics.resources is recommended for production).
## More information: https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15
##
resourcesPreset: "nano"
## @param metrics.resources Set container requests and limits for different resources like CPU or memory (essential for production workloads)
## Example:
## resources:
## requests:
## cpu: 2
## memory: 512Mi
## limits:
## cpu: 3
## memory: 1024Mi
##
resources: {}
## @param metrics.podLabels Extra labels for Redis® exporter pods
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
##
podLabels: {}
## @param metrics.podAnnotations [object] Annotations for Redis® exporter pods
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/
##
podAnnotations:
prometheus.io/scrape: "true"
prometheus.io/port: "9121"
## Redis® exporter service parameters
##
service:
## @param metrics.service.enabled Create Service resource(s) for scraping metrics using PrometheusOperator ServiceMonitor, can be disabled when using a PodMonitor
##
enabled: true
## @param metrics.service.type Redis® exporter service type
##
type: ClusterIP
## @param metrics.service.ports.http Redis® exporter service port
##
ports:
http: 9121
## @param metrics.service.externalTrafficPolicy Redis® exporter service external traffic policy
## ref: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
##
externalTrafficPolicy: Cluster
## @param metrics.service.extraPorts Extra ports to expose (normally used with the `sidecar` value)
##
extraPorts: []
## @param metrics.service.loadBalancerIP Redis® exporter service Load Balancer IP
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
##
loadBalancerIP: ""
## @param metrics.service.loadBalancerClass exporter service Load Balancer class if service type is `LoadBalancer` (optional, cloud specific)
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-loadbalancer
##
loadBalancerClass: ""
## @param metrics.service.loadBalancerSourceRanges Redis® exporter service Load Balancer sources
## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service
## e.g.
## loadBalancerSourceRanges:
## - 10.10.10.0/24
##
loadBalancerSourceRanges: []
## @param metrics.service.annotations Additional custom annotations for Redis® exporter service
##
annotations: {}
## @param metrics.service.clusterIP Redis® exporter service Cluster IP
##
clusterIP: ""
## Prometheus Service Monitor
## ref: https://github.com/coreos/prometheus-operator
## https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#endpoint
##
serviceMonitor:
## @param metrics.serviceMonitor.port the service port to scrape metrics from
##
port: http-metrics
## @param metrics.serviceMonitor.enabled Create ServiceMonitor resource(s) for scraping metrics using PrometheusOperator
##
enabled: false
## @param metrics.serviceMonitor.namespace The namespace in which the ServiceMonitor will be created
##
namespace: ""
## @param metrics.serviceMonitor.interval The interval at which metrics should be scraped
##
interval: 30s
## @param metrics.serviceMonitor.scrapeTimeout The timeout after which the scrape is ended
##
scrapeTimeout: ""
## @param metrics.serviceMonitor.relabelings Metrics RelabelConfigs to apply to samples before scraping.
##
relabelings: []
## @skip metrics.serviceMonitor.relabellings DEPRECATED: Use `metrics.serviceMonitor.relabelings` instead.
##
relabellings: []
## @param metrics.serviceMonitor.metricRelabelings Metrics RelabelConfigs to apply to samples before ingestion.
##
metricRelabelings: []
## @param metrics.serviceMonitor.honorLabels Specify honorLabels parameter to add the scrape endpoint
##
honorLabels: false
## @param metrics.serviceMonitor.additionalLabels Additional labels that can be used so ServiceMonitor resource(s) can be discovered by Prometheus
##
additionalLabels: {}
## @param metrics.serviceMonitor.podTargetLabels Labels from the Kubernetes pod to be transferred to the created metrics
##
podTargetLabels: []
## @param metrics.serviceMonitor.sampleLimit Limit of how many samples should be scraped from every Pod
##
sampleLimit: false
## @param metrics.serviceMonitor.targetLimit Limit of how many targets should be scraped
##
targetLimit: false
## @param metrics.serviceMonitor.additionalEndpoints Additional endpoints to scrape (e.g sentinel)
##
additionalEndpoints: []
# uncomment in order to scrape sentinel metrics, also to in order distinguish between Sentinel and Redis container metrics
# add metricRelabelings with label like app=redis to main redis pod-monitor port
# - interval: "30s"
# path: "/scrape"
# port: "metrics"
# params:
# target: ["localhost:26379"]
# metricRelabelings:
# - targetLabel: "app"
# replacement: "sentinel"
## Prometheus Pod Monitor
## ref: https://github.com/coreos/prometheus-operator
## https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#podmonitor
##
podMonitor:
## @param metrics.podMonitor.port the pod port to scrape metrics from
##
port: metrics
## @param metrics.podMonitor.enabled Create PodMonitor resource(s) for scraping metrics using PrometheusOperator
##
enabled: false
## @param metrics.podMonitor.namespace The namespace in which the PodMonitor will be created
##
namespace: ""
## @param metrics.podMonitor.interval The interval at which metrics should be scraped
##
interval: 30s
## @param metrics.podMonitor.scrapeTimeout The timeout after which the scrape is ended
##
scrapeTimeout: ""
## @param metrics.podMonitor.relabelings Metrics RelabelConfigs to apply to samples before scraping.
##
relabelings: []
## @skip metrics.podMonitor.relabellings DEPRECATED: Use `metrics.podMonitor.relabelings` instead.
##
relabellings: []
## @param metrics.podMonitor.metricRelabelings Metrics RelabelConfigs to apply to samples before ingestion.
##
metricRelabelings: []
# - targetLabel: "app"
# replacement: "redis"
## @param metrics.podMonitor.honorLabels Specify honorLabels parameter to add the scrape endpoint
##
honorLabels: false
## @param metrics.podMonitor.additionalLabels Additional labels that can be used so PodMonitor resource(s) can be discovered by Prometheus
##
additionalLabels: {}
## @param metrics.podMonitor.podTargetLabels Labels from the Kubernetes pod to be transferred to the created metrics
##
podTargetLabels: []
## @param metrics.podMonitor.sampleLimit Limit of how many samples should be scraped from every Pod
##
sampleLimit: false
## @param metrics.podMonitor.targetLimit Limit of how many targets should be scraped
##
targetLimit: false
## @param metrics.podMonitor.additionalEndpoints Additional endpoints to scrape (e.g sentinel)
##
additionalEndpoints: []
# - interval: "30s"
# path: "/scrape"
# port: "metrics"
# params:
# target: ["localhost:26379"]
# metricRelabelings:
# - targetLabel: "app"
# replacement: "sentinel"
## Custom PrometheusRule to be defined
## ref: https://github.com/coreos/prometheus-operator#customresourcedefinitions
##
prometheusRule:
## @param metrics.prometheusRule.enabled Create a custom prometheusRule Resource for scraping metrics using PrometheusOperator
##
enabled: false
## @param metrics.prometheusRule.namespace The namespace in which the prometheusRule will be created
##
namespace: ""
## @param metrics.prometheusRule.additionalLabels Additional labels for the prometheusRule
##
additionalLabels: {}
## @param metrics.prometheusRule.rules Custom Prometheus rules
## e.g:
## rules:
## - alert: RedisDown
## expr: redis_up{service="{{ template "common.names.fullname" . }}-metrics"} == 0
## for: 2m
## labels:
## severity: error
## annotations:
## summary: Redis® instance {{ "{{ $labels.instance }}" }} down
## description: Redis® instance {{ "{{ $labels.instance }}" }} is down
## - alert: RedisMemoryHigh
## expr: >
## redis_memory_used_bytes{service="{{ template "common.names.fullname" . }}-metrics"} * 100
## /
## redis_memory_max_bytes{service="{{ template "common.names.fullname" . }}-metrics"}
## > 90
## for: 2m
## labels:
## severity: error
## annotations:
## summary: Redis® instance {{ "{{ $labels.instance }}" }} is using too much memory
## description: |
## Redis® instance {{ "{{ $labels.instance }}" }} is using {{ "{{ $value }}" }}% of its available memory.
## - alert: RedisKeyEviction
## expr: |
## increase(redis_evicted_keys_total{service="{{ template "common.names.fullname" . }}-metrics"}[5m]) > 0
## for: 1s
## labels:
## severity: error
## annotations:
## summary: Redis® instance {{ "{{ $labels.instance }}" }} has evicted keys
## description: |
## Redis® instance {{ "{{ $labels.instance }}" }} has evicted {{ "{{ $value }}" }} keys in the last 5 minutes.
##
rules: []
## @section Init Container Parameters
##
## 'volumePermissions' init container parameters
## Changes the owner and group of the persistent volume mount point to runAsUser:fsGroup values
## based on the *podSecurityContext/*containerSecurityContext parameters
##
volumePermissions:
## @param volumePermissions.enabled Enable init container that changes the owner/group of the PV mount point to `runAsUser:fsGroup`
##
enabled: false
## OS Shell + Utility image
## ref: https://hub.docker.com/r/bitnami/os-shell/tags/
## @param volumePermissions.image.registry [default: REGISTRY_NAME] OS Shell + Utility image registry
## @param volumePermissions.image.repository [default: REPOSITORY_NAME/os-shell] OS Shell + Utility image repository
## @skip volumePermissions.image.tag OS Shell + Utility image tag (immutable tags are recommended)
## @param volumePermissions.image.digest OS Shell + Utility image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag
## @param volumePermissions.image.pullPolicy OS Shell + Utility image pull policy
## @param volumePermissions.image.pullSecrets OS Shell + Utility image pull secrets
##
image:
registry: docker.io
repository: bitnami/os-shell
tag: 12-debian-12-r27
digest: ""
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/
## e.g:
## pullSecrets:
## - myRegistryKeySecretName
##
pullSecrets: []
## Init container's resource requests and limits
## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
## @param volumePermissions.resourcesPreset Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if volumePermissions.resources is set (volumePermissions.resources is recommended for production).
## More information: https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15
##
resourcesPreset: "nano"
## @param volumePermissions.resources Set container requests and limits for different resources like CPU or memory (essential for production workloads)
## Example:
## resources:
## requests:
## cpu: 2
## memory: 512Mi
## limits:
## cpu: 3
## memory: 1024Mi
##
resources: {}
## Init container Container Security Context
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container
## @param volumePermissions.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container
## @param volumePermissions.containerSecurityContext.runAsUser Set init container's Security Context runAsUser
## NOTE: when runAsUser is set to special value "auto", init container will try to chown the
## data folder to auto-determined user&group, using commands: `id -u`:`id -G | cut -d" " -f2`
## "auto" is especially useful for OpenShift which has scc with dynamic user ids (and 0 is not allowed)
##
containerSecurityContext:
seLinuxOptions: {}
runAsUser: 0
## @param volumePermissions.extraEnvVars Array with extra environment variables to add to volume permissions init container.
## e.g:
## extraEnvVars:
## - name: FOO
## value: "bar"
##
extraEnvVars: []
## Kubectl InitContainer
## used by Sentinel to update the isMaster label on the Redis(TM) pods
##
kubectl:
## Bitnami Kubectl image version
## ref: https://hub.docker.com/r/bitnami/kubectl/tags/
## @param kubectl.image.registry [default: REGISTRY_NAME] Kubectl image registry
## @param kubectl.image.repository [default: REPOSITORY_NAME/kubectl] Kubectl image repository
## @skip kubectl.image.tag Kubectl image tag (immutable tags are recommended), by default, using the current version
## @param kubectl.image.digest Kubectl image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag
## @param kubectl.image.pullPolicy Kubectl image pull policy
## @param kubectl.image.pullSecrets Kubectl pull secrets
##
image:
registry: docker.io
repository: bitnami/kubectl
tag: 1.31.0-debian-12-r1
digest: ""
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: https://kubernetes.io/docs/concepts/containers/images/#pre-pulled-images
##
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/
## e.g:
## pullSecrets:
## - myRegistryKeySecretName
##
pullSecrets: []
## @param kubectl.command kubectl command to execute
##
command: ["/opt/bitnami/scripts/kubectl-scripts/update-master-label.sh"]
## Configure Container Security Context
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
## @param kubectl.containerSecurityContext.enabled Enabled kubectl containers' Security Context
## @param kubectl.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container
## @param kubectl.containerSecurityContext.runAsUser Set kubectl containers' Security Context runAsUser
## @param kubectl.containerSecurityContext.runAsGroup Set kubectl containers' Security Context runAsGroup
## @param kubectl.containerSecurityContext.runAsNonRoot Set kubectl containers' Security Context runAsNonRoot
## @param kubectl.containerSecurityContext.allowPrivilegeEscalation Set kubectl containers' Security Context allowPrivilegeEscalation
## @param kubectl.containerSecurityContext.readOnlyRootFilesystem Set container's Security Context read-only root filesystem
## @param kubectl.containerSecurityContext.seccompProfile.type Set kubectl containers' Security Context seccompProfile
## @param kubectl.containerSecurityContext.capabilities.drop Set kubectl containers' Security Context capabilities to drop
##
containerSecurityContext:
enabled: true
seLinuxOptions: {}
runAsUser: 1001
runAsGroup: 1001
runAsNonRoot: true
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
seccompProfile:
type: RuntimeDefault
capabilities:
drop: ["ALL"]
## Bitnami Kubectl resource requests and limits
## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
## @param kubectl.resources.limits The resources limits for the kubectl containers
## @param kubectl.resources.requests The requested resources for the kubectl containers
##
resources:
limits: {}
requests: {}
## init-sysctl container parameters
## used to perform sysctl operation to modify Kernel settings (needed sometimes to avoid warnings)
##
sysctl:
## @param sysctl.enabled Enable init container to modify Kernel settings
##
enabled: false
## OS Shell + Utility image
## ref: https://hub.docker.com/r/bitnami/os-shell/tags/
## @param sysctl.image.registry [default: REGISTRY_NAME] OS Shell + Utility image registry
## @param sysctl.image.repository [default: REPOSITORY_NAME/os-shell] OS Shell + Utility image repository
## @skip sysctl.image.tag OS Shell + Utility image tag (immutable tags are recommended)
## @param sysctl.image.digest OS Shell + Utility image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag
## @param sysctl.image.pullPolicy OS Shell + Utility image pull policy
## @param sysctl.image.pullSecrets OS Shell + Utility image pull secrets
##
image:
registry: docker.io
repository: bitnami/os-shell
tag: 12-debian-12-r27
digest: ""
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/
## e.g:
## pullSecrets:
## - myRegistryKeySecretName
##
pullSecrets: []
## @param sysctl.command Override default init-sysctl container command (useful when using custom images)
##
command: []
## @param sysctl.mountHostSys Mount the host `/sys` folder to `/host-sys`
##
mountHostSys: false
## Init container's resource requests and limits
## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
## @param sysctl.resourcesPreset Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if sysctl.resources is set (sysctl.resources is recommended for production).
## More information: https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15
##
resourcesPreset: "nano"
## @param sysctl.resources Set container requests and limits for different resources like CPU or memory (essential for production workloads)
## Example:
## resources:
## requests:
## cpu: 2
## memory: 512Mi
## limits:
## cpu: 3
## memory: 1024Mi
##
resources: {}
## @section useExternalDNS Parameters
##
## @param useExternalDNS.enabled Enable various syntax that would enable external-dns to work. Note this requires a working installation of `external-dns` to be usable.
## @param useExternalDNS.additionalAnnotations Extra annotations to be utilized when `external-dns` is enabled.
## @param useExternalDNS.annotationKey The annotation key utilized when `external-dns` is enabled. Setting this to `false` will disable annotations.
## @param useExternalDNS.suffix The DNS suffix utilized when `external-dns` is enabled. Note that we prepend the suffix with the full name of the release.
##
useExternalDNS:
enabled: false
suffix: ""
annotationKey: external-dns.alpha.kubernetes.io/
additionalAnnotations: {}
