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

[bitnami/several] Add Redis trademark (#5023)

Browse Source 
* Add trademark to Redis and Redis Cluster

* add trademark in other charts

* Fix table indentation in READMEs

* Add trademark to yaml, tpl and txt

* Rebase master and bump chart version

* One line disclaimer

* Add trademark to recent changes and add zookeeper and cassandra

Co-authored-by: jotamartos <jotamartos@vmware.com>
This commit is contained in:
Carlos Rodríguez Hernández
2021-01-14 14:36:32 +01:00
committed by GitHub
parent 7db6b65bb5
commit dfa89b8659
35 changed files with 548 additions and 536 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
bitnami/airflow/Chart.yaml
View File

@@ -32,4 +32,4 @@ name: airflow
sources:
- https://github.com/bitnami/bitnami-docker-airflow
- https://airflow.apache.org/
version: 7.1.2
version: 7.1.3

16
bitnami/airflow/README.md
View File

@@ -240,19 +240,19 @@ The following tables lists the configurable parameters of the Airflow chart and
| `externalDatabase.password` | External PostgreSQL password | `nil` |
| `externalDatabase.port` | External PostgreSQL port | `nil` |
| `externalDatabase.user` | External PostgreSQL user | `nil` |
| `externalRedis.existingSecret` | Name of an existing secret containing the Redis password ('redis-password' key) | `nil` |
| `externalRedis.host` | External Redis host | `nil` |
| `externalRedis.password` | External Redis password | `nil` |
| `externalRedis.port` | External Redis port | `nil` |
| `externalRedis.username` | External Redis username (not required on most Redis implementations) | `nil` |
| `externalRedis.existingSecret` | Name of an existing secret containing the Redis<sup>TM</sup> password ('redis-password' key) | `nil` |
| `externalRedis.host` | External Redis<sup>TM</sup> host | `nil` |
| `externalRedis.password` | External Redis<sup>TM</sup> password | `nil` |
| `externalRedis.port` | External Redis<sup>TM</sup> port | `nil` |
| `externalRedis.username` | External Redis<sup>TM</sup> username (not required on most Redis<sup>TM</sup> implementations) | `nil` |
| `postgresql.enabled` | Switch to enable or disable the PostgreSQL helm chart | `true` |
| `postgresql.existingSecret` | Name of an existing secret containing the PostgreSQL password ('postgresql-password' key) . This secret is used in case of postgresql.enabled=true and we would like to specify password for newly created postgresql instance | `nil` |
| `postgresql.postgresqlDatabase` | Airflow Postgresql database | `bitnami_airflow` |
| `postgresql.postgresqlPassword` | Airflow Postgresql password | `nil` |
| `postgresql.postgresqlUsername` | Airflow Postgresql username | `bn_airflow` |
| `redis.cluster.enabled` | Switch to enable a clustered redis | `false` |
| `redis.enabled` | Switch to enable or disable the Redis helm chart | `true` |
| `redis.existingSecret` | Name of an existing secret containing the Redis password ('redis-password' key) . This secret is used in case of redis.enabled=true and we would like to specify password for newly created redis instance | `nil` |
| `redis.enabled` | Switch to enable or disable the Redis<sup>TM</sup> helm chart | `true` |
| `redis.existingSecret` | Name of an existing secret containing the Redis<sup>TM</sup> password ('redis-password' key) . This secret is used in case of redis.enabled=true and we would like to specify password for newly created redis instance | `nil` |
### Airflow exposing parameters
@@ -445,7 +445,7 @@ git.plugins.repositories[0].path=plugins
### Existing Secrets
You can use an existing secret to configure your Airflow auth, external Postgres, and extern Redis passwords:
You can use an existing secret to configure your Airflow auth, external Postgres, and extern Redis<sup>TM</sup> passwords:
```console
postgresql.enabled=false

2
bitnami/airflow/templates/_helpers.tpl
View File

@@ -120,7 +120,7 @@ We truncate at 63 chars because some Kubernetes name fields are limited to this
{{- end -}}
{{/*
Get the Redis credentials secret.
Get the Redis(TM) credentials secret.
*/}}
{{- define "airflow.redis.secretName" -}}
{{- if and (.Values.redis.enabled) (not .Values.redis.existingSecret) -}}

14
bitnami/airflow/values-production.yaml
View File

@@ -854,7 +854,7 @@ externalDatabase:
port: 5432
##
## Redis chart configuration
## Redis(TM) chart configuration
##
## https://github.com/bitnami/charts/blob/master/bitnami/redis/values.yaml
##
@@ -871,20 +871,20 @@ redis:
externalRedis:
## All of these values are only used when redis.enabled is set to false
## Redis host
## Redis(TM) host
##
host: localhost
## Redis port number
## Redis(TM) port number
##
port: 6379
## Redis password
## Redis(TM) password
##
password:
## Name of an existing secret resource containing the Redis password in a 'redis-password' key
## Name of an existing secret resource containing the Redis(TM) password in a 'redis-password' key
##
existingSecret:
## Redis username
## Most Redis implementnations do not require a username to authenticate
## Redis(TM) username
## Most Redis(TM) implementnations do not require a username to authenticate
## and it should be enough with the password
##
username:

14
bitnami/airflow/values.yaml
View File

@@ -858,7 +858,7 @@ externalDatabase:
port: 5432
##
## Redis chart configuration
## Redis(TM) chart configuration
##
## https://github.com/bitnami/charts/blob/master/bitnami/redis/values.yaml
##
@@ -875,20 +875,20 @@ redis:
externalRedis:
## All of these values are only used when redis.enabled is set to false
## Redis host
## Redis(TM) host
##
host: localhost
## Redis port number
## Redis(TM) port number
##
port: 6379
## Redis password
## Redis(TM) password
##
password:
## Name of an existing secret resource containing the Redis password in a 'redis-password' key
## Name of an existing secret resource containing the Redis(TM) password in a 'redis-password' key
##
existingSecret:
## Redis username
## Most Redis implementnations do not require a username to authenticate
## Redis(TM) username
## Most Redis(TM) implementnations do not require a username to authenticate
## and it should be enough with the password
##
username:

2
bitnami/cassandra/Chart.yaml
View File

@@ -23,4 +23,4 @@ name: cassandra
sources:
- https://github.com/bitnami/bitnami-docker-cassandra
- http://cassandra.apache.org
version: 7.1.3
version: 7.1.4

4
bitnami/cassandra/values-production.yaml
View File

@@ -423,8 +423,8 @@ networkPolicy:
enabled: true
## The Policy model to apply. When set to false, only pods with the correct
## client label will have network access to the port Redis is listening
## on. When true, Redis will accept connections from any source
## client label will have network access to the port Redis(TM) is listening
## on. When true, Redis(TM) will accept connections from any source
## (with the correct destination port).
##
# allowExternal: true

4
bitnami/cassandra/values.yaml
View File

@@ -423,8 +423,8 @@ networkPolicy:
enabled: false
## The Policy model to apply. When set to false, only pods with the correct
## client label will have network access to the port Redis is listening
## on. When true, Redis will accept connections from any source
## client label will have network access to the port Redis(TM) is listening
## on. When true, Redis(TM) will accept connections from any source
## (with the correct destination port).
##
# allowExternal: true

4
bitnami/common/Chart.yaml
View File

@@ -2,7 +2,7 @@ annotations:
category: Infrastructure
apiVersion: v2
# Please make sure that version and appVersion are always the same.
appVersion: 1.3.2
appVersion: 1.3.3
description: A Library Helm Chart for grouping common logic between bitnami charts. This chart is not deployable by itself.
home: https://github.com/bitnami/charts/tree/master/bitnami/common
icon: https://bitnami.com/downloads/logos/bitnami-mark.png
@@ -20,4 +20,4 @@ sources:
- https://github.com/bitnami/charts
- http://www.bitnami.com/
type: library
version: 1.3.2
version: 1.3.3

18
bitnami/common/README.md
View File

@@ -120,15 +120,15 @@ The following table lists the helpers available in the library which are scoped
### Validations
| Helper identifier | Description | Expected Input |
|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `common.validations.values.single.empty` | Validate a value must not be empty. | `dict "valueKey" "path.to.value" "secret" "secret.name" "field" "my-password" "context" $` secret and field are optional. In case they are given, the helper will generate a how to get instruction. See [ValidateValue](#validatevalue) |
| `common.validations.values.multiple.empty` | Validate a multiple values must not be empty. It returns a shared error for all the values. | `dict "required" (list $validateValueConf00 $validateValueConf01) "context" $`. See [ValidateValue](#validatevalue) |
| `common.validations.values.mariadb.passwords` | This helper will ensure required password for MariaDB are not empty. It returns a shared error for all the values. | `dict "secret" "mariadb-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use mariadb chart and the helper. |
| `common.validations.values.postgresql.passwords` | This helper will ensure required password for PostgreSQL are not empty. It returns a shared error for all the values. | `dict "secret" "postgresql-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use postgresql chart and the helper. |
| `common.validations.values.redis.passwords` | This helper will ensure required password for Redis are not empty. It returns a shared error for all the values. | `dict "secret" "redis-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use redis chart and the helper. |
| `common.validations.values.cassandra.passwords` | This helper will ensure required password for Cassandra are not empty. It returns a shared error for all the values. | `dict "secret" "cassandra-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use cassandra chart and the helper. |
| `common.validations.values.mongodb.passwords` | This helper will ensure required password for MongoDB are not empty. It returns a shared error for all the values. | `dict "secret" "mongodb-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use mongodb chart and the helper. |
| Helper identifier | Description | Expected Input |
|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `common.validations.values.single.empty` | Validate a value must not be empty. | `dict "valueKey" "path.to.value" "secret" "secret.name" "field" "my-password" "context" $` secret and field are optional. In case they are given, the helper will generate a how to get instruction. See [ValidateValue](#validatevalue) |
| `common.validations.values.multiple.empty` | Validate a multiple values must not be empty. It returns a shared error for all the values. | `dict "required" (list $validateValueConf00 $validateValueConf01) "context" $`. See [ValidateValue](#validatevalue) |
| `common.validations.values.mariadb.passwords` | This helper will ensure required password for MariaDB are not empty. It returns a shared error for all the values. | `dict "secret" "mariadb-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use mariadb chart and the helper. |
| `common.validations.values.postgresql.passwords` | This helper will ensure required password for PostgreSQL are not empty. It returns a shared error for all the values. | `dict "secret" "postgresql-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use postgresql chart and the helper. |
| `common.validations.values.redis.passwords` | This helper will ensure required password for Redis<sup>TM</sup> are not empty. It returns a shared error for all the values. | `dict "secret" "redis-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use redis chart and the helper. |
| `common.validations.values.cassandra.passwords` | This helper will ensure required password for Cassandra are not empty. It returns a shared error for all the values. | `dict "secret" "cassandra-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use cassandra chart and the helper. |
| `common.validations.values.mongodb.passwords` | This helper will ensure required password for MongoDB are not empty. It returns a shared error for all the values. | `dict "secret" "mongodb-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use mongodb chart and the helper. |
### Warnings

4
bitnami/common/templates/validations/_redis.tpl
View File

@@ -1,7 +1,7 @@
{{/* vim: set filetype=mustache: */}}
{{/*
Validate Redis required passwords are not empty.
Validate Redis(TM) required passwords are not empty.
Usage:
{{ include "common.validations.values.redis.passwords" (dict "secret" "secretName" "subchart" false "context" $) }}
@@ -35,7 +35,7 @@ Redis Auxiliary function to get the right value for existingSecret.
Usage:
{{ include "common.redis.values.existingSecret" (dict "context" $) }}
Params:
- subchart - Boolean - Optional. Whether Redis is used as subchart or not. Default: false
- subchart - Boolean - Optional. Whether Redis(TM) is used as subchart or not. Default: false
*/}}
{{- define "common.redis.values.existingSecret" -}}
{{- if .subchart -}}

2
bitnami/discourse/Chart.yaml
View File

@@ -32,4 +32,4 @@ sources:
- https://github.com/bitnami/bitnami-docker-discourse
- https://github.com/spinnaker
- https://www.discourse.org/
version: 2.1.1
version: 2.1.2

40
bitnami/discourse/README.md
View File

@@ -13,7 +13,7 @@ $ helm install my-release bitnami/discourse
This chart bootstraps a [Discourse](https://www.discourse.org/) deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
It also packages [Bitnami Postgresql](https://github.com/bitnami/charts/tree/master/bitnami/postgresql) and [Bitnami Redis](https://github.com/bitnami/charts/tree/master/bitnami/redis) which are required as databases for the Discourse application.
It also packages [Bitnami Postgresql](https://github.com/bitnami/charts/tree/master/bitnami/postgresql) and [Bitnami Redis<sup>TM</sup>](https://github.com/bitnami/charts/tree/master/bitnami/redis) which are required as databases for the Discourse application.
Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment and management of Helm Charts in clusters.
@@ -209,22 +209,22 @@ The following table lists the configurable parameters of the Discourse chart and
| `externalDatabase.existingSecret` | Name of an existing Kubernetes secret. The secret must have the following keys configured: `postgresql-postgres-password`, `postgresql-password` | `nil` |
| `externalDatabase.database` | Name of the existing database (when using an external db) | `bitnami_application` |
### Redis parameters
### Redis<sup>TM</sup> parameters
| Parameter | Description | Default |
|-------------------------------------------|----------------------------------------------------------------------------|------------------|
| `redis.enabled` | Deploy Redis container(s) | `true` |
| `redis.usePassword` | Use password authentication | `false` |
| `redis.password` | Password for Redis authentication - ignored if existingSecret is provided | `nil` |
| `redis.existingSecret` | Name of an existing Kubernetes secret | `nil` |
| `redis.existingSecretPasswordKey` | Name of the key pointing to the password in your Kubernetes secret | `redis-password` |
| `redis.cluster.enabled` | Whether to use cluster replication | `false` |
| `redis.master.persistence.enabled` | Enable database persistence using PVC | `true` |
| `externalRedis.host` | Host of the external database | `""` |
| `externalRedis.port` | Database port number | `6379` |
| `externalRedis.password` | Password for the external Redis | `nil` |
| `externalRedis.existingSecret` | Name of an existing Kubernetes secret | `nil` |
| `externalRedis.existingSecretPasswordKey` | Name of the key pointing to the password in your Kubernetes secret | `redis-password` |
| Parameter | Description | Default |
|-------------------------------------------|-----------------------------------------------------------------------------------------|------------------|
| `redis.enabled` | Deploy Redis<sup>TM</sup> container(s) | `true` |
| `redis.usePassword` | Use password authentication | `false` |
| `redis.password` | Password for Redis<sup>TM</sup> authentication - ignored if existingSecret is provided | `nil` |
| `redis.existingSecret` | Name of an existing Kubernetes secret | `nil` |
| `redis.existingSecretPasswordKey` | Name of the key pointing to the password in your Kubernetes secret | `redis-password` |
| `redis.cluster.enabled` | Whether to use cluster replication | `false` |
| `redis.master.persistence.enabled` | Enable database persistence using PVC | `true` |
| `externalRedis.host` | Host of the external database | `""` |
| `externalRedis.port` | Database port number | `6379` |
| `externalRedis.password` | Password for the external Redis<sup>TM</sup> | `nil` |
| `externalRedis.existingSecret` | Name of an existing Kubernetes secret | `nil` |
| `externalRedis.existingSecretPasswordKey` | Name of the key pointing to the password in your Kubernetes secret | `redis-password` |
The above parameters map to the env variables defined in [bitnami/discourse](http://github.com/bitnami/bitnami-docker-discourse). For more information please refer to the [bitnami/discourse](http://github.com/bitnami/bitnami-docker-discourse) image documentation.
@@ -303,7 +303,7 @@ This chart includes a `values-production.yaml` file where you can find some para
+ service.externalTrafficPolicy: Local
```
- Make Redis use password for auth:
- Make Redis<sup>TM</sup> use password for auth:
```diff
- redis.usePassword: false
@@ -368,7 +368,7 @@ Note also that if you disable PostgreSQL per above you MUST supply values for th
In case the database already contains data from a previous Discourse installation, you need to set the `discourse.skipInstall` parameter to _true_. Otherwise, the container would execute the installation wizard and could modify the existing data in the database. This parameter force the container to not execute the Discourse installation wizard.
Similarly, you can specify an external Redis instance rather than installing one inside your cluster. First, you may disable the Redis installation with the `redis.enabled` option. As aforementioned, used the provided parameters to provide data about your instance:
Similarly, you can specify an external Redis<sup>TM</sup> instance rather than installing one inside your cluster. First, you may disable the Redis<sup>TM</sup> installation with the `redis.enabled` option. As aforementioned, used the provided parameters to provide data about your instance:
```console
redis.enabled=false
@@ -539,7 +539,7 @@ postgresql 08:05:12.59 INFO ==> Deploying PostgreSQL with persisted data...
This new major version includes the following changes:
* PostgreSQL dependency version was bumped to a new major version `9.X.X`, which includes changes that do no longer guarantee backwards compatibility. Check [PostgreSQL Upgrading Notes](https://github.com/bitnami/charts/tree/master/bitnami/postgresql#900) for more information.
* Redis dependency version was bumped to a new major version `11.X.X`, which includes breaking changes regarding sentinel. Discourse does not use this type of setup, so no issues are expected to happen in this case. Check [Redis Upgrading Notes](https://github.com/bitnami/charts/tree/master/bitnami/redis#to-1100) for more information.
* Redis<sup>TM</sup> dependency version was bumped to a new major version `11.X.X`, which includes breaking changes regarding sentinel. Discourse does not use this type of setup, so no issues are expected to happen in this case. Check [Redis<sup>TM</sup> Upgrading Notes](https://github.com/bitnami/charts/tree/master/bitnami/redis#to-1100) for more information.
* Some non-breaking changes so as to use the `bitnami/common` library chart.
As a consequence, backwards compatibility from previous versions is not guaranteed during the upgrade. To upgrade to this new version `1.0.0` there are two alternatives:
@@ -572,7 +572,7 @@ As a consequence, backwards compatibility from previous versions is not guarante
$ export POSTGRESQL_PASSWORD=$(kubectl get secret --namespace default discourse-postgresql -o jsonpath="{.data.postgresql-password}" | base64 --decode)
```
> NOTE: You will need to export Redis credentials as well if your setup makes use of them.
> NOTE: You will need to export Redis<sup>TM</sup> credentials as well if your setup makes use of them.
3. Scale down the Discourse deployment and delete the PostgreSQL statefulset. Notice the option `--cascade=false` in the latter.

12
bitnami/discourse/templates/_helpers.tpl
View File

@@ -150,7 +150,7 @@ Return the Postgresql secret name
{{- end -}}
{{/*
Return the Redis hostname
Return the Redis(TM) hostname
*/}}
{{- define "discourse.redisHost" -}}
{{- if .Values.redis.enabled }}
@@ -161,7 +161,7 @@ Return the Redis hostname
{{- end -}}
{{/*
Return the Redis port
Return the Redis(TM) port
*/}}
{{- define "discourse.redisPort" -}}
{{- if .Values.redis.enabled }}
@@ -172,7 +172,7 @@ Return the Redis port
{{- end -}}
{{/*
Return true if a secret object for Redis should be created
Return true if a secret object for Redis(TM) should be created
*/}}
{{- define "discourse.redis.createSecret" -}}
{{- if and (not .Values.redis.enabled) (not .Values.externalRedis.existingSecret) .Values.externalRedis.password }}
@@ -181,7 +181,7 @@ Return true if a secret object for Redis should be created
{{- end -}}
{{/*
Return the Redis secret name
Return the Redis(TM) secret name
*/}}
{{- define "discourse.redis.secretName" -}}
{{- if .Values.redis.enabled }}
@@ -198,7 +198,7 @@ Return the Redis secret name
{{- end -}}
{{/*
Return the Redis secret key
Return the Redis(TM) secret key
*/}}
{{- define "discourse.redis.secretPasswordKey" -}}
{{- if and .Values.redis.enabled .Values.redis.existingSecret }}
@@ -211,7 +211,7 @@ Return the Redis secret key
{{- end -}}
{{/*
Return whether Redis uses password authentication or not
Return whether Redis(TM) uses password authentication or not
*/}}
{{- define "discourse.redis.usePassword" -}}
{{- if or (and .Values.redis.enabled .Values.redis.usePassword) (and (not .Values.redis.enabled) (or .Values.externalRedis.password .Values.externalRedis.existingSecret)) }}

18
bitnami/discourse/values-production.yaml
View File

@@ -568,7 +568,7 @@ externalDatabase:
##
database: bitnami_application
## Redis chart configuration
## Redis(TM) chart configuration
##
## https://github.com/bitnami/charts/blob/master/bitnami/redis/values.yaml
##
@@ -579,7 +579,7 @@ redis:
## Use password authentication
##
usePassword: true
## Redis password (both master and slave)
## Redis(TM) password (both master and slave)
## Defaults to a random 10-character alphanumeric string if not set and usePassword is true.
## It should always be set using the password value or in the existingSecret to avoid issues
## with Discourse.
@@ -590,7 +590,7 @@ redis:
##
existingSecret:
##
## Password key to be retrieved from Redis secret
## Password key to be retrieved from Redis(TM) secret
##
existingSecretPasswordKey: "redis-password"
##
@@ -599,23 +599,23 @@ redis:
cluster:
enabled: false
##
## Redis Master parameters
## Redis(TM) Master parameters
##
master:
persistence:
enabled: true
##
## External Redis
## External Redis(TM)
##
externalRedis:
## Redis host
## Redis(TM) host
##
host: ""
## Redis port
## Redis(TM) port
##
port: 6379
## Redis password for authentication
## Redis(TM) password for authentication
## Ignored if existingSecret is set
##
password: ""
@@ -624,6 +624,6 @@ externalRedis:
##
existingSecret:
##
## Password key to be retrieved from Redis secret
## Password key to be retrieved from Redis(TM) secret
##
existingSecretPasswordKey: "redis-password"

18
bitnami/discourse/values.yaml
View File

@@ -566,7 +566,7 @@ externalDatabase:
##
database: bitnami_application
## Redis chart configuration
## Redis(TM) chart configuration
##
## https://github.com/bitnami/charts/blob/master/bitnami/redis/values.yaml
##
@@ -577,7 +577,7 @@ redis:
## Use password authentication
##
usePassword: false
## Redis password (both master and slave)
## Redis(TM) password (both master and slave)
## Defaults to a random 10-character alphanumeric string if not set and usePassword is true.
## It should always be set using the password value or in the existingSecret to avoid issues
## with Discourse.
@@ -588,7 +588,7 @@ redis:
##
existingSecret:
##
## Password key to be retrieved from Redis secret
## Password key to be retrieved from Redis(TM) secret
##
existingSecretPasswordKey: 'redis-password'
##
@@ -598,23 +598,23 @@ redis:
enabled: false
##
## Redis Master parameters
## Redis(TM) Master parameters
##
master:
persistence:
enabled: true
##
## External Redis
## External Redis(TM)
##
externalRedis:
## Redis host
## Redis(TM) host
##
host: ''
## Redis port
## Redis(TM) port
##
port: 6379
## Redis password for authentication
## Redis(TM) password for authentication
## Ignored if existingSecret is set
##
password: ''
@@ -623,6 +623,6 @@ externalRedis:
##
existingSecret:
##
## Password key to be retrieved from Redis secret
## Password key to be retrieved from Redis(TM) secret
##
existingSecretPasswordKey: 'redis-password'

2
bitnami/harbor/Chart.yaml
View File

@@ -34,4 +34,4 @@ sources:
- https://github.com/bitnami/bitnami-docker-harbor-registry
- https://github.com/bitnami/bitnami-docker-harbor-registryctl
- https://goharbor.io/
version: 9.3.0
version: 9.3.1

32
bitnami/harbor/README.md
View File

@@ -4,7 +4,7 @@ This Helm chart has been developed based on [goharbor/harbor-helm](https://githu
For example, the following changes have been introduced:
- Possibility to pull all the required images from a private registry through the Global Docker image parameters.
- Redis and PostgreSQL are managed as chart dependencies.
- Redis<sup>TM</sup> and PostgreSQL are managed as chart dependencies.
- Liveness and Readiness probes for all deployments are exposed to the values.yaml.
- Uses new Helm chart labels formatting.
- Uses Bitnami container images:
@@ -707,27 +707,27 @@ The following tables list the configurable parameters of the Harbor chart and th
| `externalDatabase.password` | Password for the above username | `nil` |
| `externalDatabase.coreDatabase` | External database name for core | `nil` |
| `externalDatabase.clairDatabase` | External database name for clair | `nil` |
| `externalDatabase.clairUsername` | External database username for clair | `nil` |
| `externalDatabase.clairPassword` | External database password for clair | `nil` |
| `externalDatabase.clairUsername` | External database username for clair | `nil` |
| `externalDatabase.clairPassword` | External database password for clair | `nil` |
| `externalDatabase.notaryServerDatabase` | External database name for notary server | `nil` |
| `externalDatabase.notaryServerUsername` | External database username for notary server | `nil` |
| `externalDatabase.notaryServerPassword` | External database password for notary server | `nil` |
| `externalDatabase.notaryServerUsername` | External database username for notary server | `nil` |
| `externalDatabase.notaryServerPassword` | External database password for notary server | `nil` |
| `externalDatabase.notarySignerDatabase` | External database name for notary signer | `nil` |
| `externalDatabase.notarySignerUsername` | External database username for notary signer | `nil` |
| `externalDatabase.notarySignerPassword` | External database password for notary signer | `nil` |
| `externalDatabase.notarySignerUsername` | External database username for notary signer | `nil` |
| `externalDatabase.notarySignerPassword` | External database password for notary signer | `nil` |
| `externalDatabase.sslmode` | External database ssl mode | `disable` |
### Redis Parameters
### Redis<sup>TM</sup> Parameters
| Parameter | Description | Default |
|-------------------------------------------|-----------------------------------------------------------------------------------------------------------|-------------|
| `redis.enabled` | If external redis is used, set it to `false` | `true` |
| `redis.nameOverride` | String to partially override common.names.fullname template with a string (will prepend the release name) | `nil` |
| `redis.password` | Redis password | `nil` |
| `redis.password` | Redis<sup>TM</sup> password | `nil` |
| `redis.usePassword` | Use redis password | `false` |
| `redis.cluster.enabled` | Enable cluster redis | `false` |
| `redis.master.persistence.enabled` | Enable persistence for master Redis | `true` |
| `redis.slave.persistence.enabled` | Enable persistence for slave Redis | `true` |
| `redis.master.persistence.enabled` | Enable persistence for master Redis<sup>TM</sup> | `true` |
| `redis.slave.persistence.enabled` | Enable persistence for slave Redis<sup>TM</sup> | `true` |
| `externalRedis.host` | Host of the external redis | `localhost` |
| `externalRedis.port` | Port of the external redis | `6379` |
| `externalRedis.password` | Password for the external redis | `nil` |
@@ -786,7 +786,7 @@ This chart includes a `values-production.yaml` file where you can find some para
+ forcePassword: true
```
- Option to deploy Redis cluster:
- Option to deploy Redis<sup>TM</sup> cluster:
```diff
- redis.cluster.enabled: false
+ redis.cluster.enabled: true
@@ -972,7 +972,7 @@ postgresql 08:05:12.59 INFO ==> Deploying PostgreSQL with persisted data...
### To 8.0.0
Redis dependency version was bumped to the new major version `11.x.x`, which introduced breaking changes regarding sentinel. By default, this Chart does not use of this feature and hence no issues are expected between upgrades. You may refer to [Redis Upgrading Notes](https://github.com/bitnami/charts/tree/master/bitnami/redis#to-1100) for further information.
Redis<sup>TM</sup> dependency version was bumped to the new major version `11.x.x`, which introduced breaking changes regarding sentinel. By default, this Chart does not use of this feature and hence no issues are expected between upgrades. You may refer to [Redis<sup>TM</sup> Upgrading Notes](https://github.com/bitnami/charts/tree/master/bitnami/redis#to-1100) for further information.
### To 7.0.0
@@ -1007,10 +1007,10 @@ No issues are expected between upgrades but please double check the updated para
### To 4.0.0
PostgreSQL and Redis dependencies were updated to the use the latest major versions, `8.x.x` and `10.x.x`, respectively. These major versions do not include changes that should break backwards compatibilities, check the links below for more information:
PostgreSQL and Redis<sup>TM</sup> dependencies were updated to the use the latest major versions, `8.x.x` and `10.x.x`, respectively. These major versions do not include changes that should break backwards compatibilities, check the links below for more information:
- [PostgreSQL Upgrade notes](https://github.com/bitnami/charts/blob/master/bitnami/postgresql/README.md#upgrade)
- [Redis Upgrade notes](https://github.com/bitnami/charts/blob/master/bitnami/redis/README.md#upgrading-an-existing-release-to-a-new-major-version)
- [Redis<sup>TM</sup> Upgrade notes](https://github.com/bitnami/charts/blob/master/bitnami/redis/README.md#upgrading-an-existing-release-to-a-new-major-version)
### To 3.0.0
@@ -1024,7 +1024,7 @@ This major version signifies this change.
In this version, two major changes were performed:
- This **chart depends on the Redis 5 chart instead of Redis 4**. There is a breaking change that will affect releases with `metrics.enabled: true`, since the default tag for the exporter image is now `v1.x.x`. This introduces many changes including metrics names. You'll want to use [this dashboard](https://github.com/oliver006/redis_exporter/blob/master/contrib/grafana_prometheus_redis_dashboard.json) now. Please see the [redis_exporter github page](https://github.com/oliver006/redis_exporter#upgrading-from-0x-to-1x) for more details.
- This **chart depends on the Redis<sup>TM</sup> 5 chart instead of Redis<sup>TM</sup> 4**. There is a breaking change that will affect releases with `metrics.enabled: true`, since the default tag for the exporter image is now `v1.x.x`. This introduces many changes including metrics names. You'll want to use [this dashboard](https://github.com/oliver006/redis_exporter/blob/master/contrib/grafana_prometheus_redis_dashboard.json) now. Please see the [redis_exporter github page](https://github.com/oliver006/redis_exporter#upgrading-from-0x-to-1x) for more details.
- This **chart depends on the PostgreSQL 11 chart instead of PostgreSQL 10**. You can find the main difference and notable changes in the following links: [https://www.postgresql.org/about/news/1894/](https://www.postgresql.org/about/news/1894/) and [https://www.postgresql.org/about/featurematrix/](https://www.postgresql.org/about/featurematrix/).
For major releases of PostgreSQL, the internal data storage format is subject to change, thus complicating upgrades, you can see some errors like the following one in the logs:

16
bitnami/harbor/values-production.yaml
View File

@@ -1032,7 +1032,7 @@ core:
## Custom Startup probe
##
customStartupProbe: {}
## An array to add extra env vars
## For example:
##
@@ -1654,7 +1654,7 @@ chartmuseum:
updateStrategy:
type: RollingUpdate
## Set the use of the Redis cache.
## Set the use of the Redis(TM) cache.
##
useRedisCache: true
@@ -2622,7 +2622,7 @@ commonAnnotations: {}
##
commonLabels: {}
## Redis chart configuration
## Redis(TM) chart configuration
## ref: https://github.com/bitnami/charts/blob/master/bitnami/redis/values.yaml
##
redis:
@@ -2643,17 +2643,17 @@ redis:
persistence:
enabled: true
## If the Redis included in the chart is disabled, Harbor will use below
## Redis parameters to connect to an external Redis server.
## If the Redis(TM) included in the chart is disabled, Harbor will use below
## Redis(TM) parameters to connect to an external Redis(TM) server.
##
externalRedis:
## Redis host
## Redis(TM) host
##
host: localhost
## Redis port number
## Redis(TM) port number
##
port: 6379
## Redis password
## Redis(TM) password
##
password: ""
coreDatabaseIndex: "0"

14
bitnami/harbor/values.yaml
View File

@@ -1655,7 +1655,7 @@ chartmuseum:
updateStrategy:
type: RollingUpdate
## Set the use of the Redis cache.
## Set the use of the Redis(TM) cache.
##
useRedisCache: true
@@ -2624,7 +2624,7 @@ commonAnnotations: {}
##
commonLabels: {}
## Redis chart configuration
## Redis(TM) chart configuration
## ref: https://github.com/bitnami/charts/blob/master/bitnami/redis/values.yaml
##
redis:
@@ -2644,17 +2644,17 @@ redis:
persistence:
enabled: true
## If the Redis included in the chart is disabled, Harbor will use below
## Redis parameters to connect to an external Redis server.
## If the Redis(TM) included in the chart is disabled, Harbor will use below
## Redis(TM) parameters to connect to an external Redis(TM) server.
##
externalRedis:
## Redis host
## Redis(TM) host
##
host: localhost
## Redis port number
## Redis(TM) port number
##
port: 6379
## Redis password
## Redis(TM) password
##
password: ''
coreDatabaseIndex: '0'

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

@@ -23,4 +23,4 @@ name: redis-cluster
sources:
- https://github.com/bitnami/bitnami-docker-redis
- http://redis.io/
version: 4.2.3
version: 4.2.4

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

@@ -1,7 +1,9 @@
# Redis Cluster
# Redis<sup>TM</sup> Cluster Chart packaged by Bitnami
[Redis](http://redis.io/) is an advanced key-value cache and store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets, sorted sets, bitmaps and hyperloglogs.
[Redis<sup>TM</sup>](http://redis.io/) is an advanced key-value cache and store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets, sorted sets, bitmaps and hyperloglogs.
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.
## TL;DR
@@ -17,21 +19,21 @@ $ helm install my-release bitnami/redis-cluster --values values-production.yaml
## Introduction
This chart bootstraps a [Redis](https://github.com/bitnami/bitnami-docker-redis) deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
This chart bootstraps a [Redis<sup>TM</sup>](https://github.com/bitnami/bitnami-docker-redis) deployment on a [Kubernetes](http://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 Helm Chart and Redis Cluster Helm Chart
### Choose between Redis<sup>TM</sup> Helm Chart and Redis<sup>TM</sup> Cluster Helm Chart
You can choose any of the two Redis Helm charts for deploying a Redis cluster.
While [Redis Helm Chart](https://github.com/bitnami/charts/tree/master/bitnami/redis) will deploy a master-slave cluster using Redis Sentinel, the [Redis Cluster Helm Chart](https://github.com/bitnami/charts/tree/master/bitnami/redis-cluster) will deploy a Redis Cluster with sharding.
You can choose any of the two Redis<sup>TM</sup> Helm charts for deploying a Redis<sup>TM</sup> cluster.
While [Redis<sup>TM</sup> Helm Chart](https://github.com/bitnami/charts/tree/master/bitnami/redis) will deploy a master-slave cluster using Redis<sup>TM</sup> Sentinel, the [Redis<sup>TM</sup> Cluster Helm Chart](https://github.com/bitnami/charts/tree/master/bitnami/redis-cluster) will deploy a Redis<sup>TM</sup> Cluster with sharding.
The main features of each chart are the following:
| Redis | Redis 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 Topology](img/redis-topology.png) | ![Redis Cluster Topology](img/redis-cluster-topology.png) |
| Redis<sup>TM</sup> | Redis<sup>TM</sup> 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<sup>TM</sup> Topology](img/redis-topology.png) | ![Redis<sup>TM</sup> Cluster Topology](img/redis-cluster-topology.png) |
## Prerequisites
@@ -47,7 +49,7 @@ To install the chart with the release name `my-release`:
$ helm install my-release bitnami/redis-cluster
```
The command deploys Redis 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<sup>TM</sup> 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:
@@ -69,7 +71,7 @@ The command removes all the Kubernetes components associated with the chart and
## Parameters
The following table lists the configurable parameters of the Redis chart and their default values.
The following table lists the configurable parameters of the Redis<sup>TM</sup> chart and their default values.
#### Global parameters
@@ -78,16 +80,16 @@ The following table lists the configurable parameters of the Redis chart and the
| `global.imageRegistry` | Global Docker image registry | `nil` |
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `global.storageClass` | Global storage class for dynamic provisioning | `nil` |
| `global.redis.password` | Redis password (overrides `password`) | `nil` |
| `global.redis.password` | Redis<sup>TM</sup> password (overrides `password`) | `nil` |
#### Common parameters
| Parameter | Description | Default |
|-----------------------------------------|-------------------------------------------------------------------------------------|---------------------------------------------------------|
| `image.registry` | Redis Image registry | `docker.io` |
| `image.repository` | Redis Image name | `bitnami/redis` |
| `image.tag` | Redis Image tag | `{TAG_NAME}` |
| `image.registry` | Redis<sup>TM</sup> Image registry | `docker.io` |
| `image.repository` | Redis<sup>TM</sup> Image name | `bitnami/redis` |
| `image.tag` | Redis<sup>TM</sup> Image tag | `{TAG_NAME}` |
| `image.pullPolicy` | Image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `nil` |
| `nameOverride` | String to partially override redis.fullname template with a string | `nil` |
@@ -96,8 +98,8 @@ The following table lists the configurable parameters of the Redis chart and the
| `existingSecretPasswordKey` | Name of key containing password to be retrieved from the existing secret | `nil` |
| `usePassword` | Use password | `true` |
| `usePasswordFile` | Mount passwords as files instead of environment variables | `false` |
| `password` | Redis password (ignored if existingSecret set) | Randomly generated |
| `configmap` | Additional common Redis node configuration (this value is evaluated as a template) | See `values.yaml` |
| `password` | Redis<sup>TM</sup> password (ignored if existingSecret set) | Randomly generated |
| `configmap` | Additional common Redis<sup>TM</sup> node configuration (this value is evaluated as a template) | See `values.yaml` |
| `networkPolicy.enabled` | Enable NetworkPolicy | `false` |
| `networkPolicy.allowExternal` | Don't require client label for connections | `true` |
| `networkPolicy.ingressNSMatchLabels` | Allow connections from other namespaces | `{}` |
@@ -145,26 +147,26 @@ The following table lists the configurable parameters of the Redis chart and the
| `commonAnnotations` | Annotations to add to all deployed objects | `[]` |
| `extraDeploy` | Array of extra objects to deploy with the release (evaluated as a template). | `nil` |
#### Redis statefulset parameters
#### Redis<sup>TM</sup> statefulset parameters
| Parameter | Description | Default |
|--------------------------------------------|-------------------------------------------------------------------------------------------------------|---------------------------------------------------------|
| `redis.port` | Redis port. | `6379` |
| `redis.port` | Redis<sup>TM</sup> port. | `6379` |
| `redis.useAOFPersistence` | Enables AOF persistence mode | `"yes"` |
| `redis.podLabels` | Additional labels for Redis pod | {} |
| `redis.command` | Redis entrypoint string. The command `redis-server` is executed if this is not provided. | `nil` |
| `redis.podLabels` | Additional labels for Redis<sup>TM</sup> pod | {} |
| `redis.command` | Redis<sup>TM</sup> entrypoint string. The command `redis-server` is executed if this is not provided. | `nil` |
| `redis.args` | Arguments for the provided command if needed | `nil` |
| `redis.schedulerName` | Name of an alternate scheduler | `nil` |
| `redis.configmap` | Additional Redis configuration for the nodes (this value is evaluated as a template) | `nil` |
| `redis.podAffinityPreset` | Redis pod affinity preset. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `redis.podAntiAffinityPreset` | Redis pod anti-affinity preset. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard` | `soft` |
| `redis.nodeAffinityPreset.type` | Redis node affinity preset type. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `redis.nodeAffinityPreset.key` | Redis node label key to match Ignored if `redis.affinity` is set. | `""` |
| `redis.nodeAffinityPreset.values` | Redis node label values to match. Ignored if `redis.affinity` is set. | `[]` |
| `redis.affinity` | Affinity for Redis pods assignment | `{}` (evaluated as a template) |
| `redis.nodeSelector` | Node labels for Redis pods assignment | `{}` (evaluated as a template) |
| `redis.tolerations` | Tolerations for Redis pods assignment | `[]` (evaluated as a template) |
| `redis.busPort` | Port for the Redis gossip protocol | `16379` |
| `redis.configmap` | Additional Redis<sup>TM</sup> configuration for the nodes (this value is evaluated as a template) | `nil` |
| `redis.podAffinityPreset` | Redis<sup>TM</sup> pod affinity preset. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `redis.podAntiAffinityPreset` | Redis<sup>TM</sup> pod anti-affinity preset. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard` | `soft` |
| `redis.nodeAffinityPreset.type` | Redis<sup>TM</sup> node affinity preset type. Ignored if `redis.affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `redis.nodeAffinityPreset.key` | Redis<sup>TM</sup> node label key to match Ignored if `redis.affinity` is set. | `""` |
| `redis.nodeAffinityPreset.values` | Redis<sup>TM</sup> node label values to match. Ignored if `redis.affinity` is set. | `[]` |
| `redis.affinity` | Affinity for Redis<sup>TM</sup> pods assignment | `{}` (evaluated as a template) |
| `redis.nodeSelector` | Node labels for Redis<sup>TM</sup> pods assignment | `{}` (evaluated as a template) |
| `redis.tolerations` | Tolerations for Redis<sup>TM</sup> pods assignment | `[]` (evaluated as a template) |
| `redis.busPort` | Port for the Redis<sup>TM</sup> gossip protocol | `16379` |
| `redis.lifecycleHooks` | LifecycleHook to set additional configuration at startup. Evaluated as a template | `` |
| `redis.livenessProbe.enabled` | Turn on and off liveness probe. | `true` |
| `redis.livenessProbe.initialDelaySeconds` | Delay before liveness probe is initiated. | `30` |
@@ -178,19 +180,19 @@ The following table lists the configurable parameters of the Redis chart and the
| `redis.readinessProbe.timeoutSeconds` | When the probe times out. | `1` |
| `redis.readinessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `redis.readinessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `5` |
| `redis.priorityClassName` | Redis Master pod priorityClassName | `{}` |
| `redis.priorityClassName` | Redis<sup>TM</sup> Master pod priorityClassName | `{}` |
| `redis.customLivenessProbe` | Override default liveness probe | `nil` |
| `redis.customReadinessProbe` | Override default readiness probe | `nil` |
| `redis.extraVolumes` | Array of extra volumes to be added to all pods (evaluated as a template) | `[]` |
| `redis.extraVolumeMounts` | Array of extra volume mounts to be added to all pods (evaluated as a template) | `[]` |
| `redis.affinity` | Affinity settings for Redis pod assignment | `{}` |
| `redis.topologySpreadConstraints` | Pod topology spread constraints for Redis pod | `[]` |
| `redis.affinity` | Affinity settings for Redis<sup>TM</sup> pod assignment | `{}` |
| `redis.topologySpreadConstraints` | Pod topology spread constraints for Redis<sup>TM</sup> pod | `[]` |
| `redis.extraEnvVars` | Array containing extra env vars to be added to all pods (evaluated as a template) | `[]` |
| `redis.extraEnvVarsCM` | ConfigMap containing extra env vars to be added to all pods (evaluated as a template) | `nil` |
| `redis.extraEnvVarsSecret` | Secret containing extra env vars to be added to all pods (evaluated as a template) | `nil` |
| `redis.initContainers` | Init containers to add to the cronjob container | `{}` |
| `redis.sidecars` | Attach additional containers to the pod (evaluated as a template) | `nil` |
| `redis.resources` | Redis CPU/Memory resource requests/limits | `{Memory: "256Mi", CPU: "100m"}` |
| `redis.resources` | Redis<sup>TM</sup> CPU/Memory resource requests/limits | `{Memory: "256Mi", CPU: "100m"}` |
#### Cluster initialization job parameters
@@ -216,7 +218,7 @@ The following table lists the configurable parameters of the Redis chart and the
| `initJob.affinity` | Affinity for init job pods assignment | `{}` (evaluated as a template) |
| `initJob.nodeSelector` | Node labels for init job pods assignment | `{}` (evaluated as a template) |
| `initJob.tolerations` | Tolerations for init job pods assignment | `[]` (evaluated as a template) |
| `initJob.resources` | Redis CPU/Memory resource requests/limits | `nil` |
| `initJob.resources` | Redis<sup>TM</sup> CPU/Memory resource requests/limits | `nil` |
| `initJob.priorityClassName` | Priority class name | `nil` |
#### Cluster update job parameters
@@ -243,33 +245,33 @@ The following table lists the configurable parameters of the Redis chart and the
| `updateJob.affinity` | Affinity for update job pods assignment | `{}` (evaluated as a template) |
| `updateJob.nodeSelector` | Node labels for update job pods assignment | `{}` (evaluated as a template) |
| `updateJob.tolerations` | Tolerations for update job pods assignment | `[]` (evaluated as a template) |
| `updateJob.resources` | Redis CPU/Memory resource requests/limits | `nil` |
| `updateJob.resources` | Redis<sup>TM</sup> CPU/Memory resource requests/limits | `nil` |
| `updateJob.priorityClassName` | Priority class name | `nil` |
#### Cluster management parameters
| Parameter | Description | Default |
|-------------------------------------------------|----------------------------------------------------------------|-------------------|
| `cluster.init` | Enable the creation of a job that initializes the Redis Cluster | `true` |
| `cluster.nodes` | Number of nodes in the Redis cluster | `6` |
| `cluster.replicas` | Number of replicas for every master in the cluster | `1` |
| `cluster.externalAccess.enabled` | Enable access to the Redis cluster from Outside the Kubernetes Cluster | `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 LoadBalancer IPs used to expose every Pod of the Redis cluster when `cluster.externalAccess.service.type` is `LoadBalancer` | `[]` |
| `cluster.externalAccess.service.annotations` | Annotations to add to the services used to expose every Pod of the Redis 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 nodes | `6` |
| `cluster.update.newExternalIPs` | External IPs obtained from the services for the new nodes to add to the cluster | `nil` |
| Parameter | Description | Default |
|-------------------------------------------------|-----------------------------------------------------------------------------------------------|-------------------|
| `cluster.init` | Enable the creation of a job that initializes the Redis<sup>TM</sup> Cluster | `true` |
| `cluster.nodes` | Number of nodes in the Redis<sup>TM</sup> cluster | `6` |
| `cluster.replicas` | Number of replicas for every master in the cluster | `1` |
| `cluster.externalAccess.enabled` | Enable access to the Redis<sup>TM</sup> cluster from Outside the Kubernetes Cluster | `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 LoadBalancer IPs used to expose every Pod of the Redis<sup>TM</sup> cluster when `cluster.externalAccess.service.type` is `LoadBalancer` | `[]` |
| `cluster.externalAccess.service.annotations` | Annotations to add to the services used to expose every Pod of the Redis<sup>TM</sup> 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<sup>TM</sup> nodes | `6` |
| `cluster.update.newExternalIPs` | External IPs obtained from the services for the new nodes to add to the cluster | `nil` |
#### Metrics sidecar parameters
| Parameter | Description | Default |
|-------------------------------------------------|----------------------------------------------------------------|-------------------|
| `metrics.enabled` | Start a side-car prometheus exporter | `false` |
| `metrics.image.registry` | Redis exporter image registry | `docker.io` |
| `metrics.image.repository` | Redis exporter image name | `bitnami/redis-exporter` |
| `metrics.image.tag` | Redis exporter image tag | `{TAG_NAME}` |
| `metrics.image.registry` | Redis<sup>TM</sup> exporter image registry | `docker.io` |
| `metrics.image.repository` | Redis<sup>TM</sup> exporter image name | `bitnami/redis-exporter` |
| `metrics.image.tag` | Redis<sup>TM</sup> exporter image tag | `{TAG_NAME}` |
| `metrics.image.pullPolicy` | Image pull policy | `IfNotPresent` |
| `metrics.image.pullSecrets` | Specify docker-registry secret names as an array | `nil` |
| `metrics.extraArgs` | Extra arguments for the binary; possible values [here](https://github.com/oliver006/redis_exporter#flags) | {} |
@@ -310,7 +312,7 @@ $ helm install my-release \
bitnami/redis-cluster
```
The above command sets the Redis server password to `secretpassword`.
The above command sets the Redis<sup>TM</sup> server password to `secretpassword`.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
@@ -320,7 +322,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 pod as it attempts to write to the `/bitnami` directory. Consider installing Redis with `--set persistence.enabled=false`. 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<sup>TM</sup> pod as it attempts to write to the `/bitnami` directory. Consider installing Redis<sup>TM</sup> with `--set persistence.enabled=false`. See minikube issue [1990](https://github.com/kubernetes/minikube/issues/1990) for more information.
## Configuration and installation details
@@ -348,26 +350,26 @@ This chart includes a `values-production.yaml` file where you can find some para
+ metrics.enabled: true
```
### Change Redis version
### Change Redis<sup>TM</sup> version
To modify the Redis version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/redis-cluster/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters.
To modify the Redis<sup>TM</sup> version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/redis-cluster/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters.
### Cluster topology
The Helm Chart will deploy by default 3 redis masters and 3 replicas. By default the Redis Cluster is not accessible from outside the Kubernetes cluster, to access the Redis 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 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 Helm Chart will deploy by default 3 redis masters and 3 replicas. By default the Redis<sup>TM</sup> Cluster is not accessible from outside the Kubernetes cluster, to access the Redis<sup>TM</sup> 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<sup>TM</sup> 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 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<sup>TM</sup> 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 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<sup>TM</sup> 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
@@ -389,7 +391,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 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<sup>TM</sup> 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
@@ -399,7 +401,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 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<sup>TM</sup> 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:
```
@@ -408,7 +410,7 @@ 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 Cluster again, you will need to provide `cluster.init=false`.
> NOTE: To avoid the creation of the Job that initializes the Redis<sup>TM</sup> Cluster again, you will need to provide `cluster.init=false`.
#### Scale down the cluster
@@ -420,10 +422,10 @@ 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 Cluster again, you will need to provide `cluster.init=false`.
> NOTE: To avoid the creation of the Job that initializes the Redis<sup>TM</sup> Cluster again, you will need to provide `cluster.init=false`.
### Using password file
To use a password file for Redis you need to create a secret containing the password.
To use a password file for Redis<sup>TM</sup> you need to create a secret containing the password.
> *NOTE*: It is important that the file with the password must be called `redis-password`
@@ -466,7 +468,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 (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<sup>TM</sup> (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:
@@ -507,7 +509,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 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<sup>TM</sup> 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:
@@ -535,7 +537,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 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<sup>TM</sup> 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
@@ -543,7 +545,7 @@ By default, the chart mounts a [Persistent Volume](http://kubernetes.io/docs/use
## NetworkPolicy
To enable network policy for Redis, install
To enable network policy for Redis<sup>TM</sup>, 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`.
@@ -553,7 +555,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. This label will be displayed in the output
able to connect to Redis<sup>TM</sup>. 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:
@@ -604,7 +606,7 @@ Find more information about how to deal with common errors related to Bitnami’
### 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 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<sup>TM</sup> 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

@@ -8,13 +8,13 @@ To get your password run:
{{- if .Values.cluster.externalAccess.enabled }}
To connect to your Redis server from outside the cluster check the following information:
To connect to your Redis(TM) 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 node. Get the external ip from `-external` suffixed services: `kubectl get svc`.
Redis port: {{ .Values.cluster.externalAccess.service.port }}
You will have a different external IP for each Redis(TM) node. Get the external ip from `-external` suffixed services: `kubectl get svc`.
Redis(TM) 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:
@@ -34,15 +34,15 @@ To connect to your Redis server from outside the cluster check the following inf
{{- else }}
You have deployed a Redis Cluster accessible only from within you Kubernetes Cluster.
You have deployed a Redis(TM) 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 cluster:
To connect to your Redis(TM) cluster:
1. Run a Redis pod that you can use as a client:
1. Run a Redis(TM) 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
@@ -65,7 +65,7 @@ kubectl run --namespace {{ .Release.Namespace }} {{ template "common.names.fulln
--image {{ template "redis-cluster.image" . }} -- bash
{{- end }}
2. Connect using the Redis CLI:
2. Connect using the Redis(TM) 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 }}

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

@@ -1,7 +1,7 @@
{{/* vim: set filetype=mustache: */}}
{{/*
Return the proper Redis image name
Return the proper Redis(TM) image name
*/}}
{{- define "redis-cluster.image" -}}
{{ include "common.images.image" (dict "imageRoot" .Values.image "global" .Values.global) }}
@@ -121,7 +121,7 @@ Get the password secret.
{{- end -}}
{{/*
Get the password key to be retrieved from Redis secret.
Get the password key to be retrieved from Redis(TM) secret.
*/}}
{{- define "redis-cluster.secretPasswordKey" -}}
{{- if and .Values.existingSecret .Values.existingSecretPasswordKey -}}
@@ -132,7 +132,7 @@ Get the password key to be retrieved from Redis secret.
{{- end -}}
{{/*
Return Redis password
Return Redis(TM) password
*/}}
{{- define "redis-cluster.password" -}}
{{- if not (empty .Values.global.redis.password) }}
@@ -177,7 +177,7 @@ Compile all warnings into a single message, and call fail.
{{- end -}}
{{- end -}}
{{/* Validate values of Redis Cluster - check update parameters */}}
{{/* Validate values of Redis(TM) 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 }}
@@ -194,7 +194,7 @@ redis-cluster: currentNumberOfNodes
{{- end -}}
{{- end -}}
{{/* Validate values of Redis Cluster - tls settings */}}
{{/* Validate values of Redis(TM) Cluster - tls settings */}}
{{- define "redis-cluster.validateValues.tlsParameters" -}}
{{- if .Values.tls.enabled }}
{{- if not .Values.tls.certFilename -}}

68
bitnami/redis-cluster/values-production.yaml
View File

@@ -9,13 +9,13 @@ global:
# storageClass: myStorageClass
redis: {}
## Bitnami Redis image version
## Bitnami Redis(TM) image version
## ref: https://hub.docker.com/r/bitnami/redis/tags/
##
image:
registry: docker.io
repository: bitnami/redis-cluster
## Bitnami Redis image tag
## Bitnami Redis(TM) image tag
## ref: https://github.com/bitnami/bitnami-docker-redis#supported-tags-and-respective-dockerfile-links
##
tag: 6.0.9-debian-10-r59
@@ -39,13 +39,13 @@ nameOverride:
##
fullnameOverride:
## Redis Cluster settings
## Redis(TM) Cluster settings
##
cluster:
## Enable the creation of a Job that will execute the proper command to create the Redis Cluster.
## Enable the creation of a Job that will execute the proper command to create the Redis(TM) Cluster.
##
init: true
## Number of Redis nodes to be deployed
## Number of Redis(TM) nodes to be deployed
##
nodes: 6
## Parameter to be passed as --cluster-replicas to the redis-cli --cluster create
@@ -53,7 +53,7 @@ cluster:
##
replicas: 1
## Configuration to access the Redis Cluster from outside the Kubernetes cluster
## Configuration to access the Redis(TM) Cluster from outside the Kubernetes cluster
##
externalAccess:
enabled: false
@@ -64,17 +64,17 @@ cluster:
## Port used when service type is LoadBalancer
##
port: 6379
## Array of load balancer IPs for each Redis node. Length must be the same as cluster.nodes
## Array of load balancer IPs for each Redis(TM) node. Length must be the same as cluster.nodes
##
loadBalancerIP: []
## Service annotations done as key:value pairs
##
annotations: {}
## This section allows to update the Redis cluster nodes.
## This section allows to update the Redis(TM) cluster nodes.
##
update:
## Setting this to true a hook will add nodes to the Redis cluster after the upgrade.
## Setting this to true a hook will add nodes to the Redis(TM) cluster after the upgrade.
## currentNumberOfNodes is required
##
addNodes: false
@@ -101,7 +101,7 @@ redis:
# ref: https://redis.io/topics/cluster-tutorial#creating-and-using-a-redis-cluster
useAOFPersistence: "yes"
# Redis port
# Redis(TM) port
port: 6379
## lifecycleHooks for the container to automate configuration before or after startup.
@@ -141,7 +141,7 @@ redis:
##
priorityClassName:
## Additional Redis configuration for the nodes
## Additional Redis(TM) configuration for the nodes
## ref: https://redis.io/topics/config
##
configmap:
@@ -161,12 +161,12 @@ redis:
##
extraEnvVarsSecret:
## Redis additional annotations
## Redis(TM) additional annotations
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
##
podAnnotations: {}
## Redis resource requests and limits
## Redis(TM) resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
##
resources:
@@ -179,7 +179,7 @@ redis:
##
schedulerName:
## Configure extra options for Redis liveness and readiness probes
## Configure extra options for Redis(TM) liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
##
livenessProbe:
@@ -197,19 +197,19 @@ redis:
successThreshold: 1
failureThreshold: 5
## Redis pod affinity preset
## Redis(TM) pod affinity preset
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity
## Allowed values: soft, hard
##
podAffinityPreset: ""
## Redis pod anti-affinity preset
## Redis(TM) pod anti-affinity preset
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity
## Allowed values: soft, hard
##
podAntiAffinityPreset: soft
## Redis node affinity preset
## Redis(TM) node affinity preset
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity
## Allowed values: soft, hard
##
@@ -230,18 +230,18 @@ redis:
##
values: []
## Affinity for Redis pods assignment
## Affinity for Redis(TM) pods 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: {}
## Node labels for Redis pods assignment
## Node labels for Redis(TM) pods assignment
## ref: https://kubernetes.io/docs/user-guide/node-selection/
##
nodeSelector: {}
## Tolerations for Redis pods assignment
## Tolerations for Redis(TM) pods assignment
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
##
tolerations: []
@@ -508,8 +508,8 @@ networkPolicy:
enabled: true
## The Policy model to apply. When set to false, only pods with the correct
## client label will have network access to the port Redis is listening
## on. When true, Redis will accept connections from any source
## client label will have network access to the port Redis(TM) is listening
## on. When true, Redis(TM) will accept connections from any source
## (with the correct destination port).
##
allowExternal: true
@@ -546,7 +546,7 @@ rbac:
# - gce.unprivileged
rules: []
## Redis pod Security Context
## Redis(TM) pod Security Context
##
podSecurityContext:
enabled: true
@@ -587,7 +587,7 @@ containerSecurityContext:
## Use password authentication
##
usePassword: true
## Redis password
## Redis(TM) password
## 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
##
@@ -595,7 +595,7 @@ password: ""
## Use existing secret (ignores previous password)
##
existingSecret:
## Password key to be retrieved from Redis secret
## Password key to be retrieved from Redis(TM) secret
##
existingSecretPasswordKey:
@@ -636,7 +636,7 @@ commonAnnotations:
##
commonLabels:
## Redis Service properties for standalone mode.
## Redis(TM) Service properties for standalone mode.
##
service:
port: 6379
@@ -664,14 +664,14 @@ service:
persistence:
enabled: true
## The path the volume will be mounted at, useful when using different
## Redis images.
## Redis(TM) images.
##
path: /bitnami/redis/data
## The subdirectory of the volume to mount to, useful in dev environments
## and one PV for multiple services.
##
subPath: ""
## Redis data Persistent Volume Storage Class
## Redis(TM) data Persistent Volume Storage Class
## If defined, storageClassName: <storageClass>
## If set to "-", storageClassName: "", which disables dynamic provisioning
## If undefined (the default) or set to null, no storageClassName spec is
@@ -760,8 +760,8 @@ metrics:
# labels:
# severity: error
# annotations:
# summary: Redis instance {{ "{{ $instance }}" }} down
# description: Redis instance {{ "{{ $instance }}" }} is down.
# summary: Redis(TM) instance {{ "{{ $instance }}" }} down
# description: Redis(TM) instance {{ "{{ $instance }}" }} is down.
# - alert: RedisMemoryHigh
# expr: >
# redis_memory_used_bytes{service="{{ template "common.names.fullname" . }}-metrics"} * 100
@@ -772,16 +772,16 @@ metrics:
# labels:
# severity: error
# annotations:
# summary: Redis instance {{ "{{ $instance }}" }} is using too much memory
# description: Redis instance {{ "{{ $instance }}" }} is using {{ "{{ $value }}" }}% of its available memory.
# summary: Redis(TM) instance {{ "{{ $instance }}" }} is using too much memory
# description: Redis(TM) 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 instance {{ "{{ $instance }}" }} has evicted keys
# description: Redis instance {{ "{{ $instance }}" }} has evicted {{ "{{ $value }}" }} keys in the last 5 minutes.
# summary: Redis(TM) instance {{ "{{ $instance }}" }} has evicted keys
# description: Redis(TM) instance {{ "{{ $instance }}" }} has evicted {{ "{{ $value }}" }} keys in the last 5 minutes.
## Metrics exporter pod priorityClassName
# priorityClassName: {}

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

@@ -9,13 +9,13 @@ global:
# storageClass: myStorageClass
redis: {}
## Bitnami Redis image version
## Bitnami Redis(TM) image version
## ref: https://hub.docker.com/r/bitnami/redis/tags/
##
image:
registry: docker.io
repository: bitnami/redis-cluster
## Bitnami Redis image tag
## Bitnami Redis(TM) image tag
## ref: https://github.com/bitnami/bitnami-docker-redis#supported-tags-and-respective-dockerfile-links
##
tag: 6.0.9-debian-10-r59
@@ -39,13 +39,13 @@ nameOverride:
##
fullnameOverride:
## Redis Cluster settings
## Redis(TM) Cluster settings
##
cluster:
## Enable the creation of a Job that will execute the proper command to create the Redis Cluster.
## Enable the creation of a Job that will execute the proper command to create the Redis(TM) Cluster.
##
init: true
## Number of Redis nodes to be deployed
## Number of Redis(TM) nodes to be deployed
##
nodes: 6
## Parameter to be passed as --cluster-replicas to the redis-cli --cluster create
@@ -53,7 +53,7 @@ cluster:
##
replicas: 1
## Configuration to access the Redis Cluster from outside the Kubernetes cluster
## Configuration to access the Redis(TM) Cluster from outside the Kubernetes cluster
##
externalAccess:
enabled: false
@@ -64,17 +64,17 @@ cluster:
## Port used when service type is LoadBalancer
##
port: 6379
## Array of load balancer IPs for each Redis node. Length must be the same as cluster.nodes
## Array of load balancer IPs for each Redis(TM) node. Length must be the same as cluster.nodes
##
loadBalancerIP: []
## Service annotations done as key:value pairs
##
annotations: {}
## This section allows to update the Redis cluster nodes.
## This section allows to update the Redis(TM) cluster nodes.
##
update:
## Setting this to true a hook will add nodes to the Redis cluster after the upgrade.
## Setting this to true a hook will add nodes to the Redis(TM) cluster after the upgrade.
## currentNumberOfNodes is required
##
addNodes: false
@@ -101,7 +101,7 @@ redis:
# ref: https://redis.io/topics/cluster-tutorial#creating-and-using-a-redis-cluster
useAOFPersistence: "yes"
# Redis port
# Redis(TM) port
port: 6379
## lifecycleHooks for the container to automate configuration before or after startup.
@@ -141,7 +141,7 @@ redis:
##
priorityClassName:
## Additional Redis configuration for the nodes
## Additional Redis(TM) configuration for the nodes
## ref: https://redis.io/topics/config
##
configmap:
@@ -161,12 +161,12 @@ redis:
##
extraEnvVarsSecret:
## Redis additional annotations
## Redis(TM) additional annotations
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
##
podAnnotations: {}
## Redis resource requests and limits
## Redis(TM) resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
##
resources: {}
@@ -179,7 +179,7 @@ redis:
##
schedulerName:
## Configure extra options for Redis liveness and readiness probes
## Configure extra options for Redis(TM) liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
##
livenessProbe:
@@ -197,19 +197,19 @@ redis:
successThreshold: 1
failureThreshold: 5
## Redis pod affinity preset
## Redis(TM) pod affinity preset
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity
## Allowed values: soft, hard
##
podAffinityPreset: ""
## Redis pod anti-affinity preset
## Redis(TM) pod anti-affinity preset
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity
## Allowed values: soft, hard
##
podAntiAffinityPreset: soft
## Redis node affinity preset
## Redis(TM) node affinity preset
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity
## Allowed values: soft, hard
##
@@ -230,18 +230,18 @@ redis:
##
values: []
## Affinity for Redis pods assignment
## Affinity for Redis(TM) pods 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: {}
## Node labels for Redis pods assignment
## Node labels for Redis(TM) pods assignment
## ref: https://kubernetes.io/docs/user-guide/node-selection/
##
nodeSelector: {}
## Tolerations for Redis pods assignment
## Tolerations for Redis(TM) pods assignment
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
##
tolerations: []
@@ -511,8 +511,8 @@ networkPolicy:
enabled: false
## The Policy model to apply. When set to false, only pods with the correct
## client label will have network access to the port Redis is listening
## on. When true, Redis will accept connections from any source
## client label will have network access to the port Redis(TM) is listening
## on. When true, Redis(TM) will accept connections from any source
## (with the correct destination port).
##
allowExternal: true
@@ -549,7 +549,7 @@ rbac:
# - gce.unprivileged
rules: []
## Redis pod Security Context
## Redis(TM) pod Security Context
##
podSecurityContext:
enabled: true
@@ -590,7 +590,7 @@ containerSecurityContext:
## Use password authentication
##
usePassword: true
## Redis password
## Redis(TM) password
## 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
##
@@ -598,7 +598,7 @@ password: ""
## Use existing secret (ignores previous password)
##
existingSecret:
## Password key to be retrieved from Redis secret
## Password key to be retrieved from Redis(TM) secret
##
existingSecretPasswordKey:
@@ -639,7 +639,7 @@ commonAnnotations:
##
commonLabels:
## Redis Service properties for standalone mode.
## Redis(TM) Service properties for standalone mode.
##
service:
port: 6379
@@ -667,14 +667,14 @@ service:
persistence:
enabled: true
## The path the volume will be mounted at, useful when using different
## Redis images.
## Redis(TM) images.
##
path: /bitnami/redis/data
## The subdirectory of the volume to mount to, useful in dev environments
## and one PV for multiple services.
##
subPath: ""
## Redis data Persistent Volume Storage Class
## Redis(TM) data Persistent Volume Storage Class
## If defined, storageClassName: <storageClass>
## If set to "-", storageClassName: "", which disables dynamic provisioning
## If undefined (the default) or set to null, no storageClassName spec is
@@ -763,8 +763,8 @@ metrics:
# labels:
# severity: error
# annotations:
# summary: Redis instance {{ "{{ $instance }}" }} down
# description: Redis instance {{ "{{ $instance }}" }} is down.
# summary: Redis(TM) instance {{ "{{ $instance }}" }} down
# description: Redis(TM) instance {{ "{{ $instance }}" }} is down.
# - alert: RedisMemoryHigh
# expr: >
# redis_memory_used_bytes{service="{{ template "common.names.fullname" . }}-metrics"} * 100
@@ -775,16 +775,16 @@ metrics:
# labels:
# severity: error
# annotations:
# summary: Redis instance {{ "{{ $instance }}" }} is using too much memory
# description: Redis instance {{ "{{ $instance }}" }} is using {{ "{{ $value }}" }}% of its available memory.
# summary: Redis(TM) instance {{ "{{ $instance }}" }} is using too much memory
# description: Redis(TM) 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 instance {{ "{{ $instance }}" }} has evicted keys
# description: Redis instance {{ "{{ $instance }}" }} has evicted {{ "{{ $value }}" }} keys in the last 5 minutes.
# summary: Redis(TM) instance {{ "{{ $instance }}" }} has evicted keys
# description: Redis(TM) instance {{ "{{ $instance }}" }} has evicted {{ "{{ $value }}" }} keys in the last 5 minutes.
## Metrics exporter pod priorityClassName
# priorityClassName: {}

176
bitnami/redis/README.md
View File

@@ -1,6 +1,8 @@
# Redis
# Redis<sup>TM</sup> Chart packaged by Bitnami
[Redis](http://redis.io/) is an advanced key-value cache and store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets, sorted sets, bitmaps and hyperloglogs.
[Redis<sup>TM</sup>](http://redis.io/) is an advanced key-value cache and store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets, sorted sets, bitmaps and hyperloglogs.
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.
## TL;DR
@@ -18,21 +20,21 @@ $ helm install my-release bitnami/redis --values values-production.yaml
## Introduction
This chart bootstraps a [Redis](https://github.com/bitnami/bitnami-docker-redis) deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
This chart bootstraps a [Redis<sup>TM</sup>](https://github.com/bitnami/bitnami-docker-redis) deployment on a [Kubernetes](http://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 Helm Chart and Redis Cluster Helm Chart
### Choose between Redis<sup>TM</sup> Helm Chart and Redis<sup>TM</sup> Cluster Helm Chart
You can choose any of the two Redis Helm charts for deploying a Redis cluster.
While [Redis Helm Chart](https://github.com/bitnami/charts/tree/master/bitnami/redis) will deploy a master-slave cluster using Redis Sentinel, the [Redis Cluster Helm Chart](https://github.com/bitnami/charts/tree/master/bitnami/redis-cluster) will deploy a Redis Cluster topology with sharding.
You can choose any of the two Redis<sup>TM</sup> Helm charts for deploying a Redis<sup>TM</sup> cluster.
While [Redis<sup>TM</sup> Helm Chart](https://github.com/bitnami/charts/tree/master/bitnami/redis) will deploy a master-slave cluster using Redis<sup>TM</sup> Sentinel, the [Redis<sup>TM</sup> Cluster Helm Chart](https://github.com/bitnami/charts/tree/master/bitnami/redis-cluster) will deploy a Redis<sup>TM</sup> Cluster topology with sharding.
The main features of each chart are the following:
| Redis | Redis 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 Topology](img/redis-topology.png) | ![Redis Cluster Topology](img/redis-cluster-topology.png) |
| Redis<sup>TM</sup> | Redis<sup>TM</sup> 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<sup>TM</sup> Topology](img/redis-topology.png) | ![Redis<sup>TM</sup> Cluster Topology](img/redis-cluster-topology.png) |
## Prerequisites
@@ -48,7 +50,7 @@ To install the chart with the release name `my-release`:
$ helm install my-release bitnami/redis
```
The command deploys Redis 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<sup>TM</sup> on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
> **Tip**: List all releases using `helm list`
@@ -64,17 +66,17 @@ The command removes all the Kubernetes components associated with the chart and
## Parameters
The following table lists the configurable parameters of the Redis chart and their default values.
The following table lists the configurable parameters of the Redis<sup>TM</sup> chart and their default values.
| Parameter | Description | Default |
|:----------------------------------------------|:----------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------|
| `global.imageRegistry` | Global Docker image registry | `nil` |
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `global.storageClass` | Global storage class for dynamic provisioning | `nil` |
| `global.redis.password` | Redis password (overrides `password`) | `nil` |
| `image.registry` | Redis Image registry | `docker.io` |
| `image.repository` | Redis Image name | `bitnami/redis` |
| `image.tag` | Redis Image tag | `{TAG_NAME}` |
| `global.redis.password` | Redis<sup>TM</sup> password (overrides `password`) | `nil` |
| `image.registry` | Redis<sup>TM</sup> Image registry | `docker.io` |
| `image.repository` | Redis<sup>TM</sup> Image name | `bitnami/redis` |
| `image.tag` | Redis<sup>TM</sup> Image tag | `{TAG_NAME}` |
| `image.pullPolicy` | Image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `nil` |
| `nameOverride` | String to partially override redis.fullname template with a string (will prepend the release name) | `nil` |
@@ -85,8 +87,8 @@ The following table lists the configurable parameters of the Redis chart and the
| `existingSecretPasswordKey` | Name of key containing password to be retrieved from the existing secret | `nil` |
| `usePassword` | Use password | `true` |
| `usePasswordFile` | Mount passwords as files instead of environment variables | `false` |
| `password` | Redis password (ignored if existingSecret set) | Randomly generated |
| `configmap` | Additional common Redis node configuration (this value is evaluated as a template) | See values.yaml |
| `password` | Redis<sup>TM</sup> password (ignored if existingSecret set) | Randomly generated |
| `configmap` | Additional common Redis<sup>TM</sup> node configuration (this value is evaluated as a template) | See values.yaml |
| `clusterDomain` | Kubernetes DNS Domain name to use | `cluster.local` |
| `networkPolicy.enabled` | Enable NetworkPolicy | `false` |
| `networkPolicy.allowExternal` | Don't require client label for connections | `true` |
@@ -104,9 +106,9 @@ The following table lists the configurable parameters of the Redis chart and the
| `rbac.create` | Specifies whether RBAC resources should be created | `false` |
| `rbac.role.rules` | Rules to create | `[]` |
| `metrics.enabled` | Start a side-car prometheus exporter | `false` |
| `metrics.image.registry` | Redis exporter image registry | `docker.io` |
| `metrics.image.repository` | Redis exporter image name | `bitnami/redis-exporter` |
| `metrics.image.tag` | Redis exporter image tag | `{TAG_NAME}` |
| `metrics.image.registry` | Redis<sup>TM</sup> exporter image registry | `docker.io` |
| `metrics.image.repository` | Redis<sup>TM</sup> exporter image name | `bitnami/redis-exporter` |
| `metrics.image.tag` | Redis<sup>TM</sup> exporter image tag | `{TAG_NAME}` |
| `metrics.image.pullPolicy` | Image pull policy | `IfNotPresent` |
| `metrics.image.pullSecrets` | Specify docker-registry secret names as an array | `nil` |
| `metrics.extraArgs` | Extra arguments for the binary; possible values [here](https://github.com/oliver006/redis_exporter#flags) | {} |
@@ -138,35 +140,39 @@ The following table lists the configurable parameters of the Redis chart and the
| `master.persistence.size` | Size of data volume | `8Gi` |
| `master.persistence.matchLabels` | matchLabels persistent volume selector | `{}` |
| `master.persistence.matchExpressions` | matchExpressions persistent volume selector | `{}` |
<<<<<<< HEAD
| `master.persistence.volumes ` | Additional volumes without creating PVC | `{}` |
=======
| `master.persistence.volumes` | Additional volumes without creating PVC | `{}` |
>>>>>>> 217efe432c3 (Fix table indentation in READMEs)
| `master.statefulset.labels` | Additional labels for redis master StatefulSet | `{}` |
| `master.statefulset.annotations` | Additional annotations for redis master StatefulSet | `{}` |
| `master.statefulset.updateStrategy` | Update strategy for StatefulSet | onDelete |
| `master.statefulset.rollingUpdatePartition` | Partition update strategy | `nil` |
| `master.podLabels` | Additional labels for Redis master pod | {} |
| `master.podAnnotations` | Additional annotations for Redis master pod | {} |
| `master.podLabels` | Additional labels for Redis<sup>TM</sup> master pod | {} |
| `master.podAnnotations` | Additional annotations for Redis<sup>TM</sup> master pod | {} |
| `master.extraEnvVars` | Additional Environment Variables passed to the pod of the master's stateful set set | `[]` |
| `master.extraEnvVarCMs` | Additional Environment Variables ConfigMappassed to the pod of the master's stateful set set | `[]` |
| `master.extraEnvVarsSecret` | Additional Environment Variables Secret passed to the master's stateful set | `[]` |
| `podDisruptionBudget.enabled` | Pod Disruption Budget toggle | `false` |
| `podDisruptionBudget.minAvailable` | Minimum available pods | `1` |
| `podDisruptionBudget.maxUnavailable` | Maximum unavailable pods | `nil` |
| `redisPort` | Redis port (in both master and slaves) | `6379` |
| `podDisruptionBudget.maxUnavailable` | Maximum unavailable | `nil` |
| `redisPort` | Redis<sup>TM</sup> port (in both master and slaves) | `6379` |
| `tls.enabled` | Enable TLS support for replication traffic | `false` |
| `tls.authClients` | Require clients to authenticate or not | `true` |
| `tls.certificatesSecret` | Name of the secret that contains the certificates | `nil` |
| `tls.certFilename` | Certificate filename | `nil` |
| `tls.certKeyFilename` | Certificate key filename | `nil` |
| `tls.certCAFilename` | CA Certificate filename | `nil` |
| `tls.dhParamsFilename` | DH params (in order to support DH based ciphers) | `nil` |
| `master.command` | Redis master entrypoint string. The command `redis-server` is executed if this is not provided. Note this is prepended with `exec` | `/run.sh` |
| `tls.certCAFilename` | CA Certificate filename |`nil` |
| `tls.dhParamsFilename` | DH params (in order to support DH based ciphers) |`nil` |
| `master.command` | Redis<sup>TM</sup> master entrypoint string. The command `redis-server` is executed if this is not provided. Note this is prepended with `exec` | `/run.sh` |
| `master.preExecCmds` | Text to inset into the startup script immediately prior to `master.command`. Use this if you need to run other ad-hoc commands as part of startup | `nil` |
| `master.configmap` | Additional Redis configuration for the master nodes (this value is evaluated as a template) | `nil` |
| `master.disableCommands` | Array of Redis commands to disable (master) | `["FLUSHDB", "FLUSHALL"]` |
| `master.extraFlags` | Redis master additional command line flags | [] |
| `master.nodeSelector` | Redis master Node labels for pod assignment | {"beta.kubernetes.io/arch": "amd64"} |
| `master.tolerations` | Toleration labels for Redis master pod assignment | [] |
| `master.affinity` | Affinity settings for Redis master pod assignment | {} |
| `master.configmap` | Additional Redis<sup>TM</sup> configuration for the master nodes (this value is evaluated as a template) | `nil` |
| `master.disableCommands` | Array of Redis<sup>TM</sup> commands to disable (master) | `["FLUSHDB", "FLUSHALL"]` |
| `master.extraFlags` | Redis<sup>TM</sup> master additional command line flags | [] |
| `master.nodeSelector` | Redis<sup>TM</sup> master Node labels for pod assignment | {"beta.kubernetes.io/arch": "amd64"} |
| `master.tolerations` | Toleration labels for Redis<sup>TM</sup> master pod assignment | [] |
| `master.affinity` | Affinity settings for Redis<sup>TM</sup> master pod assignment | {} |
| `master.schedulerName` | Name of an alternate scheduler | `nil` |
| `master.service.type` | Kubernetes Service type (redis master) | `ClusterIP` |
| `master.service.externalTrafficPolicy` | External traffic policy (when service type is LoadBalancer) | `Cluster` |
@@ -176,7 +182,7 @@ The following table lists the configurable parameters of the Redis chart and the
| `master.service.labels` | Additional labels for redis master service | {} |
| `master.service.loadBalancerIP` | loadBalancerIP if redis master service type is `LoadBalancer` | `nil` |
| `master.service.loadBalancerSourceRanges` | loadBalancerSourceRanges if redis master service type is `LoadBalancer` | `nil` |
| `master.resources` | Redis master CPU/Memory resource requests/limits | Memory: `256Mi`, CPU: `100m` |
| `master.resources` | Redis<sup>TM</sup> master CPU/Memory resource requests/limits | Memory: `256Mi`, CPU: `100m` |
| `master.livenessProbe.enabled` | Turn on and off liveness probe (redis master pod) | `true` |
| `master.livenessProbe.initialDelaySeconds` | Delay before liveness probe is initiated (redis master pod) | `5` |
| `master.livenessProbe.periodSeconds` | How often to perform the probe (redis master pod) | `5` |
@@ -189,8 +195,8 @@ The following table lists the configurable parameters of the Redis chart and the
| `master.readinessProbe.timeoutSeconds` | When the probe times out (redis master pod) | `1` |
| `master.readinessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed (redis master pod) | `1` |
| `master.readinessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `5` |
| `master.shareProcessNamespace` | Redis Master pod `shareProcessNamespace` option. Enables /pause reap zombie PIDs. | `false` |
| `master.priorityClassName` | Redis Master pod priorityClassName | `nil` |
| `master.shareProcessNamespace` | Redis<sup>TM</sup> Master pod `shareProcessNamespace` option. Enables /pause reap zombie PIDs. | `false` |
| `master.priorityClassName` | Redis<sup>TM</sup> Master pod priorityClassName | `nil` |
| `volumePermissions.enabled` | Enable init container that changes volume permissions in the registry (for cases where the default k8s `runAsUser` and `fsUser` values do not work) | `false` |
| `volumePermissions.image.registry` | Init container volume-permissions image registry | `docker.io` |
| `volumePermissions.image.repository` | Init container volume-permissions image name | `bitnami/minideb` |
@@ -205,13 +211,13 @@ The following table lists the configurable parameters of the Redis chart and the
| `slave.service.annotations` | annotations for redis slave service | {} |
| `slave.service.labels` | Additional labels for redis slave service | {} |
| `slave.service.port` | Kubernetes Service port (redis slave) | `6379` |
| `slave.service.loadBalancerIP` | LoadBalancerIP if Redis slave service type is `LoadBalancer` | `nil` |
| `slave.service.loadBalancerSourceRanges` | loadBalancerSourceRanges if Redis slave service type is `LoadBalancer` | `nil` |
| `slave.command` | Redis slave entrypoint string. The command `redis-server` is executed if this is not provided. Note this is prepended with `exec` | `/run.sh` |
| `slave.service.loadBalancerIP` | LoadBalancerIP if Redis<sup>TM</sup> slave service type is `LoadBalancer` | `nil` |
| `slave.service.loadBalancerSourceRanges` | loadBalancerSourceRanges if Redis<sup>TM</sup> slave service type is `LoadBalancer` | `nil` |
| `slave.command` | Redis<sup>TM</sup> slave entrypoint string. The command `redis-server` is executed if this is not provided. Note this is prepended with `exec` | `/run.sh` |
| `slave.preExecCmds` | Text to inset into the startup script immediately prior to `slave.command`. Use this if you need to run other ad-hoc commands as part of startup | `nil` |
| `slave.configmap` | Additional Redis configuration for the slave nodes (this value is evaluated as a template) | `nil` |
| `slave.disableCommands` | Array of Redis commands to disable (slave) | `[FLUSHDB, FLUSHALL]` |
| `slave.extraFlags` | Redis slave additional command line flags | `[]` |
| `slave.configmap` | Additional Redis<sup>TM</sup> configuration for the slave nodes (this value is evaluated as a template) | `nil` |
| `slave.disableCommands` | Array of Redis<sup>TM</sup> commands to disable (slave) | `[FLUSHDB, FLUSHALL]` |
| `slave.extraFlags` | Redis<sup>TM</sup> slave additional command line flags | `[]` |
| `slave.livenessProbe.enabled` | Turn on and off liveness probe (redis slave pod) | `true` |
| `slave.livenessProbe.initialDelaySeconds` | Delay before liveness probe is initiated (redis slave pod) | `5` |
| `slave.livenessProbe.periodSeconds` | How often to perform the probe (redis slave pod) | `5` |
@@ -224,7 +230,7 @@ The following table lists the configurable parameters of the Redis chart and the
| `slave.readinessProbe.timeoutSeconds` | When the probe times out (redis slave pod) | `1` |
| `slave.readinessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed (redis slave pod) | `1` |
| `slave.readinessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. (redis slave pod) | `5` |
| `slave.shareProcessNamespace` | Redis slave pod `shareProcessNamespace` option. Enables /pause reap zombie PIDs. | `false` |
| `slave.shareProcessNamespace` | Redis<sup>TM</sup> slave pod `shareProcessNamespace` option. Enables /pause reap zombie PIDs. | `false` |
| `slave.persistence.enabled` | Use a PVC to persist data (slave node) | `true` |
| `slave.persistence.path` | Path to mount the volume at, to use other images | `/data` |
| `slave.persistence.subPath` | Subdirectory of the volume to mount at | `""` |
@@ -240,35 +246,35 @@ The following table lists the configurable parameters of the Redis chart and the
| `slave.extraEnvVars` | Additional Environment Variables passed to the pod of the slave's stateful set set | `[]` |
| `slave.extraEnvVarCMs` | Additional Environment Variables ConfigMappassed to the pod of the slave's stateful set set | `[]` |
| `masslaveter.extraEnvVarsSecret` | Additional Environment Variables Secret passed to the slave's stateful set | `[]` |
| `slave.podLabels` | Additional labels for Redis slave pod | `master.podLabels` |
| `slave.podAnnotations` | Additional annotations for Redis slave pod | `master.podAnnotations` |
| `slave.podLabels` | Additional labels for Redis<sup>TM</sup> slave pod | `master.podLabels` |
| `slave.podAnnotations` | Additional annotations for Redis<sup>TM</sup> slave pod | `master.podAnnotations` |
| `slave.schedulerName` | Name of an alternate scheduler | `nil` |
| `slave.resources` | Redis slave CPU/Memory resource requests/limits | `{}` |
| `slave.resources` | Redis<sup>TM</sup> slave CPU/Memory resource requests/limits | `{}` |
| `slave.affinity` | Enable node/pod affinity for slaves | {} |
| `slave.tolerations` | Toleration labels for Redis slave pod assignment | [] |
| `slave.spreadConstraints` | [Topology Spread Constraints](https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/) for Redis slave pod | {} |
| `slave.priorityClassName` | Redis Slave pod priorityClassName | `nil` |
| `slave.tolerations` | Toleration labels for Redis<sup>TM</sup> slave pod assignment | [] |
| `slave.spreadConstraints` | [Topology Spread Constraints](https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/) for Redis<sup>TM</sup> slave pod | {} |
| `slave.priorityClassName` | Redis<sup>TM</sup> Slave pod priorityClassName | `nil` |
| `sentinel.enabled` | Enable sentinel containers | `false` |
| `sentinel.usePassword` | Use password for sentinel containers | `true` |
| `sentinel.masterSet` | Name of the sentinel master set | `mymaster` |
| `sentinel.initialCheckTimeout` | Timeout for querying the redis sentinel service for the active sentinel list | `5` |
| `sentinel.quorum` | Quorum for electing a new master | `2` |
| `sentinel.downAfterMilliseconds` | Timeout for detecting a Redis node is down | `60000` |
| `sentinel.downAfterMilliseconds` | Timeout for detecting a Redis<sup>TM</sup> node is down | `60000` |
| `sentinel.failoverTimeout` | Timeout for performing a election failover | `18000` |
| `sentinel.parallelSyncs` | Number of parallel syncs in the cluster | `1` |
| `sentinel.port` | Redis Sentinel port | `26379` |
| `sentinel.configmap` | Additional Redis configuration for the sentinel nodes (this value is evaluated as a template) | `nil` |
| `sentinel.port` | Redis<sup>TM</sup> Sentinel port | `26379` |
| `sentinel.configmap` | Additional Redis<sup>TM</sup> configuration for the sentinel nodes (this value is evaluated as a template) | `nil` |
| `sentinel.staticID` | Enable static IDs for sentinel replicas (If disabled IDs will be randomly generated on startup) | `false` |
| `sentinel.service.type` | Kubernetes Service type (redis sentinel) | `ClusterIP` |
| `sentinel.service.externalTrafficPolicy` | External traffic policy (when service type is LoadBalancer) | `Cluster` |
| `sentinel.service.nodePort` | Kubernetes Service nodePort (redis sentinel) | `nil` |
| `sentinel.service.annotations` | annotations for redis sentinel service | {} |
| `sentinel.service.labels` | Additional labels for redis sentinel service | {} |
| `sentinel.service.redisPort` | Kubernetes Service port for Redis read only operations | `6379` |
| `sentinel.service.sentinelPort` | Kubernetes Service port for Redis sentinel | `26379` |
| `sentinel.service.redisNodePort` | Kubernetes Service node port for Redis read only operations | `` |
| `sentinel.service.sentinelNodePort` | Kubernetes Service node port for Redis sentinel | `` |
| `sentinel.service.loadBalancerIP` | LoadBalancerIP if Redis sentinel service type is `LoadBalancer` | `nil` |
| `sentinel.service.redisPort` | Kubernetes Service port for Redis<sup>TM</sup> read only operations | `6379` |
| `sentinel.service.sentinelPort` | Kubernetes Service port for Redis<sup>TM</sup> sentinel | `26379` |
| `sentinel.service.redisNodePort` | Kubernetes Service node port for Redis<sup>TM</sup> read only operations | `` |
| `sentinel.service.sentinelNodePort` | Kubernetes Service node port for Redis<sup>TM</sup> sentinel | `` |
| `sentinel.service.loadBalancerIP` | LoadBalancerIP if Redis<sup>TM</sup> sentinel service type is `LoadBalancer` | `nil` |
| `sentinel.livenessProbe.enabled` | Turn on and off liveness probe (redis sentinel pod) | `true` |
| `sentinel.livenessProbe.initialDelaySeconds` | Delay before liveness probe is initiated (redis sentinel pod) | `5` |
| `sentinel.livenessProbe.periodSeconds` | How often to perform the probe (redis sentinel container) | `5` |
@@ -281,10 +287,10 @@ The following table lists the configurable parameters of the Redis chart and the
| `sentinel.readinessProbe.timeoutSeconds` | When the probe times out (redis sentinel container) | `1` |
| `sentinel.readinessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed (redis sentinel container) | `1` |
| `sentinel.readinessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. (redis sentinel container) | `5` |
| `sentinel.resources` | Redis sentinel CPU/Memory resource requests/limits | `{}` |
| `sentinel.image.registry` | Redis Sentinel Image registry | `docker.io` |
| `sentinel.image.repository` | Redis Sentinel Image name | `bitnami/redis-sentinel` |
| `sentinel.image.tag` | Redis Sentinel Image tag | `{TAG_NAME}` |
| `sentinel.resources` | Redis<sup>TM</sup> sentinel CPU/Memory resource requests/limits | `{}` |
| `sentinel.image.registry` | Redis<sup>TM</sup> Sentinel Image registry | `docker.io` |
| `sentinel.image.repository` | Redis<sup>TM</sup> Sentinel Image name | `bitnami/redis-sentinel` |
| `sentinel.image.tag` | Redis<sup>TM</sup> Sentinel Image tag | `{TAG_NAME}` |
| `sentinel.image.pullPolicy` | Image pull policy | `IfNotPresent` |
| `sentinel.image.pullSecrets` | Specify docker-registry secret names as an array | `nil` |
| `sentinel.extraEnvVars` | Additional Environment Variables passed to the pod of the sentinel node stateful set set | `[]` |
@@ -309,7 +315,7 @@ $ helm install my-release \
bitnami/redis
```
The above command sets the Redis server password to `secretpassword`.
The above command sets the Redis<sup>TM</sup> server password to `secretpassword`.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
@@ -319,7 +325,7 @@ $ helm install my-release -f values.yaml bitnami/redis
> **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 pod as it attempts to write to the `/bitnami` directory. Consider installing Redis with `--set persistence.enabled=false`. 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<sup>TM</sup> pod as it attempts to write to the `/bitnami` directory. Consider installing Redis<sup>TM</sup> with `--set persistence.enabled=false`. See minikube issue [1990](https://github.com/kubernetes/minikube/issues/1990) for more information.
## Configuration and installation details
@@ -351,28 +357,28 @@ This chart includes a `values-production.yaml` file where you can find some para
+ metrics.enabled: true
```
### Change Redis version
### Change Redis<sup>TM</sup> version
To modify the Redis version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/redis/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters.
To modify the Redis<sup>TM</sup> version used in this chart you can specify a [valid image tag](https://hub.docker.com/r/bitnami/redis/tags/) using the `image.tag` parameter. For example, `image.tag=X.Y.Z`. This approach is also applicable to other images like exporters.
### Cluster topologies
#### Default: Master-Slave
When installing the chart with `cluster.enabled=true`, it will deploy a Redis master StatefulSet (only one master node allowed) and a Redis slave StatefulSet. The slaves will be read-replicas of the master. Two services will be exposed:
When installing the chart with `cluster.enabled=true`, it will deploy a Redis<sup>TM</sup> master StatefulSet (only one master node allowed) and a Redis<sup>TM</sup> slave StatefulSet. The slaves will be read-replicas of the master. Two services will be exposed:
- Redis Master service: Points to the master, where read-write operations can be performed
- Redis Slave service: Points to the slaves, where only read operations are allowed.
- Redis<sup>TM</sup> Master service: Points to the master, where read-write operations can be performed
- Redis<sup>TM</sup> Slave service: Points to the slaves, where only read operations are allowed.
In case the master crashes, the slaves will wait until the master node is respawned again by the Kubernetes Controller Manager.
#### Master-Slave with Sentinel
When installing the chart with `cluster.enabled=true` and `sentinel.enabled=true`, it will deploy a Redis master StatefulSet (only one master allowed) and a Redis slave StatefulSet. In this case, the pods will contain an extra container with Redis Sentinel. This container will form a cluster of Redis Sentinel nodes, which will promote a new master in case the actual one fails. In addition to this, only one service is exposed:
When installing the chart with `cluster.enabled=true` and `sentinel.enabled=true`, it will deploy a Redis<sup>TM</sup> master StatefulSet (only one master allowed) and a Redis<sup>TM</sup> slave StatefulSet. In this case, the pods will contain an extra container with Redis<sup>TM</sup> Sentinel. This container will form a cluster of Redis<sup>TM</sup> Sentinel nodes, which will promote a new master in case the actual one fails. In addition to this, only one service is exposed:
- Redis service: Exposes port 6379 for Redis read-only operations and port 26379 for accessing Redis Sentinel.
- Redis<sup>TM</sup> service: Exposes port 6379 for Redis<sup>TM</sup> read-only operations and port 26379 for accessing Redis<sup>TM</sup> Sentinel.
For read-only operations, access the service using port 6379. For write operations, it's necessary to access the Redis Sentinel cluster and query the current master using the command below (using redis-cli or similar:
For read-only operations, access the service using port 6379. For write operations, it's necessary to access the Redis<sup>TM</sup> Sentinel cluster and query the current master using the command below (using redis-cli or similar:
```
SENTINEL get-master-addr-by-name <name of your MasterSet. Example: mymaster>
@@ -382,7 +388,7 @@ This command will return the address of the current master, which can be accesse
In case the current master crashes, the Sentinel containers will elect a new master node.
### Using password file
To use a password file for Redis you need to create a secret containing the password.
To use a password file for Redis<sup>TM</sup> you need to create a secret containing the password.
> *NOTE*: It is important that the file with the password must be called `redis-password`
@@ -430,7 +436,7 @@ The chart optionally can start a metrics exporter for [prometheus](https://prome
### Host Kernel Settings
Redis 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<sup>TM</sup> 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:
```
@@ -565,7 +571,7 @@ helm install new-redis -f values.yaml . --set cluster.enabled=true --set clus
## NetworkPolicy
To enable network policy for Redis, install
To enable network policy for Redis<sup>TM</sup>, 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`.
@@ -575,7 +581,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. This label will be displayed in the output
able to connect to Redis<sup>TM</sup>. 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:
@@ -617,15 +623,15 @@ For releases with `metrics.enabled: true` the default tag for the exporter image
### To 7.0.0
This version causes a change in the Redis Master StatefulSet definition, so the command helm upgrade would not work out of the box. As an alternative, one of the following could be done:
This version causes a change in the Redis<sup>TM</sup> Master StatefulSet definition, so the command helm upgrade would not work out of the box. As an alternative, one of the following could be done:
- Recommended: Create a clone of the Redis Master PVC (for example, using projects like [this one](https://github.com/edseymour/pvc-transfer)). Then launch a fresh release reusing this cloned PVC.
- Recommended: Create a clone of the Redis<sup>TM</sup> Master PVC (for example, using projects like [this one](https://github.com/edseymour/pvc-transfer)). Then launch a fresh release reusing this cloned PVC.
```
helm install my-release bitnami/redis --set persistence.existingClaim=<NEW PVC>
```
- Alternative (not recommended, do at your own risk): `helm delete --purge` does not remove the PVC assigned to the Redis Master StatefulSet. As a consequence, the following commands can be done to upgrade the release
- Alternative (not recommended, do at your own risk): `helm delete --purge` does not remove the PVC assigned to the Redis<sup>TM</sup> Master StatefulSet. As a consequence, the following commands can be done to upgrade the release
```
helm delete --purge <RELEASE>
@@ -639,7 +645,7 @@ Some values have changed as well:
- `master.port` and `slave.port` have been changed to `redisPort` (same value for both master and slaves)
- `master.securityContext` and `slave.securityContext` have been changed to `securityContext`(same values for both master and slaves)
By default, the upgrade will not change the cluster topology. In case you want to use Redis Sentinel, you must explicitly set `sentinel.enabled` to `true`.
By default, the upgrade will not change the cluster topology. In case you want to use Redis<sup>TM</sup> Sentinel, you must explicitly set `sentinel.enabled` to `true`.
### To 6.0.0
@@ -667,13 +673,13 @@ It also fixes https://github.com/helm/charts/issues/7726 where a deployment `ext
Finally, it fixes https://github.com/helm/charts/issues/7803 by removing mutable labels in `spec.VolumeClaimTemplate.metadata.labels` so that it is upgradable.
In order to upgrade, delete the Redis StatefulSet before upgrading:
In order to upgrade, delete the Redis<sup>TM</sup> StatefulSet before upgrading:
```bash
kubectl delete statefulsets.apps --cascade=false my-release-redis-master
```
And edit the Redis slave (and metrics if enabled) deployment:
And edit the Redis<sup>TM</sup> slave (and metrics if enabled) deployment:
```bash
kubectl patch deployments my-release-redis-slave --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
@@ -709,10 +715,10 @@ When deployed with sentinel enabled, only a group of nodes is deployed and the m
### To 9.0.0
The metrics exporter has been changed from a separate deployment to a sidecar container, due to the latest changes in the Redis exporter code. Check the [official page](https://github.com/oliver006/redis_exporter/) for more information. The metrics container image was changed from oliver006/redis_exporter to bitnami/redis-exporter (Bitnami's maintained package of oliver006/redis_exporter).
The metrics exporter has been changed from a separate deployment to a sidecar container, due to the latest changes in the Redis<sup>TM</sup> exporter code. Check the [official page](https://github.com/oliver006/redis_exporter/) for more information. The metrics container image was changed from oliver006/redis_exporter to bitnami/redis-exporter (Bitnami's maintained package of oliver006/redis_exporter).
### To 7.0.0
In order to improve the performance in case of slave failure, we added persistence to the read-only slaves. That means that we moved from Deployment to StatefulSets. This should not affect upgrades from previous versions of the chart, as the deployments did not contain any persistence at all.
This version also allows enabling Redis Sentinel containers inside of the Redis Pods (feature disabled by default). In case the master crashes, a new Redis node will be elected as master. In order to query the current master (no redis master service is exposed), you need to query first the Sentinel cluster. Find more information [in this section](#master-slave-with-sentinel).
This version also allows enabling Redis<sup>TM</sup> Sentinel containers inside of the Redis<sup>TM</sup> Pods (feature disabled by default). In case the master crashes, a new Redis<sup>TM</sup> node will be elected as master. In order to query the current master (no redis master service is exposed), you need to query first the Sentinel cluster. Find more information [in this section](#master-slave-with-sentinel).

106
bitnami/redis/ci/production-sentinel-values.yaml
View File

@@ -9,13 +9,13 @@ global:
# storageClass: myStorageClass
redis: {}
## Bitnami Redis image version
## Bitnami Redis(TM) image version
## ref: https://hub.docker.com/r/bitnami/redis/tags/
##
image:
registry: docker.io
repository: bitnami/redis
## Bitnami Redis image tag
## Bitnami Redis(TM) image tag
## ref: https://github.com/bitnami/bitnami-docker-redis#supported-tags-and-respective-dockerfile-links
##
tag: 5.0.9-debian-10-r0
@@ -51,13 +51,13 @@ sentinel:
## Require password authentication on the sentinel itself
## ref: https://redis.io/topics/sentinel
usePassword: true
## Bitnami Redis Sentintel image version
## Bitnami Redis(TM) Sentintel image version
## ref: https://hub.docker.com/r/bitnami/redis-sentinel/tags/
##
image:
registry: docker.io
repository: bitnami/redis-sentinel
## Bitnami Redis image tag
## Bitnami Redis(TM) image tag
## ref: https://github.com/bitnami/bitnami-docker-redis-sentinel#supported-tags-and-respective-dockerfile-links
##
tag: 5.0.9-debian-10-r0
@@ -79,7 +79,7 @@ sentinel:
failoverTimeout: 18000
parallelSyncs: 1
port: 26379
## Additional Redis configuration for the sentinel nodes
## Additional Redis(TM) configuration for the sentinel nodes
## ref: https://redis.io/topics/config
##
configmap:
@@ -88,7 +88,7 @@ sentinel:
## If enabled, each replicas will have a constant ID on each start-up
##
staticID: false
## Configure extra options for Redis Sentinel liveness and readiness probes
## Configure extra options for Redis(TM) Sentinel liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
##
livenessProbe:
@@ -107,15 +107,15 @@ sentinel:
failureThreshold: 5
customLivenessProbe: {}
customReadinessProbe: {}
## Redis Sentinel resource requests and limits
## Redis(TM) Sentinel resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
# resources:
# requests:
# memory: 256Mi
# cpu: 100m
## Redis Sentinel Service properties
## Redis(TM) Sentinel Service properties
service:
## Redis Sentinel Service type
## Redis(TM) Sentinel Service type
type: ClusterIP
sentinelPort: 26379
redisPort: 6379
@@ -144,8 +144,8 @@ networkPolicy:
enabled: true
## The Policy model to apply. When set to false, only pods with the correct
## client label will have network access to the port Redis is listening
## on. When true, Redis will accept connections from any source
## client label will have network access to the port Redis(TM) is listening
## on. When true, Redis(TM) will accept connections from any source
## (with the correct destination port).
##
# allowExternal: true
@@ -181,7 +181,7 @@ rbac:
# - gce.unprivileged
rules: []
## Redis pod Security Context
## Redis(TM) pod Security Context
securityContext:
enabled: true
fsGroup: 1001
@@ -196,14 +196,14 @@ securityContext:
## Use password authentication
usePassword: true
## Redis password (both master and slave)
## Redis(TM) password (both master and slave)
## Defaults to a random 10-character alphanumeric string if not set and usePassword is true
## ref: https://github.com/bitnami/bitnami-docker-redis#setting-the-server-password-on-first-run
##
password:
## Use existing secret (ignores previous password)
# existingSecret:
## Password key to be retrieved from Redis secret
## Password key to be retrieved from Redis(TM) secret
##
# existingSecretPasswordKey:
@@ -217,23 +217,23 @@ persistence:
## If defined, PVC must be created manually before volume will be bound
existingClaim:
# Redis port
# Redis(TM) port
redisPort: 6379
##
## Redis Master parameters
## Redis(TM) Master parameters
##
master:
## Redis command arguments
## Redis(TM) command arguments
##
## Can be used to specify command line arguments, for example:
##
command: "/run.sh"
## Additional Redis configuration for the master nodes
## Additional Redis(TM) configuration for the master nodes
## ref: https://redis.io/topics/config
##
configmap:
## Redis additional command line flags
## Redis(TM) additional command line flags
##
## Can be used to specify command line flags, for example:
##
@@ -241,9 +241,9 @@ master:
## - "--maxmemory-policy volatile-ttl"
## - "--repl-backlog-size 1024mb"
extraFlags: []
## Comma-separated list of Redis commands to disable
## Comma-separated list of Redis(TM) commands to disable
##
## Can be used to disable Redis commands for security reasons.
## Can be used to disable Redis(TM) commands for security reasons.
## Commands will be completely disabled by renaming each to an empty string.
## ref: https://redis.io/topics/security#disabling-of-specific-commands
##
@@ -251,12 +251,12 @@ master:
- FLUSHDB
- FLUSHALL
## Redis Master additional pod labels and annotations
## Redis(TM) Master additional pod labels and annotations
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
podLabels: {}
podAnnotations: {}
## Redis Master resource requests and limits
## Redis(TM) Master resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
# resources:
# requests:
@@ -267,7 +267,7 @@ master:
##
# schedulerName:
## Configure extra options for Redis Master liveness and readiness probes
## Configure extra options for Redis(TM) Master liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
##
livenessProbe:
@@ -307,19 +307,19 @@ master:
customLivenessProbe: {}
customReadinessProbe: {}
## Redis Master Node selectors and tolerations for pod assignment
## Redis(TM) Master Node selectors and tolerations for pod assignment
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#taints-and-tolerations-beta-feature
##
# nodeSelector: {"beta.kubernetes.io/arch": "amd64"}
# tolerations: []
## Redis Master pod/node affinity/anti-affinity
## Redis(TM) Master pod/node affinity/anti-affinity
##
affinity: {}
## Redis Master Service properties
## Redis(TM) Master Service properties
service:
## Redis Master Service type
## Redis(TM) Master Service type
type: ClusterIP
port: 6379
@@ -343,7 +343,7 @@ master:
persistence:
enabled: true
## The path the volume will be mounted at, useful when using different
## Redis images.
## Redis(TM) images.
path: /data
## The subdirectory of the volume to mount to, useful in dev environments
## and one PV for multiple services.
@@ -372,21 +372,21 @@ master:
## https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#partitions
# rollingUpdatePartition:
## Redis Master pod priorityClassName
## Redis(TM) Master pod priorityClassName
##
priorityClassName: {}
##
## Redis Slave properties
## Redis(TM) Slave properties
## Note: service.type is a mandatory parameter
## The rest of the parameters are either optional or, if undefined, will inherit those declared in Redis Master
## The rest of the parameters are either optional or, if undefined, will inherit those declared in Redis(TM) Master
##
slave:
## Slave Service properties
service:
## Redis Slave Service type
## Redis(TM) Slave Service type
type: ClusterIP
## Redis port
## Redis(TM) port
port: 6379
## Specify the nodePort value for the LoadBalancer and NodePort service types.
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
@@ -402,27 +402,27 @@ slave:
loadBalancerIP:
# loadBalancerSourceRanges: ["10.0.0.0/8"]
## Redis slave port
## Redis(TM) slave port
port: 6379
## Can be used to specify command line arguments, for example:
##
command: "/run.sh"
## Additional Redis configuration for the slave nodes
## Additional Redis(TM) configuration for the slave nodes
## ref: https://redis.io/topics/config
##
configmap:
## Redis extra flags
## Redis(TM) extra flags
extraFlags: []
## List of Redis commands to disable
## List of Redis(TM) commands to disable
disableCommands:
- FLUSHDB
- FLUSHALL
## Redis Slave pod/node affinity/anti-affinity
## Redis(TM) Slave pod/node affinity/anti-affinity
##
affinity: {}
## Configure extra options for Redis Slave liveness and readiness probes
## Configure extra options for Redis(TM) Slave liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
##
livenessProbe:
@@ -462,13 +462,13 @@ slave:
customLivenessProbe: {}
customReadinessProbe: {}
## Redis slave Resource
## Redis(TM) slave Resource
# resources:
# requests:
# memory: 256Mi
# cpu: 100m
## Redis slave selectors and tolerations for pod assignment
## Redis(TM) slave selectors and tolerations for pod assignment
# nodeSelector: {"beta.kubernetes.io/arch": "amd64"}
# tolerations: []
@@ -477,11 +477,11 @@ slave:
##
# schedulerName:
## Redis slave pod Annotation and Labels
## Redis(TM) slave pod Annotation and Labels
podLabels: {}
podAnnotations: {}
## Redis slave pod priorityClassName
## Redis(TM) slave pod priorityClassName
# priorityClassName: {}
## Enable persistence using Persistent Volume Claims
@@ -490,7 +490,7 @@ slave:
persistence:
enabled: true
## The path the volume will be mounted at, useful when using different
## Redis images.
## Redis(TM) images.
path: /data
## The subdirectory of the volume to mount to, useful in dev environments
## and one PV for multiple services.
@@ -572,7 +572,7 @@ metrics:
enabled: false
additionalLabels: {}
namespace: ""
## Redis prometheus rules
## Redis(TM) prometheus rules
## These are just examples rules, please adapt them to your needs.
## Make sure to constraint the rules to the current postgresql service.
# rules:
@@ -582,8 +582,8 @@ metrics:
# labels:
# severity: error
# annotations:
# summary: Redis instance {{ "{{ $labels.instance }}" }} down
# description: Redis instance {{ "{{ $labels.instance }}" }} is down
# summary: Redis(TM) instance {{ "{{ $labels.instance }}" }} down
# description: Redis(TM) instance {{ "{{ $labels.instance }}" }} is down
# - alert: RedisMemoryHigh
# expr: >
# redis_memory_used_bytes{service="{{ template "redis.fullname" . }}-metrics"} * 100
@@ -594,9 +594,9 @@ metrics:
# labels:
# severity: error
# annotations:
# summary: Redis instance {{ "{{ $labels.instance }}" }} is using too much memory
# summary: Redis(TM) instance {{ "{{ $labels.instance }}" }} is using too much memory
# description: |
# Redis instance {{ "{{ $labels.instance }}" }} is using {{ "{{ $value }}" }}% of its available memory.
# Redis(TM) instance {{ "{{ $labels.instance }}" }} is using {{ "{{ $value }}" }}% of its available memory.
# - alert: RedisKeyEviction
# expr: |
# increase(redis_evicted_keys_total{service="{{ template "redis.fullname" . }}-metrics"}[5m]) > 0
@@ -604,9 +604,9 @@ metrics:
# labels:
# severity: error
# annotations:
# summary: Redis instance {{ "{{ $labels.instance }}" }} has evicted keys
# summary: Redis(TM) instance {{ "{{ $labels.instance }}" }} has evicted keys
# description: |
# Redis instance {{ "{{ $labels.instance }}" }} has evicted {{ "{{ $value }}" }} keys in the last 5 minutes.
# Redis(TM) instance {{ "{{ $labels.instance }}" }} has evicted {{ "{{ $value }}" }} keys in the last 5 minutes.
rules: []
## Metrics exporter pod priorityClassName
@@ -642,7 +642,7 @@ volumePermissions:
# memory: 128Mi
# cpu: 100m
## Redis config file
## Redis(TM) config file
## ref: https://redis.io/topics/config
##
configmap: |-

10
bitnami/redis/templates/NOTES.txt
View File

@@ -8,7 +8,7 @@
WARNING
By specifying "master.service.type=LoadBalancer" and "usePassword=false" you have
most likely exposed the Redis service externally without any authentication
most likely exposed the Redis(TM) service externally without any authentication
mechanism.
For security reasons, we strongly suggest that you switch to "ClusterIP" or
@@ -40,7 +40,7 @@ Redis can be accessed via port {{ .Values.sentinel.service.redisPort }} on the f
{{ template "redis.fullname" . }}.{{ .Release.Namespace }}.svc.{{ .Values.clusterDomain }} for read only operations
For read/write operations, first access the Redis Sentinel cluster, which is available in port {{ .Values.sentinel.service.sentinelPort }} using the same domain name above.
For read/write operations, first access the Redis(TM) Sentinel cluster, which is available in port {{ .Values.sentinel.service.sentinelPort }} using the same domain name above.
{{- else }}
Redis can be accessed via port {{ .Values.redisPort }} on the following DNS names from within your cluster:
@@ -62,9 +62,9 @@ To get your password run:
export REDIS_PASSWORD=$(kubectl get secret --namespace {{ .Release.Namespace }} {{ template "redis.secretName" . }} -o jsonpath="{.data.redis-password}" | base64 --decode)
{{- end }}
To connect to your Redis server:
To connect to your Redis(TM) server:
1. Run a Redis pod that you can use as a client:
1. Run a Redis(TM) pod that you can use as a client:
{{- if .Values.tls.enabled }}
kubectl run --namespace {{ .Release.Namespace }} {{ template "redis.fullname" . }}-client --restart='Never' --env REDIS_PASSWORD=$REDIS_PASSWORD --image {{ template "redis.image" . }} --command -- sleep infinity
@@ -87,7 +87,7 @@ To connect to your Redis server:
--image {{ template "redis.image" . }} -- bash
{{- end }}
2. Connect using the Redis CLI:
2. Connect using the Redis(TM) CLI:
{{- if .Values.cluster.enabled }}
{{- if .Values.sentinel.enabled }}

10
bitnami/redis/templates/_helpers.tpl
View File

@@ -65,7 +65,7 @@ Return the appropriate apiVersion for PodSecurityPolicy.
{{- end -}}
{{/*
Return the proper Redis image name
Return the proper Redis(TM) image name
*/}}
{{- define "redis.image" -}}
{{- $registryName := .Values.image.registry -}}
@@ -88,7 +88,7 @@ Also, we can't use a single if because lazy evaluation is not an option
{{- end -}}
{{/*
Return the proper Redis Sentinel image name
Return the proper Redis(TM) Sentinel image name
*/}}
{{- define "sentinel.image" -}}
{{- $registryName := .Values.sentinel.image.registry -}}
@@ -209,7 +209,7 @@ Get the password secret.
{{- end -}}
{{/*
Get the password key to be retrieved from Redis secret.
Get the password key to be retrieved from Redis(TM) secret.
*/}}
{{- define "redis.secretPasswordKey" -}}
{{- if and .Values.existingSecret .Values.existingSecretPasswordKey -}}
@@ -220,7 +220,7 @@ Get the password key to be retrieved from Redis secret.
{{- end -}}
{{/*
Return Redis password
Return Redis(TM) password
*/}}
{{- define "redis.password" -}}
{{- if not (empty .Values.global.redis.password) }}
@@ -398,7 +398,7 @@ Compile all warnings into a single message, and call fail.
{{- end -}}
{{- end -}}
{{/* Validate values of Redis - spreadConstrainsts K8s version */}}
{{/* Validate values of Redis(TM) - spreadConstrainsts K8s version */}}
{{- define "redis.validateValues.spreadConstraints" -}}
{{- if and (semverCompare "<1.16-0" .Capabilities.KubeVersion.GitVersion) .Values.slave.spreadConstraints -}}
redis: spreadConstraints

114
bitnami/redis/values-production.yaml
View File

@@ -9,13 +9,13 @@ global:
# storageClass: myStorageClass
redis: {}
## Bitnami Redis image version
## Bitnami Redis(TM) image version
## ref: https://hub.docker.com/r/bitnami/redis/tags/
##
image:
registry: docker.io
repository: bitnami/redis
## Bitnami Redis image tag
## Bitnami Redis(TM) image tag
## ref: https://github.com/bitnami/bitnami-docker-redis#supported-tags-and-respective-dockerfile-links
##
tag: 6.0.9-debian-10-r66
@@ -51,13 +51,13 @@ sentinel:
## Require password authentication on the sentinel itself
## ref: https://redis.io/topics/sentinel
usePassword: true
## Bitnami Redis Sentintel image version
## Bitnami Redis(TM) Sentintel image version
## ref: https://hub.docker.com/r/bitnami/redis-sentinel/tags/
##
image:
registry: docker.io
repository: bitnami/redis-sentinel
## Bitnami Redis image tag
## Bitnami Redis(TM) image tag
## ref: https://github.com/bitnami/bitnami-docker-redis-sentinel#supported-tags-and-respective-dockerfile-links
##
tag: 6.0.9-debian-10-r66
@@ -79,7 +79,7 @@ sentinel:
failoverTimeout: 18000
parallelSyncs: 1
port: 26379
## Additional Redis configuration for the sentinel nodes
## Additional Redis(TM) configuration for the sentinel nodes
## ref: https://redis.io/topics/config
##
configmap:
@@ -88,7 +88,7 @@ sentinel:
## If enabled, each replicas will have a constant ID on each start-up
##
staticID: false
## Configure extra options for Redis Sentinel liveness and readiness probes
## Configure extra options for Redis(TM) Sentinel liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
##
livenessProbe:
@@ -107,15 +107,15 @@ sentinel:
failureThreshold: 5
customLivenessProbe: {}
customReadinessProbe: {}
## Redis Sentinel resource requests and limits
## Redis(TM) Sentinel resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
# resources:
# requests:
# memory: 256Mi
# cpu: 100m
## Redis Sentinel Service properties
## Redis(TM) Sentinel Service properties
service:
## Redis Sentinel Service type
## Redis(TM) Sentinel Service type
type: ClusterIP
sentinelPort: 26379
redisPort: 6379
@@ -137,9 +137,11 @@ sentinel:
annotations: {}
labels: {}
loadBalancerIP:
## Additional commands to run prior to starting Redis node with sentinel
## Additional commands to run prior to starting Redis(TM) node with sentinel
##
preExecCmds: ""
## An array to add extra env var to the sentinel node configurations
## For example:
## extraEnvVars:
@@ -170,8 +172,8 @@ networkPolicy:
enabled: true
## The Policy model to apply. When set to false, only pods with the correct
## client label will have network access to the port Redis is listening
## on. When true, Redis will accept connections from any source
## client label will have network access to the port Redis(TM) is listening
## on. When true, Redis(TM) will accept connections from any source
## (with the correct destination port).
##
# allowExternal: true
@@ -210,7 +212,7 @@ rbac:
# - gce.unprivileged
rules: []
## Redis pod Security Context
## Redis(TM) pod Security Context
securityContext:
enabled: true
fsGroup: 1001
@@ -231,14 +233,14 @@ containerSecurityContext:
## Use password authentication
usePassword: true
## Redis password (both master and slave)
## Redis(TM) password (both master and slave)
## Defaults to a random 10-character alphanumeric string if not set and usePassword is true
## ref: https://github.com/bitnami/bitnami-docker-redis#setting-the-server-password-on-first-run
##
password:
## Use existing secret (ignores previous password)
# existingSecret:
## Password key to be retrieved from Redis secret
## Password key to be retrieved from Redis(TM) secret
##
# existingSecretPasswordKey:
@@ -252,7 +254,7 @@ persistence:
## If defined, PVC must be created manually before volume will be bound
existingClaim:
# Redis port
# Redis(TM) port
redisPort: 6379
##
@@ -281,32 +283,32 @@ tls:
# dhParamsFilename:
##
## Redis Master parameters
## Redis(TM) Master parameters
##
master:
## Redis command arguments
## Redis(TM) command arguments
##
## Can be used to specify command line arguments, for example:
## Note `exec` is prepended to command
##
command: "/run.sh"
## Additional commands to run prior to starting Redis
## Additional commands to run prior to starting Redis(TM)
##
preExecCmds: ""
## Additional Redis configuration for the master nodes
## Additional Redis(TM) configuration for the master nodes
## ref: https://redis.io/topics/config
##
configmap:
## Redis additional command line flags
## Redis(TM) additional command line flags
##
## Can be used to specify command line flags, for example:
## extraFlags:
## - "--maxmemory-policy volatile-ttl"
## - "--repl-backlog-size 1024mb"
extraFlags: []
## Comma-separated list of Redis commands to disable
## Comma-separated list of Redis(TM) commands to disable
##
## Can be used to disable Redis commands for security reasons.
## Can be used to disable Redis(TM) commands for security reasons.
## Commands will be completely disabled by renaming each to an empty string.
## ref: https://redis.io/topics/security#disabling-of-specific-commands
##
@@ -314,12 +316,12 @@ master:
- FLUSHDB
- FLUSHALL
## Redis Master additional pod labels and annotations
## Redis(TM) Master additional pod labels and annotations
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
podLabels: {}
podAnnotations: {}
## Redis Master resource requests and limits
## Redis(TM) Master resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
# resources:
# requests:
@@ -337,7 +339,7 @@ master:
# Enable this only if customLivenessProbe or customReadinessProbe is used and zombie PIDs are accumulating.
# Ref: https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/
shareProcessNamespace: false
## Configure extra options for Redis Master liveness and readiness probes
## Configure extra options for Redis(TM) Master liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
##
livenessProbe:
@@ -377,19 +379,19 @@ master:
customLivenessProbe: {}
customReadinessProbe: {}
## Redis Master Node selectors and tolerations for pod assignment
## Redis(TM) Master Node selectors and tolerations for pod assignment
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#taints-and-tolerations-beta-feature
##
# nodeSelector: {"beta.kubernetes.io/arch": "amd64"}
# tolerations: []
## Redis Master pod/node affinity/anti-affinity
## Redis(TM) Master pod/node affinity/anti-affinity
##
affinity: {}
## Redis Master Service properties
## Redis(TM) Master Service properties
service:
## Redis Master Service type
## Redis(TM) Master Service type
type: ClusterIP
port: 6379
@@ -417,7 +419,7 @@ master:
persistence:
enabled: true
## The path the volume will be mounted at, useful when using different
## Redis images.
## Redis(TM) images.
path: /data
## The subdirectory of the volume to mount to, useful in dev environments
## and one PV for multiple services.
@@ -451,7 +453,7 @@ master:
## https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#partitions
# rollingUpdatePartition:
## Redis Master pod priorityClassName
## Redis(TM) Master pod priorityClassName
##
priorityClassName: ''
@@ -476,16 +478,16 @@ master:
extraEnvVarsSecret: []
##
## Redis Slave properties
## Redis(TM) Slave properties
## Note: service.type is a mandatory parameter
## The rest of the parameters are either optional or, if undefined, will inherit those declared in Redis Master
## The rest of the parameters are either optional or, if undefined, will inherit those declared in Redis(TM) Master
##
slave:
## Slave Service properties
service:
## Redis Slave Service type
## Redis(TM) Slave Service type
type: ClusterIP
## Redis port
## Redis(TM) port
port: 6379
## External traffic policy (when service type is LoadBalancer)
@@ -506,27 +508,27 @@ slave:
loadBalancerIP:
# loadBalancerSourceRanges: ["10.0.0.0/8"]
## Redis slave port
## Redis(TM) slave port
port: 6379
## Can be used to specify command line arguments, for example:
## Note `exec` is prepended to command
##
command: "/run.sh"
## Additional commands to run prior to starting Redis
## Additional commands to run prior to starting Redis(TM)
##
preExecCmds: ""
## Additional Redis configuration for the slave nodes
## Additional Redis(TM) configuration for the slave nodes
## ref: https://redis.io/topics/config
##
configmap:
## Redis extra flags
## Redis(TM) extra flags
extraFlags: []
## List of Redis commands to disable
## List of Redis(TM) commands to disable
disableCommands:
- FLUSHDB
- FLUSHALL
## Redis Slave pod/node affinity/anti-affinity
## Redis(TM) Slave pod/node affinity/anti-affinity
##
affinity: {}
@@ -545,7 +547,7 @@ slave:
# Enable this only if customLivenessProbe or customReadinessProbe is used and zombie PIDs are accumulating.
# Ref: https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/
shareProcessNamespace: false
## Configure extra options for Redis Slave liveness and readiness probes
## Configure extra options for Redis(TM) Slave liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
##
livenessProbe:
@@ -585,13 +587,13 @@ slave:
customLivenessProbe: {}
customReadinessProbe: {}
## Redis slave Resource
## Redis(TM) slave Resource
# resources:
# requests:
# memory: 256Mi
# cpu: 100m
## Redis slave selectors and tolerations for pod assignment
## Redis(TM) slave selectors and tolerations for pod assignment
# nodeSelector: {"beta.kubernetes.io/arch": "amd64"}
# tolerations: []
@@ -600,11 +602,11 @@ slave:
##
# schedulerName:
## Redis slave pod Annotation and Labels
## Redis(TM) slave pod Annotation and Labels
podLabels: {}
podAnnotations: {}
## Redis slave pod priorityClassName
## Redis(TM) slave pod priorityClassName
# priorityClassName: ''
## Enable persistence using Persistent Volume Claims
@@ -613,7 +615,7 @@ slave:
persistence:
enabled: true
## The path the volume will be mounted at, useful when using different
## Redis images.
## Redis(TM) images.
path: /data
## The subdirectory of the volume to mount to, useful in dev environments
## and one PV for multiple services.
@@ -735,7 +737,7 @@ metrics:
enabled: false
additionalLabels: {}
namespace: ""
## Redis prometheus rules
## Redis(TM) prometheus rules
## These are just examples rules, please adapt them to your needs.
## Make sure to constraint the rules to the current redis service.
# rules:
@@ -745,8 +747,8 @@ metrics:
# labels:
# severity: error
# annotations:
# summary: Redis instance {{ "{{ $labels.instance }}" }} down
# description: Redis instance {{ "{{ $labels.instance }}" }} is down
# summary: Redis(TM) instance {{ "{{ $labels.instance }}" }} down
# description: Redis(TM) instance {{ "{{ $labels.instance }}" }} is down
# - alert: RedisMemoryHigh
# expr: >
# redis_memory_used_bytes{service="{{ template "redis.fullname" . }}-metrics"} * 100
@@ -757,9 +759,9 @@ metrics:
# labels:
# severity: error
# annotations:
# summary: Redis instance {{ "{{ $labels.instance }}" }} is using too much memory
# summary: Redis(TM) instance {{ "{{ $labels.instance }}" }} is using too much memory
# description: |
# Redis instance {{ "{{ $labels.instance }}" }} is using {{ "{{ $value }}" }}% of its available memory.
# Redis(TM) instance {{ "{{ $labels.instance }}" }} is using {{ "{{ $value }}" }}% of its available memory.
# - alert: RedisKeyEviction
# expr: |
# increase(redis_evicted_keys_total{service="{{ template "redis.fullname" . }}-metrics"}[5m]) > 0
@@ -767,9 +769,9 @@ metrics:
# labels:
# severity: error
# annotations:
# summary: Redis instance {{ "{{ $labels.instance }}" }} has evicted keys
# summary: Redis(TM) instance {{ "{{ $labels.instance }}" }} has evicted keys
# description: |
# Redis instance {{ "{{ $labels.instance }}" }} has evicted {{ "{{ $value }}" }} keys in the last 5 minutes.
# Redis(TM) instance {{ "{{ $labels.instance }}" }} has evicted {{ "{{ $value }}" }} keys in the last 5 minutes.
rules: []
## Metrics exporter pod priorityClassName
@@ -822,7 +824,7 @@ volumePermissions:
securityContext:
runAsUser: 0
## Redis config file
## Redis(TM) config file
## ref: https://redis.io/topics/config
##
configmap: |-

114
bitnami/redis/values.yaml
View File

@@ -9,13 +9,13 @@ global:
# storageClass: myStorageClass
redis: {}
## Bitnami Redis image version
## Bitnami Redis(TM) image version
## ref: https://hub.docker.com/r/bitnami/redis/tags/
##
image:
registry: docker.io
repository: bitnami/redis
## Bitnami Redis image tag
## Bitnami Redis(TM) image tag
## ref: https://github.com/bitnami/bitnami-docker-redis#supported-tags-and-respective-dockerfile-links
##
tag: 6.0.9-debian-10-r66
@@ -51,13 +51,13 @@ sentinel:
## Require password authentication on the sentinel itself
## ref: https://redis.io/topics/sentinel
usePassword: true
## Bitnami Redis Sentintel image version
## Bitnami Redis(TM) Sentintel image version
## ref: https://hub.docker.com/r/bitnami/redis-sentinel/tags/
##
image:
registry: docker.io
repository: bitnami/redis-sentinel
## Bitnami Redis image tag
## Bitnami Redis(TM) image tag
## ref: https://github.com/bitnami/bitnami-docker-redis-sentinel#supported-tags-and-respective-dockerfile-links
##
tag: 6.0.9-debian-10-r66
@@ -79,7 +79,7 @@ sentinel:
failoverTimeout: 18000
parallelSyncs: 1
port: 26379
## Additional Redis configuration for the sentinel nodes
## Additional Redis(TM) configuration for the sentinel nodes
## ref: https://redis.io/topics/config
##
configmap:
@@ -88,7 +88,7 @@ sentinel:
## If enabled, each replicas will have a constant ID on each start-up
##
staticID: false
## Configure extra options for Redis Sentinel liveness and readiness probes
## Configure extra options for Redis(TM) Sentinel liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
##
livenessProbe:
@@ -107,15 +107,15 @@ sentinel:
failureThreshold: 5
customLivenessProbe: {}
customReadinessProbe: {}
## Redis Sentinel resource requests and limits
## Redis(TM) Sentinel resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
# resources:
# requests:
# memory: 256Mi
# cpu: 100m
## Redis Sentinel Service properties
## Redis(TM) Sentinel Service properties
service:
## Redis Sentinel Service type
## Redis(TM) Sentinel Service type
type: ClusterIP
sentinelPort: 26379
redisPort: 6379
@@ -137,9 +137,11 @@ sentinel:
annotations: {}
labels: {}
loadBalancerIP:
## Additional commands to run prior to starting Redis node with sentinel
## Additional commands to run prior to starting Redis(TM) node with sentinel
##
preExecCmds: ""
## An array to add extra env var to the sentinel node configurations
## For example:
## extraEnvVars:
@@ -170,8 +172,8 @@ networkPolicy:
enabled: false
## The Policy model to apply. When set to false, only pods with the correct
## client label will have network access to the port Redis is listening
## on. When true, Redis will accept connections from any source
## client label will have network access to the port Redis(TM) is listening
## on. When true, Redis(TM) will accept connections from any source
## (with the correct destination port).
##
# allowExternal: true
@@ -211,7 +213,7 @@ rbac:
# - gce.unprivileged
rules: []
## Redis pod Security Context
## Redis(TM) pod Security Context
securityContext:
enabled: true
fsGroup: 1001
@@ -232,14 +234,14 @@ containerSecurityContext:
## Use password authentication
usePassword: true
## Redis password (both master and slave)
## Redis(TM) password (both master and slave)
## Defaults to a random 10-character alphanumeric string if not set and usePassword is true
## ref: https://github.com/bitnami/bitnami-docker-redis#setting-the-server-password-on-first-run
##
password: ""
## Use existing secret (ignores previous password)
# existingSecret:
## Password key to be retrieved from Redis secret
## Password key to be retrieved from Redis(TM) secret
##
# existingSecretPasswordKey:
@@ -253,7 +255,7 @@ persistence:
## If defined, PVC must be created manually before volume will be bound
existingClaim:
# Redis port
# Redis(TM) port
redisPort: 6379
##
@@ -282,32 +284,32 @@ tls:
# dhParamsFilename:
##
## Redis Master parameters
## Redis(TM) Master parameters
##
master:
## Redis command arguments
## Redis(TM) command arguments
##
## Can be used to specify command line arguments, for example:
## Note `exec` is prepended to command
##
command: "/run.sh"
## Additional commands to run prior to starting Redis
## Additional commands to run prior to starting Redis(TM)
##
preExecCmds: ""
## Additional Redis configuration for the master nodes
## Additional Redis(TM) configuration for the master nodes
## ref: https://redis.io/topics/config
##
configmap:
## Redis additional command line flags
## Redis(TM) additional command line flags
##
## Can be used to specify command line flags, for example:
## extraFlags:
## - "--maxmemory-policy volatile-ttl"
## - "--repl-backlog-size 1024mb"
extraFlags: []
## Comma-separated list of Redis commands to disable
## Comma-separated list of Redis(TM) commands to disable
##
## Can be used to disable Redis commands for security reasons.
## Can be used to disable Redis(TM) commands for security reasons.
## Commands will be completely disabled by renaming each to an empty string.
## ref: https://redis.io/topics/security#disabling-of-specific-commands
##
@@ -315,12 +317,12 @@ master:
- FLUSHDB
- FLUSHALL
## Redis Master additional pod labels and annotations
## Redis(TM) Master additional pod labels and annotations
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
podLabels: {}
podAnnotations: {}
## Redis Master resource requests and limits
## Redis(TM) Master resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
# resources:
# requests:
@@ -338,7 +340,7 @@ master:
# Enable this only if customLivenessProbe or customReadinessProbe is used and zombie PIDs are accumulating.
# Ref: https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/
shareProcessNamespace: false
## Configure extra options for Redis Master liveness and readiness probes
## Configure extra options for Redis(TM) Master liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
##
livenessProbe:
@@ -378,19 +380,19 @@ master:
customLivenessProbe: {}
customReadinessProbe: {}
## Redis Master Node selectors and tolerations for pod assignment
## Redis(TM) Master Node selectors and tolerations for pod assignment
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#taints-and-tolerations-beta-feature
##
# nodeSelector: {"beta.kubernetes.io/arch": "amd64"}
# tolerations: []
## Redis Master pod/node affinity/anti-affinity
## Redis(TM) Master pod/node affinity/anti-affinity
##
affinity: {}
## Redis Master Service properties
## Redis(TM) Master Service properties
service:
## Redis Master Service type
## Redis(TM) Master Service type
type: ClusterIP
port: 6379
@@ -418,7 +420,7 @@ master:
persistence:
enabled: true
## The path the volume will be mounted at, useful when using different
## Redis images.
## Redis(TM) images.
path: /data
## The subdirectory of the volume to mount to, useful in dev environments
## and one PV for multiple services.
@@ -452,7 +454,7 @@ master:
## https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#partitions
# rollingUpdatePartition:
## Redis Master pod priorityClassName
## Redis(TM) Master pod priorityClassName
##
priorityClassName: ''
@@ -477,16 +479,16 @@ master:
extraEnvVarsSecret: []
##
## Redis Slave properties
## Redis(TM) Slave properties
## Note: service.type is a mandatory parameter
## The rest of the parameters are either optional or, if undefined, will inherit those declared in Redis Master
## The rest of the parameters are either optional or, if undefined, will inherit those declared in Redis(TM) Master
##
slave:
## Slave Service properties
service:
## Redis Slave Service type
## Redis(TM) Slave Service type
type: ClusterIP
## Redis port
## Redis(TM) port
port: 6379
## External traffic policy (when service type is LoadBalancer)
@@ -507,27 +509,27 @@ slave:
loadBalancerIP:
# loadBalancerSourceRanges: ["10.0.0.0/8"]
## Redis slave port
## Redis(TM) slave port
port: 6379
## Can be used to specify command line arguments, for example:
## Note `exec` is prepended to command
##
command: "/run.sh"
## Additional commands to run prior to starting Redis
## Additional commands to run prior to starting Redis(TM)
##
preExecCmds: ""
## Additional Redis configuration for the slave nodes
## Additional Redis(TM) configuration for the slave nodes
## ref: https://redis.io/topics/config
##
configmap:
## Redis extra flags
## Redis(TM) extra flags
extraFlags: []
## List of Redis commands to disable
## List of Redis(TM) commands to disable
disableCommands:
- FLUSHDB
- FLUSHALL
## Redis Slave pod/node affinity/anti-affinity
## Redis(TM) Slave pod/node affinity/anti-affinity
##
affinity: {}
@@ -546,7 +548,7 @@ slave:
# Enable this only if customLivenessProbe or customReadinessProbe is used and zombie PIDs are accumulating.
# Ref: https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/
shareProcessNamespace: false
## Configure extra options for Redis Slave liveness and readiness probes
## Configure extra options for Redis(TM) Slave liveness and readiness probes
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes)
##
livenessProbe:
@@ -586,13 +588,13 @@ slave:
customLivenessProbe: {}
customReadinessProbe: {}
## Redis slave Resource
## Redis(TM) slave Resource
# resources:
# requests:
# memory: 256Mi
# cpu: 100m
## Redis slave selectors and tolerations for pod assignment
## Redis(TM) slave selectors and tolerations for pod assignment
# nodeSelector: {"beta.kubernetes.io/arch": "amd64"}
# tolerations: []
@@ -601,11 +603,11 @@ slave:
##
# schedulerName:
## Redis slave pod Annotation and Labels
## Redis(TM) slave pod Annotation and Labels
podLabels: {}
podAnnotations: {}
## Redis slave pod priorityClassName
## Redis(TM) slave pod priorityClassName
# priorityClassName: ''
## Enable persistence using Persistent Volume Claims
@@ -614,7 +616,7 @@ slave:
persistence:
enabled: true
## The path the volume will be mounted at, useful when using different
## Redis images.
## Redis(TM) images.
path: /data
## The subdirectory of the volume to mount to, useful in dev environments
## and one PV for multiple services.
@@ -736,7 +738,7 @@ metrics:
enabled: false
additionalLabels: {}
namespace: ""
## Redis prometheus rules
## Redis(TM) prometheus rules
## These are just examples rules, please adapt them to your needs.
## Make sure to constraint the rules to the current redis service.
# rules:
@@ -746,8 +748,8 @@ metrics:
# labels:
# severity: error
# annotations:
# summary: Redis instance {{ "{{ $labels.instance }}" }} down
# description: Redis instance {{ "{{ $labels.instance }}" }} is down
# summary: Redis(TM) instance {{ "{{ $labels.instance }}" }} down
# description: Redis(TM) instance {{ "{{ $labels.instance }}" }} is down
# - alert: RedisMemoryHigh
# expr: >
# redis_memory_used_bytes{service="{{ template "redis.fullname" . }}-metrics"} * 100
@@ -758,9 +760,9 @@ metrics:
# labels:
# severity: error
# annotations:
# summary: Redis instance {{ "{{ $labels.instance }}" }} is using too much memory
# summary: Redis(TM) instance {{ "{{ $labels.instance }}" }} is using too much memory
# description: |
# Redis instance {{ "{{ $labels.instance }}" }} is using {{ "{{ $value }}" }}% of its available memory.
# Redis(TM) instance {{ "{{ $labels.instance }}" }} is using {{ "{{ $value }}" }}% of its available memory.
# - alert: RedisKeyEviction
# expr: |
# increase(redis_evicted_keys_total{service="{{ template "redis.fullname" . }}-metrics"}[5m]) > 0
@@ -768,9 +770,9 @@ metrics:
# labels:
# severity: error
# annotations:
# summary: Redis instance {{ "{{ $labels.instance }}" }} has evicted keys
# summary: Redis(TM) instance {{ "{{ $labels.instance }}" }} has evicted keys
# description: |
# Redis instance {{ "{{ $labels.instance }}" }} has evicted {{ "{{ $value }}" }} keys in the last 5 minutes.
# Redis(TM) instance {{ "{{ $labels.instance }}" }} has evicted {{ "{{ $value }}" }} keys in the last 5 minutes.
rules: []
## Metrics exporter pod priorityClassName
@@ -823,7 +825,7 @@ volumePermissions:
securityContext:
runAsUser: 0
## Redis config file
## Redis(TM) config file
## ref: https://redis.io/topics/config
##
configmap: |-

2
bitnami/zookeeper/Chart.yaml
View File

@@ -21,4 +21,4 @@ name: zookeeper
sources:
- https://github.com/bitnami/bitnami-docker-zookeeper
- https://zookeeper.apache.org/
version: 6.3.0
version: 6.3.1

2
bitnami/zookeeper/values-production.yaml
View File

@@ -401,7 +401,7 @@ networkPolicy:
enabled: true
## The Policy model to apply. When set to false, only pods with the correct
## client label will have network access to the port Redis is listening
## client label will have network access to the port Redis(TM) is listening
## on. When true, zookeeper accept connections from any source
## (with the correct destination port).
##

2
bitnami/zookeeper/values.yaml
View File

@@ -401,7 +401,7 @@ networkPolicy:
enabled: false
## The Policy model to apply. When set to false, only pods with the correct
## client label will have network access to the port Redis is listening
## client label will have network access to the port Redis(TM) is listening
## on. When true, zookeeper accept connections from any source
## (with the correct destination port).
##