mirror of
https://github.com/bitnami/charts.git
synced 2026-03-15 14:57:16 +08:00
Update Redis trademark references
* Update Redis reference and usage Signed-off-by: michield <michield@vmware.com> * Update Redis reference and usage Summary: Change Redis solution names Reviewers: jotamartos Differential Revision: https://phabricator.nami.run/D63488 Signed-off-by: michield <michield@vmware.com> * Corrections Signed-off-by: michield <michield@vmware.com> * Bump versions Signed-off-by: michield <michield@vmware.com> * Bump all affected Charts versions Signed-off-by: michield <michield@vmware.com> * Rebase Airflow version Signed-off-by: michield <michield@vmware.com> * Bump remaining affected Charts versions Signed-off-by: michield <michield@vmware.com> * Bump remaining affected Charts versions Signed-off-by: michield <michield@vmware.com> * Correction Signed-off-by: michield <michield@vmware.com> * Bump remaining affected Charts versions Signed-off-by: michield <michield@vmware.com> * Rebasing Chart versions Signed-off-by: michield <michield@vmware.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers <containers@bitnami.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers <containers@bitnami.com> * Bump airflow version Signed-off-by: michield <michield@vmware.com> * Bump all versions Signed-off-by: michield <michield@vmware.com> Co-authored-by: michield <michield@vmware.com> Co-authored-by: Bitnami Containers <containers@bitnami.com>
This commit is contained in:
@@ -19,7 +19,7 @@ $ helm install my-release bitnami/discourse
|
||||
|
||||
This chart bootstraps a [Discourse](https://www.discourse.org/) deployment on a [Kubernetes](https://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®](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.
|
||||
|
||||
@@ -316,19 +316,19 @@ The command removes all the Kubernetes components associated with the chart and
|
||||
| `externalDatabase.existingSecretPostgresPasswordKey` | Name of an existing secret key containing the database admin user credentials | `postgres-password` |
|
||||
|
||||
|
||||
### Redis™ parameters
|
||||
### Redis® parameters
|
||||
|
||||
| Name | Description | Value |
|
||||
| ----------------------------------------- | -------------------------------------------------------------------------- | ---------------- |
|
||||
| `redis.enabled` | Switch to enable or disable the Redis™ helm | `true` |
|
||||
| `redis.enabled` | Switch to enable or disable the Redis® helm | `true` |
|
||||
| `redis.auth.enabled` | Enable password authentication | `true` |
|
||||
| `redis.auth.password` | Redis™ password | `""` |
|
||||
| `redis.auth.existingSecret` | The name of an existing secret with Redis™ credentials | `""` |
|
||||
| `redis.architecture` | Redis™ architecture. Allowed values: `standalone` or `replication` | `standalone` |
|
||||
| `externalRedis.host` | Redis™ host | `localhost` |
|
||||
| `externalRedis.port` | Redis™ port number | `6379` |
|
||||
| `externalRedis.username` | Redis™ username | `""` |
|
||||
| `externalRedis.password` | Redis™ password | `""` |
|
||||
| `redis.auth.password` | Redis® password | `""` |
|
||||
| `redis.auth.existingSecret` | The name of an existing secret with Redis® credentials | `""` |
|
||||
| `redis.architecture` | Redis® architecture. Allowed values: `standalone` or `replication` | `standalone` |
|
||||
| `externalRedis.host` | Redis® host | `localhost` |
|
||||
| `externalRedis.port` | Redis® port number | `6379` |
|
||||
| `externalRedis.username` | Redis® username | `""` |
|
||||
| `externalRedis.password` | Redis® password | `""` |
|
||||
| `externalRedis.existingSecret` | Name of an existing secret resource containing the Redis&trade credentials | `""` |
|
||||
| `externalRedis.existingSecretPasswordKey` | Name of an existing secret key containing the Redis&trade credentials | `redis-password` |
|
||||
|
||||
@@ -445,7 +445,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® 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:
|
||||
|
||||
```console
|
||||
redis.enabled=false
|
||||
|
||||
Reference in New Issue
Block a user