Bitnami/charts
2
0
Fork 0
mirror of https://github.com/bitnami/charts.git synced 2026-03-16 06:47:30 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update Redis trademark references

Browse Source 
* Update Redis reference and usage

Signed-off-by: michield <michield@vmware.com>

* Update Redis reference and usage

Summary: Change Redis solution names

Reviewers: jotamartos

Differential Revision: https://phabricator.nami.run/D63488

Signed-off-by: michield <michield@vmware.com>

* Corrections

Signed-off-by: michield <michield@vmware.com>

* Bump versions

Signed-off-by: michield <michield@vmware.com>

* Bump all affected Charts versions

Signed-off-by: michield <michield@vmware.com>

* Rebase Airflow version

Signed-off-by: michield <michield@vmware.com>

* Bump remaining affected Charts versions

Signed-off-by: michield <michield@vmware.com>

* Bump remaining affected Charts versions

Signed-off-by: michield <michield@vmware.com>

* Correction

Signed-off-by: michield <michield@vmware.com>

* Bump remaining affected Charts versions

Signed-off-by: michield <michield@vmware.com>

* Rebasing Chart versions

Signed-off-by: michield <michield@vmware.com>

* Update README.md with readme-generator-for-helm

Signed-off-by: Bitnami Containers <containers@bitnami.com>

* Update README.md with readme-generator-for-helm

Signed-off-by: Bitnami Containers <containers@bitnami.com>

* Bump airflow version

Signed-off-by: michield <michield@vmware.com>

* Bump all versions

Signed-off-by: michield <michield@vmware.com>

Co-authored-by: michield <michield@vmware.com>
Co-authored-by: Bitnami Containers <containers@bitnami.com>
This commit is contained in:
Michiel
2022-06-02 18:00:29 +02:00
committed by GitHub
parent a240e3966a
commit 2cada87ed4
42 changed files with 912 additions and 912 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
bitnami/redis-cluster/Chart.yaml
View File

@@ -8,7 +8,7 @@ dependencies:
tags:
- bitnami-common
version: 1.x.x
description: Redis(TM) is an open source, scalable, distributed in-memory cache for applications. It can be used to store and serve data in the form of strings, hashes, lists, sets and sorted sets.
description: Redis(R) is an open source, scalable, distributed in-memory cache for applications. It can be used to store and serve data in the form of strings, hashes, lists, sets and sorted sets.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/redis-cluster
icon: https://bitnami.com/assets/stacks/redis/img/redis-stack-220x234.png

238
bitnami/redis-cluster/README.md
View File

@@ -1,12 +1,12 @@
<!--- app-name: Redis&trade; Cluster -->
<!--- app-name: Redis&reg; Cluster -->
# Redis(TM) Cluster packaged by Bitnami
# Bitnami package for Redis(R) Cluster
Redis(TM) is an open source, scalable, distributed in-memory cache for applications. It can be used to store and serve data in the form of strings, hashes, lists, sets and sorted sets.
Redis(R) is an open source, scalable, distributed in-memory cache for applications. It can be used to store and serve data in the form of strings, hashes, lists, sets and sorted sets.
[Overview of Redis&trade; Cluster](http://redis.io)
[Overview of Redis&reg; Cluster](http://redis.io)
Disclaimer: Redis is a registered trademark of Redis Labs Ltd. Any rights therein are reserved to Redis Labs Ltd. Any use by Bitnami is for referential purposes only and does not indicate any sponsorship, endorsement, or affiliation between Redis Labs Ltd.
Disclaimer: Redis is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd. Any use by Bitnami is for referential purposes only and does not indicate any sponsorship, endorsement, or affiliation between Redis Ltd.
## TL;DR
@@ -17,21 +17,21 @@ $ helm install my-release bitnami/redis-cluster
## Introduction
This chart bootstraps a [Redis&trade;](https://github.com/bitnami/bitnami-docker-redis) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
This chart bootstraps a [Redis&reg;](https://github.com/bitnami/bitnami-docker-redis) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment and management of Helm Charts in clusters. This chart has been tested to work with NGINX Ingress, cert-manager, fluentd and Prometheus on top of the [BKPR](https://kubeprod.io/).
### Choose between Redis&trade; Helm Chart and Redis&trade; Cluster Helm Chart
### Choose between Redis&reg; Helm Chart and Redis&reg; Cluster Helm Chart
You can choose any of the two Redis&trade; Helm charts for deploying a Redis&trade; cluster.
While [Redis&trade; Helm Chart](https://github.com/bitnami/charts/tree/master/bitnami/redis) will deploy a master-slave cluster using Redis&trade; Sentinel, the [Redis&trade; Cluster Helm Chart](https://github.com/bitnami/charts/tree/master/bitnami/redis-cluster) will deploy a Redis&trade; Cluster with sharding.
You can choose any of the two Redis&reg; Helm charts for deploying a Redis&reg; cluster.
While [Redis&reg; Helm Chart](https://github.com/bitnami/charts/tree/master/bitnami/redis) will deploy a master-slave cluster using Redis&reg; Sentinel, the [Redis&reg; Cluster Helm Chart](https://github.com/bitnami/charts/tree/master/bitnami/redis-cluster) will deploy a Redis&reg; Cluster with sharding.
The main features of each chart are the following:
| Redis&trade; | Redis&trade; Cluster |
| Redis&reg; | Redis&reg; Cluster |
|--------------------------------------------------------|------------------------------------------------------------------------|
| Supports multiple databases | Supports only one database. Better if you have a big dataset |
| Single write point (single master) | Multiple write points (multiple masters) |
| ![Redis&trade; Topology](img/redis-topology.png) | ![Redis&trade; Cluster Topology](img/redis-cluster-topology.png) |
| ![Redis&reg; Topology](img/redis-topology.png) | ![Redis&reg; Cluster Topology](img/redis-cluster-topology.png) |
## Prerequisites
@@ -47,7 +47,7 @@ To install the chart with the release name `my-release`:
$ helm install my-release bitnami/redis-cluster
```
The command deploys Redis&trade; on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
The command deploys Redis&reg; on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
NOTE: if you get a timeout error waiting for the hook to complete increase the default timeout (300s) to a higher one, for example:
@@ -76,10 +76,10 @@ The command removes all the Kubernetes components associated with the chart and
| `global.imageRegistry` | Global Docker image registry | `""` |
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |
| `global.storageClass` | Global StorageClass for Persistent Volume(s) | `""` |
| `global.redis.password` | Redis&trade; password (overrides `password`) | `""` |
| `global.redis.password` | Redis&reg; password (overrides `password`) | `""` |
### Redis&trade; Cluster Common parameters
### Redis&reg; Cluster Common parameters
| Name | Description | Value |
| --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------- |
@@ -92,10 +92,10 @@ The command removes all the Kubernetes components associated with the chart and
| `diagnosticMode.enabled` | Enable diagnostic mode (all probes will be disabled and the command will be overridden) | `false` |
| `diagnosticMode.command` | Command to override all containers in the deployment | `["sleep"]` |
| `diagnosticMode.args` | Args to override all containers in the deployment | `["infinity"]` |
| `image.registry` | Redis&trade; cluster image registry | `docker.io` |
| `image.repository` | Redis&trade; cluster image repository | `bitnami/redis-cluster` |
| `image.tag` | Redis&trade; cluster image tag (immutable tags are recommended) | `6.2.7-debian-10-r22` |
| `image.pullPolicy` | Redis&trade; cluster image pull policy | `IfNotPresent` |
| `image.registry` | Redis&reg; cluster image registry | `docker.io` |
| `image.repository` | Redis&reg; cluster image repository | `bitnami/redis-cluster` |
| `image.tag` | Redis&reg; cluster image tag (immutable tags are recommended) | `6.2.7-debian-10-r22` |
| `image.pullPolicy` | Redis&reg; cluster image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
| `image.debug` | Enable image debug mode | `false` |
| `networkPolicy.enabled` | Enable NetworkPolicy | `false` |
@@ -108,7 +108,7 @@ The command removes all the Kubernetes components associated with the chart and
| `serviceAccount.automountServiceAccountToken` | Automount API credentials for a service account. | `false` |
| `rbac.create` | Specifies whether RBAC resources should be created | `false` |
| `rbac.role.rules` | Rules to create. It follows the role specification | `[]` |
| `podSecurityContext.enabled` | Enable Redis&trade; pod Security Context | `true` |
| `podSecurityContext.enabled` | Enable Redis&reg; pod Security Context | `true` |
| `podSecurityContext.fsGroup` | Group ID for the pods | `1001` |
| `podSecurityContext.runAsUser` | User ID for the pods | `1001` |
| `podSecurityContext.sysctls` | Set namespaced sysctls for the pods | `[]` |
@@ -119,7 +119,7 @@ The command removes all the Kubernetes components associated with the chart and
| `containerSecurityContext.runAsUser` | User ID for the containers. | `1001` |
| `containerSecurityContext.runAsNonRoot` | Run container as non root | `true` |
| `usePassword` | Use password authentication | `true` |
| `password` | Redis&trade; password (ignored if existingSecret set) | `""` |
| `password` | Redis&reg; password (ignored if existingSecret set) | `""` |
| `existingSecret` | Name of existing secret object (for password authentication) | `""` |
| `existingSecretPasswordKey` | Name of key containing password to be retrieved from the existing secret | `""` |
| `usePasswordFile` | Mount passwords as files instead of environment variables | `false` |
@@ -144,7 +144,7 @@ The command removes all the Kubernetes components associated with the chart and
| `service.externalTrafficPolicy` | Service external traffic policy | `Cluster` |
| `service.sessionAffinity` | Session Affinity for Kubernetes service, can be "None" or "ClientIP" | `None` |
| `service.sessionAffinityConfig` | Additional settings for the sessionAffinity | `{}` |
| `persistence.path` | Path to mount the volume at, to use other images Redis&trade; images. | `/bitnami/redis/data` |
| `persistence.path` | Path to mount the volume at, to use other images Redis&reg; images. | `/bitnami/redis/data` |
| `persistence.subPath` | The subdirectory of the volume to mount to, useful in dev environments and one PV for multiple services | `""` |
| `persistence.storageClass` | Storage class of backing PVC | `""` |
| `persistence.annotations` | Persistent Volume Claim annotations | `{}` |
@@ -163,67 +163,67 @@ The command removes all the Kubernetes components associated with the chart and
| `podSecurityPolicy.create` | Whether to create a PodSecurityPolicy. WARNING: PodSecurityPolicy is deprecated in Kubernetes v1.21 or later, unavailable in v1.25 or later | `false` |
### Redis&trade; statefulset parameters
### Redis&reg; statefulset parameters
| Name | Description | Value |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | --------------- |
| `redis.command` | Redis&trade; entrypoint string. The command `redis-server` is executed if this is not provided | `[]` |
| `redis.args` | Arguments for the provided command if needed | `[]` |
| `redis.updateStrategy.type` | Argo Workflows statefulset strategy type | `RollingUpdate` |
| `redis.updateStrategy.rollingUpdate.partition` | Partition update strategy | `0` |
| `redis.podManagementPolicy` | Statefulset Pod management policy, it needs to be Parallel to be able to complete the cluster join | `Parallel` |
| `redis.hostAliases` | Deployment pod host aliases | `[]` |
| `redis.hostNetwork` | Host networking requested for this pod. Use the host's network namespace. | `false` |
| `redis.useAOFPersistence` | Whether to use AOF Persistence mode or not | `yes` |
| `redis.containerPorts.redis` | Redis&trade; port | `6379` |
| `redis.containerPorts.bus` | The busPort should be obtained adding 10000 to the redisPort. By default: 10000 + 6379 = 16379 | `16379` |
| `redis.lifecycleHooks` | LifecycleHook to set additional configuration before or after startup. Evaluated as a template | `{}` |
| `redis.extraVolumes` | Extra volumes to add to the deployment | `[]` |
| `redis.extraVolumeMounts` | Extra volume mounts to add to the container | `[]` |
| `redis.customLivenessProbe` | Override default liveness probe | `{}` |
| `redis.customReadinessProbe` | Override default readiness probe | `{}` |
| `redis.customStartupProbe` | Custom startupProbe that overrides the default one | `{}` |
| `redis.initContainers` | Extra init containers to add to the deployment | `[]` |
| `redis.sidecars` | Extra sidecar containers to add to the deployment | `[]` |
| `redis.podLabels` | Additional labels for Redis&trade; pod | `{}` |
| `redis.priorityClassName` | Redis&trade; Master pod priorityClassName | `""` |
| `redis.configmap` | Additional Redis&trade; configuration for the nodes | `""` |
| `redis.extraEnvVars` | An array to add extra environment variables | `[]` |
| `redis.extraEnvVarsCM` | ConfigMap with extra environment variables | `""` |
| `redis.extraEnvVarsSecret` | Secret with extra environment variables | `""` |
| `redis.podAnnotations` | Redis&trade; additional annotations | `{}` |
| `redis.resources.limits` | The resources limits for the container | `{}` |
| `redis.resources.requests` | The requested resources for the container | `{}` |
| `redis.schedulerName` | Use an alternate scheduler, e.g. "stork". | `""` |
| `redis.shareProcessNamespace` | Enable shared process namespace in a pod. | `false` |
| `redis.livenessProbe.enabled` | Enable livenessProbe | `true` |
| `redis.livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `5` |
| `redis.livenessProbe.periodSeconds` | Period seconds for livenessProbe | `5` |
| `redis.livenessProbe.timeoutSeconds` | Timeout seconds for livenessProbe | `5` |
| `redis.livenessProbe.failureThreshold` | Failure threshold for livenessProbe | `5` |
| `redis.livenessProbe.successThreshold` | Success threshold for livenessProbe | `1` |
| `redis.readinessProbe.enabled` | Enable readinessProbe | `true` |
| `redis.readinessProbe.initialDelaySeconds` | Initial delay seconds for readinessProbe | `5` |
| `redis.readinessProbe.periodSeconds` | Period seconds for readinessProbe | `5` |
| `redis.readinessProbe.timeoutSeconds` | Timeout seconds for readinessProbe | `1` |
| `redis.readinessProbe.failureThreshold` | Failure threshold for readinessProbe | `5` |
| `redis.readinessProbe.successThreshold` | Success threshold for readinessProbe | `1` |
| `redis.startupProbe.enabled` | Enable startupProbe | `false` |
| `redis.startupProbe.path` | Path to check for startupProbe | `/` |
| `redis.startupProbe.initialDelaySeconds` | Initial delay seconds for startupProbe | `300` |
| `redis.startupProbe.periodSeconds` | Period seconds for startupProbe | `10` |
| `redis.startupProbe.timeoutSeconds` | Timeout seconds for startupProbe | `5` |
| `redis.startupProbe.failureThreshold` | Failure threshold for startupProbe | `6` |
| `redis.startupProbe.successThreshold` | Success threshold for startupProbe | `1` |
| `redis.podAffinityPreset` | Redis&trade; pod affinity preset. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `redis.podAntiAffinityPreset` | Redis&trade; pod anti-affinity preset. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard` | `soft` |
| `redis.nodeAffinityPreset.type` | Redis&trade; node affinity preset type. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `redis.nodeAffinityPreset.key` | Redis&trade; node label key to match Ignored if `redis.affinity` is set. | `""` |
| `redis.nodeAffinityPreset.values` | Redis&trade; node label values to match. Ignored if `redis.affinity` is set. | `[]` |
| `redis.affinity` | Affinity settings for Redis&trade; pod assignment | `{}` |
| `redis.nodeSelector` | Node labels for Redis&trade; pods assignment | `{}` |
| `redis.tolerations` | Tolerations for Redis&trade; pods assignment | `[]` |
| `redis.topologySpreadConstraints` | Pod topology spread constraints for Redis&trade; pod | `[]` |
| Name | Description | Value |
| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | --------------- |
| `redis.command` | Redis&reg; entrypoint string. The command `redis-server` is executed if this is not provided | `[]` |
| `redis.args` | Arguments for the provided command if needed | `[]` |
| `redis.updateStrategy.type` | Argo Workflows statefulset strategy type | `RollingUpdate` |
| `redis.updateStrategy.rollingUpdate.partition` | Partition update strategy | `0` |
| `redis.podManagementPolicy` | Statefulset Pod management policy, it needs to be Parallel to be able to complete the cluster join | `Parallel` |
| `redis.hostAliases` | Deployment pod host aliases | `[]` |
| `redis.hostNetwork` | Host networking requested for this pod. Use the host's network namespace. | `false` |
| `redis.useAOFPersistence` | Whether to use AOF Persistence mode or not | `yes` |
| `redis.containerPorts.redis` | Redis&reg; port | `6379` |
| `redis.containerPorts.bus` | The busPort should be obtained adding 10000 to the redisPort. By default: 10000 + 6379 = 16379 | `16379` |
| `redis.lifecycleHooks` | LifecycleHook to set additional configuration before or after startup. Evaluated as a template | `{}` |
| `redis.extraVolumes` | Extra volumes to add to the deployment | `[]` |
| `redis.extraVolumeMounts` | Extra volume mounts to add to the container | `[]` |
| `redis.customLivenessProbe` | Override default liveness probe | `{}` |
| `redis.customReadinessProbe` | Override default readiness probe | `{}` |
| `redis.customStartupProbe` | Custom startupProbe that overrides the default one | `{}` |
| `redis.initContainers` | Extra init containers to add to the deployment | `[]` |
| `redis.sidecars` | Extra sidecar containers to add to the deployment | `[]` |
| `redis.podLabels` | Additional labels for Redis&reg; pod | `{}` |
| `redis.priorityClassName` | Redis&reg; Master pod priorityClassName | `""` |
| `redis.configmap` | Additional Redis&reg; configuration for the nodes | `""` |
| `redis.extraEnvVars` | An array to add extra environment variables | `[]` |
| `redis.extraEnvVarsCM` | ConfigMap with extra environment variables | `""` |
| `redis.extraEnvVarsSecret` | Secret with extra environment variables | `""` |
| `redis.podAnnotations` | Redis&reg; additional annotations | `{}` |
| `redis.resources.limits` | The resources limits for the container | `{}` |
| `redis.resources.requests` | The requested resources for the container | `{}` |
| `redis.schedulerName` | Use an alternate scheduler, e.g. "stork". | `""` |
| `redis.shareProcessNamespace` | Enable shared process namespace in a pod. | `false` |
| `redis.livenessProbe.enabled` | Enable livenessProbe | `true` |
| `redis.livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `5` |
| `redis.livenessProbe.periodSeconds` | Period seconds for livenessProbe | `5` |
| `redis.livenessProbe.timeoutSeconds` | Timeout seconds for livenessProbe | `5` |
| `redis.livenessProbe.failureThreshold` | Failure threshold for livenessProbe | `5` |
| `redis.livenessProbe.successThreshold` | Success threshold for livenessProbe | `1` |
| `redis.readinessProbe.enabled` | Enable readinessProbe | `true` |
| `redis.readinessProbe.initialDelaySeconds` | Initial delay seconds for readinessProbe | `5` |
| `redis.readinessProbe.periodSeconds` | Period seconds for readinessProbe | `5` |
| `redis.readinessProbe.timeoutSeconds` | Timeout seconds for readinessProbe | `1` |
| `redis.readinessProbe.failureThreshold` | Failure threshold for readinessProbe | `5` |
| `redis.readinessProbe.successThreshold` | Success threshold for readinessProbe | `1` |
| `redis.startupProbe.enabled` | Enable startupProbe | `false` |
| `redis.startupProbe.path` | Path to check for startupProbe | `/` |
| `redis.startupProbe.initialDelaySeconds` | Initial delay seconds for startupProbe | `300` |
| `redis.startupProbe.periodSeconds` | Period seconds for startupProbe | `10` |
| `redis.startupProbe.timeoutSeconds` | Timeout seconds for startupProbe | `5` |
| `redis.startupProbe.failureThreshold` | Failure threshold for startupProbe | `6` |
| `redis.startupProbe.successThreshold` | Success threshold for startupProbe | `1` |
| `redis.podAffinityPreset` | Redis&reg; pod affinity preset. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `redis.podAntiAffinityPreset` | Redis&reg; pod anti-affinity preset. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard` | `soft` |
| `redis.nodeAffinityPreset.type` | Redis&reg; node affinity preset type. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `redis.nodeAffinityPreset.key` | Redis&reg; node label key to match Ignored if `redis.affinity` is set. | `""` |
| `redis.nodeAffinityPreset.values` | Redis&reg; node label values to match. Ignored if `redis.affinity` is set. | `[]` |
| `redis.affinity` | Affinity settings for Redis&reg; pod assignment | `{}` |
| `redis.nodeSelector` | Node labels for Redis&reg; pods assignment | `{}` |
| `redis.tolerations` | Tolerations for Redis&reg; pods assignment | `[]` |
| `redis.topologySpreadConstraints` | Pod topology spread constraints for Redis&reg; pod | `[]` |
### Cluster update job parameters
@@ -258,21 +258,21 @@ The command removes all the Kubernetes components associated with the chart and
### Cluster management parameters
| Name | Description | Value |
| --------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | -------------- |
| `cluster.init` | Enable the initialization of the Redis&trade; Cluster | `true` |
| `cluster.nodes` | The number of master nodes should always be >= 3, otherwise cluster creation will fail | `6` |
| `cluster.replicas` | Number of replicas for every master in the cluster | `1` |
| `cluster.externalAccess.enabled` | Enable access to the Redis | `false` |
| `cluster.externalAccess.service.type` | Type for the services used to expose every Pod | `LoadBalancer` |
| `cluster.externalAccess.service.port` | Port for the services used to expose every Pod | `6379` |
| `cluster.externalAccess.service.loadBalancerIP` | Array of load balancer IPs for each Redis&trade; node. Length must be the same as cluster.nodes | `[]` |
| `cluster.externalAccess.service.loadBalancerSourceRanges` | Service Load Balancer sources | `[]` |
| `cluster.externalAccess.service.annotations` | Annotations to add to the services used to expose every Pod of the Redis&trade; Cluster | `{}` |
| `cluster.update.addNodes` | Boolean to specify if you want to add nodes after the upgrade | `false` |
| `cluster.update.currentNumberOfNodes` | Number of currently deployed Redis&trade; nodes | `6` |
| `cluster.update.currentNumberOfReplicas` | Number of currently deployed Redis&trade; replicas | `1` |
| `cluster.update.newExternalIPs` | External IPs obtained from the services for the new nodes to add to the cluster | `[]` |
| Name | Description | Value |
| --------------------------------------------------------- | --------------------------------------------------------------------------------------------- | -------------- |
| `cluster.init` | Enable the initialization of the Redis&reg; Cluster | `true` |
| `cluster.nodes` | The number of master nodes should always be >= 3, otherwise cluster creation will fail | `6` |
| `cluster.replicas` | Number of replicas for every master in the cluster | `1` |
| `cluster.externalAccess.enabled` | Enable access to the Redis | `false` |
| `cluster.externalAccess.service.type` | Type for the services used to expose every Pod | `LoadBalancer` |
| `cluster.externalAccess.service.port` | Port for the services used to expose every Pod | `6379` |
| `cluster.externalAccess.service.loadBalancerIP` | Array of load balancer IPs for each Redis&reg; node. Length must be the same as cluster.nodes | `[]` |
| `cluster.externalAccess.service.loadBalancerSourceRanges` | Service Load Balancer sources | `[]` |
| `cluster.externalAccess.service.annotations` | Annotations to add to the services used to expose every Pod of the Redis&reg; Cluster | `{}` |
| `cluster.update.addNodes` | Boolean to specify if you want to add nodes after the upgrade | `false` |
| `cluster.update.currentNumberOfNodes` | Number of currently deployed Redis&reg; nodes | `6` |
| `cluster.update.currentNumberOfReplicas` | Number of currently deployed Redis&reg; replicas | `1` |
| `cluster.update.newExternalIPs` | External IPs obtained from the services for the new nodes to add to the cluster | `[]` |
### Metrics sidecar parameters
@@ -280,10 +280,10 @@ The command removes all the Kubernetes components associated with the chart and
| Name | Description | Value |
| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------ |
| `metrics.enabled` | Start a side-car prometheus exporter | `false` |
| `metrics.image.registry` | Redis&trade; exporter image registry | `docker.io` |
| `metrics.image.repository` | Redis&trade; exporter image name | `bitnami/redis-exporter` |
| `metrics.image.tag` | Redis&trade; exporter image tag | `1.37.0-debian-10-r62` |
| `metrics.image.pullPolicy` | Redis&trade; exporter image pull policy | `IfNotPresent` |
| `metrics.image.registry` | Redis&reg; exporter image registry | `docker.io` |
| `metrics.image.repository` | Redis&reg; exporter image name | `bitnami/redis-exporter` |
| `metrics.image.tag` | Redis&reg; exporter image tag | `1.37.0-debian-10-r62` |
| `metrics.image.pullPolicy` | Redis&reg; exporter image pull policy | `IfNotPresent` |
| `metrics.image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
| `metrics.resources` | Metrics exporter resource requests and limits | `{}` |
| `metrics.extraArgs` | Extra arguments for the binary; possible values [here](https://github.com/oliver006/redis_exporter | `{}` |
@@ -335,7 +335,7 @@ $ helm install my-release \
bitnami/redis-cluster
```
The above command sets the Redis&trade; server password to `secretpassword`.
The above command sets the Redis&reg; server password to `secretpassword`.
> NOTE: Once this chart is deployed, it is not possible to change the application's access credentials, such as usernames or passwords, using Helm. To change these application credentials after deployment, delete any persistent volumes (PVs) used by the chart and re-deploy it, or use the application's built-in administrative tools if available.
@@ -347,7 +347,7 @@ $ helm install my-release -f values.yaml bitnami/redis-cluster
> **Tip**: You can use the default [values.yaml](values.yaml)
> **Note for minikube users**: Current versions of minikube (v0.24.1 at the time of writing) provision `hostPath` persistent volumes that are only writable by root. Using chart defaults cause pod failure for the Redis&trade; pod as it attempts to write to the `/bitnami` directory. See minikube issue [1990](https://github.com/kubernetes/minikube/issues/1990) for more information.
> **Note for minikube users**: Current versions of minikube (v0.24.1 at the time of writing) provision `hostPath` persistent volumes that are only writable by root. Using chart defaults cause pod failure for the Redis&reg; pod as it attempts to write to the `/bitnami` directory. See minikube issue [1990](https://github.com/kubernetes/minikube/issues/1990) for more information.
## Configuration and installation details
@@ -357,7 +357,7 @@ It is strongly recommended to use immutable tags in a production environment. Th
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
### Use a different Redis&trade; version
### Use a different Redis&reg; version
To modify the application version used in this chart, specify a different version of the image using the `image.tag` parameter and/or a different repository using the `image.repository` parameter. Refer to the [chart documentation for more information on these parameters and how to use them with images from a private registry](https://docs.bitnami.com/kubernetes/infrastructure/redis-cluster/configuration/change-image-version/).
@@ -365,20 +365,20 @@ To modify the application version used in this chart, specify a different versio
To successfully set the cluster up, it will need to have at least 3 master nodes. The total number of nodes is calculated like- `nodes = numOfMasterNodes + numOfMasterNodes * replicas`. Hence, the defaults `cluster.nodes = 6` and `cluster.replicas = 1` means, 3 master and 3 replica nodes will be deployed by the chart.
By default the Redis&trade; Cluster is not accessible from outside the Kubernetes cluster, to access the Redis&trade; Cluster from outside you have to set `cluster.externalAccess.enabled=true` at deployment time. It will create in the first installation only 6 LoadBalancer services, one for each Redis&trade; node, once you have the external IPs of each service you will need to perform an upgrade passing those IPs to the `cluster.externalAccess.service.loadbalancerIP` array.
By default the Redis&reg; Cluster is not accessible from outside the Kubernetes cluster, to access the Redis&reg; Cluster from outside you have to set `cluster.externalAccess.enabled=true` at deployment time. It will create in the first installation only 6 LoadBalancer services, one for each Redis&reg; node, once you have the external IPs of each service you will need to perform an upgrade passing those IPs to the `cluster.externalAccess.service.loadbalancerIP` array.
The replicas will be read-only replicas of the masters. By default only one service is exposed (when not using the external access mode). You will connect your client to the exposed service, regardless you need to read or write. When a write operation arrives to a replica it will redirect the client to the proper master node. For example, using `redis-cli` you will need to provide the `-c` flag for `redis-cli` to follow the redirection automatically.
Using the external access mode, you can connect to any of the pods and the slaves will redirect the client in the same way as explained before, but the all the IPs will be public.
In case the master crashes, one of his slaves will be promoted to master. The slots stored by the crashed master will be unavailable until the slave finish the promotion. If a master and all his slaves crash, the cluster will be down until one of them is up again. To avoid downtime, it is possible to configure the number of Redis&trade; nodes with `cluster.nodes` and the number of replicas that will be assigned to each master with `cluster.replicas`. For example:
In case the master crashes, one of his slaves will be promoted to master. The slots stored by the crashed master will be unavailable until the slave finish the promotion. If a master and all his slaves crash, the cluster will be down until one of them is up again. To avoid downtime, it is possible to configure the number of Redis&reg; nodes with `cluster.nodes` and the number of replicas that will be assigned to each master with `cluster.replicas`. For example:
- `cluster.nodes=9` ( 3 master plus 2 replicas for each master)
- `cluster.replicas=2`
Providing the values above, the cluster will have 3 masters and, each master, will have 2 replicas.
> NOTE: By default `cluster.init` will be set to `true` in order to initialize the Redis&trade; Cluster in the first installation. If for testing purposes you only want to deploy or upgrade the nodes but avoiding the creation of the cluster you can set `cluster.init` to `false`.
> NOTE: By default `cluster.init` will be set to `true` in order to initialize the Redis&reg; Cluster in the first installation. If for testing purposes you only want to deploy or upgrade the nodes but avoiding the creation of the cluster you can set `cluster.init` to `false`.
#### Adding a new node to the cluster
@@ -400,7 +400,7 @@ The cluster will continue up while restarting pods one by one as the quorum is n
##### External Access
If you are using external access, to add a new node you will need to perform two upgrades. First upgrade the release to add a new Redis&trade; node and to get a LoadBalancerIP service. For example:
If you are using external access, to add a new node you will need to perform two upgrades. First upgrade the release to add a new Redis&reg; node and to get a LoadBalancerIP service. For example:
```
helm upgrade <release> --set "password=${REDIS_PASSWORD},cluster.externalAccess.enabled=true,cluster.externalAccess.service.type=LoadBalancer,cluster.externalAccess.service.loadBalancerIP[0]=<loadBalancerip-0>,cluster.externalAccess.service.loadBalancerIP[1]=<loadbalanacerip-1>,cluster.externalAccess.service.loadBalancerIP[2]=<loadbalancerip-2>,cluster.externalAccess.service.loadBalancerIP[3]=<loadbalancerip-3>,cluster.externalAccess.service.loadBalancerIP[4]=<loadbalancerip-4>,cluster.externalAccess.service.loadBalancerIP[5]=<loadbalancerip-5>,cluster.externalAccess.service.loadBalancerIP[6]=,cluster.nodes=7,cluster.init=false bitnami/redis-cluster
@@ -410,7 +410,7 @@ helm upgrade <release> --set "password=${REDIS_PASSWORD},cluster.externalAccess.
As we want to add a new node, we are setting `cluster.nodes=7` and we leave empty the LoadBalancerIP for the new node, so the cluster will provide the correct one.
`REDIS_PASSWORD` is the password obtained with the command that appears after the first installation of the Helm Chart.
At this point, you will have a new Redis&trade; Pod that will remain in `crashLoopBackOff` state until we provide the LoadBalancerIP for the new service.
At this point, you will have a new Redis&reg; Pod that will remain in `crashLoopBackOff` state until we provide the LoadBalancerIP for the new service.
Now, wait until the cluster provides the new LoadBalancerIP for the new service and perform the second upgrade:
```
@@ -419,11 +419,11 @@ helm upgrade <release> --set "password=${REDIS_PASSWORD},cluster.externalAccess.
Note we are providing the new IPs at `cluster.update.newExternalIPs`, the flag `cluster.update.addNodes=true` to enable the creation of the Job that adds a new node and now we are setting the LoadBalancerIP of the new service instead of leave it empty.
> NOTE: To avoid the creation of the Job that initializes the Redis&trade; Cluster again, you will need to provide `cluster.init=false`.
> NOTE: To avoid the creation of the Job that initializes the Redis&reg; Cluster again, you will need to provide `cluster.init=false`.
#### Scale down the cluster
To scale down the Redis&trade; Cluster, follow these steps:
To scale down the Redis&reg; Cluster, follow these steps:
First perform a normal upgrade setting the `cluster.nodes` value to the desired number of nodes. It should not be less than `6`. Also it is needed to provide the password using the `password`. For example, having more than 6 nodes, to scale down the cluster to 6 nodes:
@@ -433,7 +433,7 @@ helm upgrade --timeout 600s <release> --set "password=${REDIS_PASSWORD},cluster.
The cluster will continue working during the update as long as the quorum is not lost.
> NOTE: To avoid the creation of the Job that initializes the Redis&trade; Cluster again, you will need to provide `cluster.init=false`.
> NOTE: To avoid the creation of the Job that initializes the Redis&reg; Cluster again, you will need to provide `cluster.init=false`.
Once all the nodes are ready, get the list of nodes in the cluster using the `CLUSTER NODES` command. You will see references to the ones that were removed. Write down the node IDs of the nodes that show `fail`. In the following example the cluster scaled down from 8 to 6 nodes.
@@ -460,7 +460,7 @@ redis-cli -a $REDIS_PASSWORD CLUSTER FORGET d123b31560d4a32eabb10f1bf5e85e6f8f1d
```
### Using password file
To use a password file for Redis&trade; you need to create a secret containing the password.
To use a password file for Redis&reg; you need to create a secret containing the password.
> *NOTE*: It is important that the file with the password must be called `redis-password`
@@ -503,7 +503,7 @@ tls.certCAFilename="ca.pem"
### Sidecars and Init Containers
If you have a need for additional containers to run within the same pod as Redis&trade; (e.g. an additional metrics or logging exporter), you can do so via the `sidecars` config parameter. Simply define your container according to the Kubernetes container spec.
If you have a need for additional containers to run within the same pod as Redis&reg; (e.g. an additional metrics or logging exporter), you can do so via the `sidecars` config parameter. Simply define your container according to the Kubernetes container spec.
```yaml
sidecars:
@@ -544,7 +544,7 @@ Alternatively, you can use a ConfigMap or a Secret with the environment variable
The chart optionally can start a metrics exporter for [prometheus](https://prometheus.io). The metrics endpoint (port 9121) is exposed in the service. Metrics can be scraped from within the cluster using something similar as the described in the [example Prometheus scrape configuration](https://github.com/prometheus/prometheus/blob/master/documentation/examples/prometheus-kubernetes.yml). If metrics are to be scraped from outside the cluster, the Kubernetes API proxy can be utilized to access the endpoint.
### Host Kernel Settings
Redis&trade; may require some changes in the kernel of the host machine to work as expected, in particular increasing the `somaxconn` value and disabling transparent huge pages.
Redis&reg; may require some changes in the kernel of the host machine to work as expected, in particular increasing the `somaxconn` value and disabling transparent huge pages.
To do so, you can set up a privileged initContainer with the `sysctlImage` config values, for example:
```
sysctlImage:
@@ -571,7 +571,7 @@ Note that this will not disable transparent huge tables.
## Helm Upgrade
By default `cluster.init` will be set to `true` in order to initialize the Redis&trade; Cluster in the first installation. If for testing purposes you only want to deploy or upgrade the nodes but avoiding the creation of the cluster you can set `cluster.init` to `false`.
By default `cluster.init` will be set to `true` in order to initialize the Redis&reg; Cluster in the first installation. If for testing purposes you only want to deploy or upgrade the nodes but avoiding the creation of the cluster you can set `cluster.init` to `false`.
## Persistence
@@ -579,7 +579,7 @@ By default, the chart mounts a [Persistent Volume](https://kubernetes.io/docs/co
## NetworkPolicy
To enable network policy for Redis&trade;, install
To enable network policy for Redis&reg;, install
[a networking plugin that implements the Kubernetes NetworkPolicy spec](https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy#before-you-begin),
and set `networkPolicy.enabled` to `true`.
@@ -589,7 +589,7 @@ the DefaultDeny namespace annotation. Note: this will enforce policy for _all_ p
kubectl annotate namespace default "net.beta.kubernetes.io/network-policy={\"ingress\":{\"isolation\":\"DefaultDeny\"}}"
With NetworkPolicy enabled, only pods with the generated client label will be
able to connect to Redis&trade;. This label will be displayed in the output
able to connect to Redis&reg;. This label will be displayed in the output
after a successful install.
With `networkPolicy.ingressNSMatchLabels` pods from other namespaces can connect to redis. Set `networkPolicy.ingressNSPodMatchLabels` to match pod labels in matched namespace. For example, for a namespace labeled `redis=external` and pods in that namespace labeled `redis-client=true` the fields should be set:
@@ -634,7 +634,7 @@ As consequence, the `initJob` configuration section have been removed.
### To 5.0.0
This major version updates the Redis&trade; docker image version used from `6.0` to `6.2`, the new stable version. There are no major changes in the chart and there shouldn't be any breaking changes in it as `6.2` breaking changes center around some command and behaviour changes. For more information, please refer to [Redis&trade; 6.2 release notes](https://raw.githubusercontent.com/redis/redis/6.2/00-RELEASENOTES).
This major version updates the Redis&reg; docker image version used from `6.0` to `6.2`, the new stable version. There are no major changes in the chart and there shouldn't be any breaking changes in it as `6.2` breaking changes center around some command and behaviour changes. For more information, please refer to [Redis&reg; 6.2 release notes](https://raw.githubusercontent.com/redis/redis/6.2/00-RELEASENOTES).
### To 4.0.0
@@ -661,7 +661,7 @@ This major version updates the Redis&trade; docker image version used from `6.0`
### To 3.0.0
This version of the chart adapts the chart to the most recent Bitnami best practices and standards. Most of the Redis&trade; parameters were moved to the `redis` values section (such as extraEnvVars, sidecars, and so on). No major issues are expected during the upgrade.
This version of the chart adapts the chart to the most recent Bitnami best practices and standards. Most of the Redis&reg; parameters were moved to the `redis` values section (such as extraEnvVars, sidecars, and so on). No major issues are expected during the upgrade.
### To 2.0.0

14
bitnami/redis-cluster/templates/NOTES.txt
View File

@@ -34,13 +34,13 @@ To get your password run:
{{- if .Values.cluster.externalAccess.enabled }}
To connect to your Redis&trade; server from outside the cluster check the following information:
To connect to your Redis&reg; server from outside the cluster check the following information:
NOTE: It may take a few minutes for the LoadBalancer IP to be available.
Watch the status with: 'kubectl get svc --namespace {{ .Release.Namespace }} -w {{ template "common.names.fullname" . }}'
You will have a different external IP for each Redis&trade; node. Get the external ip from `-external` suffixed services: `kubectl get svc`.
Redis&trade; port: {{ .Values.cluster.externalAccess.service.port }}
You will have a different external IP for each Redis&reg; node. Get the external ip from `-external` suffixed services: `kubectl get svc`.
Redis&reg; port: {{ .Values.cluster.externalAccess.service.port }}
{{- if not .Values.cluster.externalAccess.service.loadBalancerIP }}
Once the LoadBalancerIPs are ready, you need to provide them and perform a Helm Upgrade:
@@ -60,15 +60,15 @@ To connect to your Redis&trade; server from outside the cluster check the follow
{{- else }}
You have deployed a Redis&trade; Cluster accessible only from within you Kubernetes Cluster.
You have deployed a Redis&reg; Cluster accessible only from within you Kubernetes Cluster.
{{- if .Values.cluster.init -}}
INFO: The Job to create the cluster will be created.
{{- end -}}
To connect to your Redis&trade; cluster:
To connect to your Redis&reg; cluster:
1. Run a Redis&trade; pod that you can use as a client:
1. Run a Redis&reg; pod that you can use as a client:
{{- if .Values.tls.enabled }}
kubectl run --namespace {{ .Release.Namespace }} {{ template "common.names.fullname" . }}-client --restart='Never' --env REDIS_PASSWORD=$REDIS_PASSWORD --image {{ template "redis-cluster.image" . }} --command -- sleep infinity
@@ -91,7 +91,7 @@ kubectl run --namespace {{ .Release.Namespace }} {{ template "common.names.fulln
--image {{ template "redis-cluster.image" . }} -- bash
{{- end }}
2. Connect using the Redis&trade; CLI:
2. Connect using the Redis&reg; CLI:
redis-cli -c -h {{ template "common.names.fullname" . }}{{ if .Values.usePassword }} -a $REDIS_PASSWORD{{ end }}{{ if .Values.tls.enabled }} --tls --cert /tmp/client.cert --key /tmp/client.key --cacert /tmp/CA.cert{{ end }}

12
bitnami/redis-cluster/templates/_helpers.tpl
View File

@@ -1,7 +1,7 @@
{{/* vim: set filetype=mustache: */}}
{{/*
Return the proper Redis&trade; image name
Return the proper Redis&reg; image name
*/}}
{{- define "redis-cluster.image" -}}
{{ include "common.images.image" (dict "imageRoot" .Values.image "global" .Values.global) }}
@@ -143,7 +143,7 @@ Get the password secret.
{{- end -}}
{{/*
Get the password key to be retrieved from Redis&trade; secret.
Get the password key to be retrieved from Redis&reg; secret.
*/}}
{{- define "redis-cluster.secretPasswordKey" -}}
{{- if and .Values.existingSecret .Values.existingSecretPasswordKey -}}
@@ -154,7 +154,7 @@ Get the password key to be retrieved from Redis&trade; secret.
{{- end -}}
{{/*
Return Redis&trade; password
Return Redis&reg; password
*/}}
{{- define "redis-cluster.password" -}}
{{- if not (empty .Values.global.redis.password) }}
@@ -200,7 +200,7 @@ Compile all warnings into a single message, and call fail.
{{- end -}}
{{- end -}}
{{/* Validate values of Redis&trade; Cluster - check update parameters */}}
{{/* Validate values of Redis&reg; Cluster - check update parameters */}}
{{- define "redis-cluster.validateValues.updateParameters" -}}
{{- if and .Values.cluster.update.addNodes ( or (and .Values.cluster.externalAccess.enabled .Values.cluster.externalAccess.service.loadBalancerIP) ( not .Values.cluster.externalAccess.enabled )) -}}
{{- if .Values.cluster.externalAccess.enabled }}
@@ -221,7 +221,7 @@ redis-cluster: currentNumberOfReplicas
{{- end -}}
{{- end -}}
{{/* Validate values of Redis&trade; Cluster - tls settings */}}
{{/* Validate values of Redis&reg; Cluster - tls settings */}}
{{- define "redis-cluster.validateValues.tlsParameters" -}}
{{- if and .Values.tls.enabled (not .Values.tls.autoGenerated) }}
{{- if and (not .Values.tls.existingSecret) (not .Values.tls.certificatesSecret) -}}
@@ -243,7 +243,7 @@ redis-cluster: TLSSecretMissingCertCA
{{- end -}}
{{- end -}}
{{/* Validate values of Redis&trade; - PodSecurityPolicy create */}}
{{/* Validate values of Redis&reg; - PodSecurityPolicy create */}}
{{- define "redis-cluster.validateValues.tls" -}}
{{- if and .Values.tls.enabled (not .Values.tls.autoGenerated) (not .Values.tls.existingSecret) (not .Values.tls.certificatesSecret) }}
redis-cluster: tls.enabled

110
bitnami/redis-cluster/values.yaml
View File

@@ -7,7 +7,7 @@
## @param global.imageRegistry Global Docker image registry
## @param global.imagePullSecrets Global Docker registry secret names as an array
## @param global.storageClass Global StorageClass for Persistent Volume(s)
## @param global.redis.password Redis&trade; password (overrides `password`)
## @param global.redis.password Redis&reg; password (overrides `password`)
##
global:
imageRegistry: ""
@@ -20,7 +20,7 @@ global:
redis:
password: ""
## @section Redis&trade; Cluster Common parameters
## @section Redis&reg; Cluster Common parameters
##
## @param nameOverride String to partially override common.names.fullname template (will maintain the release name)
@@ -57,19 +57,19 @@ diagnosticMode:
args:
- infinity
## Bitnami Redis&trade; image version
## Bitnami Redis&reg; image version
## ref: https://hub.docker.com/r/bitnami/redis/tags/
## @param image.registry Redis&trade; cluster image registry
## @param image.repository Redis&trade; cluster image repository
## @param image.tag Redis&trade; cluster image tag (immutable tags are recommended)
## @param image.pullPolicy Redis&trade; cluster image pull policy
## @param image.registry Redis&reg; cluster image registry
## @param image.repository Redis&reg; cluster image repository
## @param image.tag Redis&reg; cluster image tag (immutable tags are recommended)
## @param image.pullPolicy Redis&reg; cluster image pull policy
## @param image.pullSecrets Specify docker-registry secret names as an array
## @param image.debug Enable image debug mode
##
image:
registry: docker.io
repository: bitnami/redis-cluster
## Bitnami Redis&trade; image tag
## Bitnami Redis&reg; image tag
## ref: https://github.com/bitnami/bitnami-docker-redis#supported-tags-and-respective-dockerfile-links
##
tag: 6.2.7-debian-10-r22
@@ -98,8 +98,8 @@ image:
networkPolicy:
enabled: false
## When set to false, only pods with the correct
## client label will have network access to the port Redis&trade; is listening
## on. When true, Redis&trade; will accept connections from any source
## client label will have network access to the port Redis&reg; is listening
## on. When true, Redis&reg; will accept connections from any source
## (with the correct destination port).
##
allowExternal: true
@@ -138,8 +138,8 @@ rbac:
## - gce.unprivileged
##
rules: []
## Redis&trade; pod Security Context
## @param podSecurityContext.enabled Enable Redis&trade; pod Security Context
## Redis&reg; pod Security Context
## @param podSecurityContext.enabled Enable Redis&reg; pod Security Context
## @param podSecurityContext.fsGroup Group ID for the pods
## @param podSecurityContext.runAsUser User ID for the pods
## @param podSecurityContext.sysctls Set namespaced sysctls for the pods
@@ -177,7 +177,7 @@ containerSecurityContext:
## @param usePassword Use password authentication
##
usePassword: true
## @param password Redis&trade; password (ignored if existingSecret set)
## @param password Redis&reg; password (ignored if existingSecret set)
## Defaults to a random 10-character alphanumeric string if not set and usePassword is true
## ref: https://github.com/bitnami/bitnami-docker-redis#setting-the-server-password-on-first-run
##
@@ -222,7 +222,7 @@ tls:
## @param tls.dhParamsFilename File containing DH params (in order to support DH based ciphers)
##
dhParamsFilename: ""
## Redis&trade; Service properties for standalone mode.
## Redis&reg; Service properties for standalone mode.
##
service:
## @param service.ports.redis Kubernetes Redis service port
@@ -286,7 +286,7 @@ service:
## ref: https://kubernetes.io/docs/user-guide/persistent-volumes/
##
persistence:
## @param persistence.path Path to mount the volume at, to use other images Redis&trade; images.
## @param persistence.path Path to mount the volume at, to use other images Redis&reg; images.
##
path: /bitnami/redis/data
## @param persistence.subPath The subdirectory of the volume to mount to, useful in dev environments and one PV for multiple services
@@ -369,11 +369,11 @@ volumePermissions:
podSecurityPolicy:
create: false
## @section Redis&trade; statefulset parameters
## @section Redis&reg; statefulset parameters
##
redis:
## @param redis.command Redis&trade; entrypoint string. The command `redis-server` is executed if this is not provided
## @param redis.command Redis&reg; entrypoint string. The command `redis-server` is executed if this is not provided
##
command: []
## @param redis.args Arguments for the provided command if needed
@@ -411,7 +411,7 @@ redis:
## ref: https://redis.io/topics/cluster-tutorial#creating-and-using-a-redis-cluster
##
useAOFPersistence: "yes"
## @param redis.containerPorts.redis Redis&trade; port
## @param redis.containerPorts.redis Redis&reg; port
## @param redis.containerPorts.bus The busPort should be obtained adding 10000 to the redisPort. By default: 10000 + 6379 = 16379
##
containerPorts:
@@ -441,14 +441,14 @@ redis:
## @param redis.sidecars Extra sidecar containers to add to the deployment
##
sidecars: []
## @param redis.podLabels Additional labels for Redis&trade; pod
## @param redis.podLabels Additional labels for Redis&reg; pod
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
##
podLabels: {}
## @param redis.priorityClassName Redis&trade; Master pod priorityClassName
## @param redis.priorityClassName Redis&reg; Master pod priorityClassName
##
priorityClassName: ""
## @param redis.configmap Additional Redis&trade; configuration for the nodes
## @param redis.configmap Additional Redis&reg; configuration for the nodes
## ref: https://redis.io/topics/config
##
configmap: ""
@@ -464,11 +464,11 @@ redis:
## @param redis.extraEnvVarsSecret Secret with extra environment variables
##
extraEnvVarsSecret: ""
## @param redis.podAnnotations Redis&trade; additional annotations
## @param redis.podAnnotations Redis&reg; additional annotations
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
##
podAnnotations: {}
## Redis&trade; resource requests and limits
## Redis&reg; resource requests and limits
## ref: https://kubernetes.io/docs/user-guide/compute-resources/
## @param redis.resources.limits The resources limits for the container
## @param redis.resources.requests The requested resources for the container
@@ -498,7 +498,7 @@ redis:
## Ref: https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/
##
shareProcessNamespace: false
## Configure extra options for Redis&trade; liveness probes
## Configure extra options for Redis&reg; liveness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
## @param redis.livenessProbe.enabled Enable livenessProbe
## @param redis.livenessProbe.initialDelaySeconds Initial delay seconds for livenessProbe
@@ -514,7 +514,7 @@ redis:
timeoutSeconds: 5
successThreshold: 1
failureThreshold: 5
## Configure extra options for Redis&trade; readiness probes
## Configure extra options for Redis&reg; readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
## @param redis.readinessProbe.enabled Enable readinessProbe
## @param redis.readinessProbe.initialDelaySeconds Initial delay seconds for readinessProbe
@@ -546,47 +546,47 @@ redis:
timeoutSeconds: 5
failureThreshold: 6
successThreshold: 1
## @param redis.podAffinityPreset Redis&trade; pod affinity preset. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard`
## @param redis.podAffinityPreset Redis&reg; pod affinity preset. Ignored if `redis.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 redis.podAntiAffinityPreset Redis&trade; pod anti-affinity preset. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard`
## @param redis.podAntiAffinityPreset Redis&reg; pod anti-affinity preset. Ignored if `redis.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
## Redis&trade; node affinity preset
## Redis&reg; node affinity preset
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity
##
nodeAffinityPreset:
## @param redis.nodeAffinityPreset.type Redis&trade; node affinity preset type. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard`
## @param redis.nodeAffinityPreset.type Redis&reg; node affinity preset type. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard`
##
type: ""
## @param redis.nodeAffinityPreset.key Redis&trade; node label key to match Ignored if `redis.affinity` is set.
## @param redis.nodeAffinityPreset.key Redis&reg; node label key to match Ignored if `redis.affinity` is set.
## E.g.
## key: "kubernetes.io/e2e-az-name"
##
key: ""
## @param redis.nodeAffinityPreset.values Redis&trade; node label values to match. Ignored if `redis.affinity` is set.
## @param redis.nodeAffinityPreset.values Redis&reg; node label values to match. Ignored if `redis.affinity` is set.
## E.g.
## values:
## - e2e-az1
## - e2e-az2
##
values: []
## @param redis.affinity Affinity settings for Redis&trade; pod assignment
## @param redis.affinity Affinity settings for Redis&reg; pod assignment
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
## Note: redis.podAffinityPreset, redis.podAntiAffinityPreset, and redis.nodeAffinityPreset will be ignored when it's set
##
affinity: {}
## @param redis.nodeSelector Node labels for Redis&trade; pods assignment
## @param redis.nodeSelector Node labels for Redis&reg; pods assignment
## ref: https://kubernetes.io/docs/user-guide/node-selection/
##
nodeSelector: {}
## @param redis.tolerations Tolerations for Redis&trade; pods assignment
## @param redis.tolerations Tolerations for Redis&reg; pods assignment
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
##
tolerations: []
## @param redis.topologySpreadConstraints Pod topology spread constraints for Redis&trade; pod
## @param redis.topologySpreadConstraints Pod topology spread constraints for Redis&reg; pod
## https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/
## The value is evaluated as a template
##
@@ -711,13 +711,13 @@ updateJob:
## @section Cluster management parameters
##
## Redis&trade; Cluster settings
## Redis&reg; Cluster settings
##
cluster:
## @param cluster.init Enable the initialization of the Redis&trade; Cluster
## @param cluster.init Enable the initialization of the Redis&reg; Cluster
##
init: true
## Number of Redis&trade; nodes to be deployed
## Number of Redis&reg; nodes to be deployed
##
## Note:
## This is total number of nodes including the replicas. Meaning there will be 3 master and 3 replica
@@ -732,7 +732,7 @@ cluster:
## 1 means that we want a replica for every master created
##
replicas: 1
## Configuration to access the Redis&trade; Cluster from outside the Kubernetes cluster
## Configuration to access the Redis&reg; Cluster from outside the Kubernetes cluster
##
externalAccess:
## @param cluster.externalAccess.enabled Enable access to the Redis
@@ -746,7 +746,7 @@ cluster:
## @param cluster.externalAccess.service.port Port for the services used to expose every Pod
##
port: 6379
## @param cluster.externalAccess.service.loadBalancerIP Array of load balancer IPs for each Redis&trade; node. Length must be the same as cluster.nodes
## @param cluster.externalAccess.service.loadBalancerIP Array of load balancer IPs for each Redis&reg; node. Length must be the same as cluster.nodes
##
loadBalancerIP: []
## @param cluster.externalAccess.service.loadBalancerSourceRanges Service Load Balancer sources
@@ -756,20 +756,20 @@ cluster:
## - 10.10.10.0/24
##
loadBalancerSourceRanges: []
## @param cluster.externalAccess.service.annotations Annotations to add to the services used to expose every Pod of the Redis&trade; Cluster
## @param cluster.externalAccess.service.annotations Annotations to add to the services used to expose every Pod of the Redis&reg; Cluster
##
annotations: {}
## This section allows to update the Redis&trade; cluster nodes.
## This section allows to update the Redis&reg; cluster nodes.
##
update:
## @param cluster.update.addNodes Boolean to specify if you want to add nodes after the upgrade
## Setting this to true a hook will add nodes to the Redis&trade; cluster after the upgrade. currentNumberOfNodes and currentNumberOfReplicas is required
## Setting this to true a hook will add nodes to the Redis&reg; cluster after the upgrade. currentNumberOfNodes and currentNumberOfReplicas is required
##
addNodes: false
## @param cluster.update.currentNumberOfNodes Number of currently deployed Redis&trade; nodes
## @param cluster.update.currentNumberOfNodes Number of currently deployed Redis&reg; nodes
##
currentNumberOfNodes: 6
## @param cluster.update.currentNumberOfReplicas Number of currently deployed Redis&trade; replicas
## @param cluster.update.currentNumberOfReplicas Number of currently deployed Redis&reg; replicas
##
currentNumberOfReplicas: 1
## @param cluster.update.newExternalIPs External IPs obtained from the services for the new nodes to add to the cluster
@@ -785,10 +785,10 @@ metrics:
## @param metrics.enabled Start a side-car prometheus exporter
##
enabled: false
## @param metrics.image.registry Redis&trade; exporter image registry
## @param metrics.image.repository Redis&trade; exporter image name
## @param metrics.image.tag Redis&trade; exporter image tag
## @param metrics.image.pullPolicy Redis&trade; exporter image pull policy
## @param metrics.image.registry Redis&reg; exporter image registry
## @param metrics.image.repository Redis&reg; exporter image name
## @param metrics.image.tag Redis&reg; exporter image tag
## @param metrics.image.pullPolicy Redis&reg; exporter image pull policy
## @param metrics.image.pullSecrets Specify docker-registry secret names as an array
##
image:
@@ -883,8 +883,8 @@ metrics:
## labels:
## severity: error
## annotations:
## summary: Redis&trade; instance {{ "{{ $instance }}" }} down
## description: Redis&trade; instance {{ "{{ $instance }}" }} is down.
## summary: Redis&reg; instance {{ "{{ $instance }}" }} down
## description: Redis&reg; instance {{ "{{ $instance }}" }} is down.
## - alert: RedisMemoryHigh
## expr: >
## redis_memory_used_bytes{service="{{ template "common.names.fullname" . }}-metrics"} * 100
@@ -895,16 +895,16 @@ metrics:
## labels:
## severity: error
## annotations:
## summary: Redis&trade; instance {{ "{{ $instance }}" }} is using too much memory
## description: Redis&trade; instance {{ "{{ $instance }}" }} is using {{ "{{ $value }}" }}% of its available memory.
## summary: Redis&reg; instance {{ "{{ $instance }}" }} is using too much memory
## description: Redis&reg; instance {{ "{{ $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&trade; instance {{ "{{ $instance }}" }} has evicted keys
## description: Redis&trade; instance {{ "{{ $instance }}" }} has evicted {{ "{{ $value }}" }} keys in the last 5 minutes.
## summary: Redis&reg; instance {{ "{{ $instance }}" }} has evicted keys
## description: Redis&reg; instance {{ "{{ $instance }}" }} has evicted {{ "{{ $value }}" }} keys in the last 5 minutes.
##
rules: []
## @param metrics.priorityClassName Metrics exporter pod priorityClassName