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

Synchronize upstreamed folder to b611fe5fa

Browse Source
This commit is contained in:
bitnami-bot
2020-02-11 18:35:07 +00:00
parent 1d9b157535
commit 9858616819
30 changed files with 83 additions and 83 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
upstreamed/drupal/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: drupal
version: 6.2.4
version: 6.2.5
appVersion: 8.8.2
description: One of the most versatile open source content management systems.
keywords:

12
upstreamed/drupal/README.md
View File

@@ -5,7 +5,7 @@
## TL;DR;
```console
$ helm install stable/drupal
$ helm install my-release stable/drupal
```
## Introduction
@@ -28,7 +28,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm install --name my-release stable/drupal
$ helm install my-release stable/drupal
```
The command deploys Drupal on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -116,7 +116,7 @@ The above parameters map to the env variables defined in [bitnami/drupal](http:/
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
$ helm install --name my-release \
$ helm install my-release \
--set drupalUsername=admin,drupalPassword=password,mariadb.mariadbRootPassword=secretpassword \
stable/drupal
```
@@ -126,7 +126,7 @@ The above command sets the Drupal administrator account username and password to
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
$ helm install --name my-release -f values.yaml stable/drupal
$ helm install my-release -f values.yaml stable/drupal
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -171,7 +171,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
1. Install the chart
```bash
$ helm install --name my-release --set persistence.drupal.existingClaim=PVC_NAME stable/drupal
$ helm install my-release --set persistence.drupal.existingClaim=PVC_NAME stable/drupal
```
### Host path
@@ -187,7 +187,7 @@ $ helm install --name my-release --set persistence.drupal.existingClaim=PVC_NAME
1. Install the chart
```bash
$ helm install --name my-release --set persistence.drupal.hostPath=/PATH/TO/HOST/MOUNT stable/drupal
$ helm install my-release --set persistence.drupal.hostPath=/PATH/TO/HOST/MOUNT stable/drupal
```
This will mount the `drupal-data` volume into the `hostPath` directory. The site data will be persisted if the mount path contains valid data, else the site data will be initialized at first launch.

2
upstreamed/ghost/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: ghost
version: 9.1.6
version: 9.1.7
appVersion: 3.5.0
description: A simple, powerful publishing platform that allows you to share your stories with the world
keywords:

8
upstreamed/ghost/README.md
View File

@@ -5,7 +5,7 @@
## TL;DR;
```console
$ helm install stable/ghost
$ helm install my-release stable/ghost
```
## Introduction
@@ -28,7 +28,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm install --name my-release stable/ghost
$ helm install my-release stable/ghost
```
The command deploys Ghost on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -150,7 +150,7 @@ The above parameters map to the env variables defined in [bitnami/ghost](http://
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
$ helm install --name my-release \
$ helm install my-release \
--set ghostUsername=admin,ghostPassword=password,mariadb.mariadbRootPassword=secretpassword \
stable/ghost
```
@@ -160,7 +160,7 @@ The above command sets the Ghost administrator account username and password to
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
$ helm install --name my-release -f values.yaml stable/ghost
$ helm install my-release -f values.yaml stable/ghost
```
> **Tip**: You can use the default [values.yaml](values.yaml)

2
upstreamed/jasperreports/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: jasperreports
version: 7.0.4
version: 7.0.5
appVersion: 7.2.0
description: The JasperReports server can be used as a stand-alone or embedded reporting
and BI server that offers web-based reporting, analytic tools and visualization,

8
upstreamed/jasperreports/README.md
View File

@@ -5,7 +5,7 @@
## TL;DR;
```console
$ helm install stable/jasperreports
$ helm install my-release stable/jasperreports
```
## Introduction
@@ -28,7 +28,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm install --name my-release stable/jasperreports
$ helm install my-release stable/jasperreports
```
The command deploys JasperReports on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -108,7 +108,7 @@ The above parameters map to the env variables defined in [bitnami/jasperreports]
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
$ helm install --name my-release \
$ helm install my-release \
--set jasperreportsUsername=admin,jasperreportsPassword=password,mariadb.mariadbRootPassword=secretpassword \
stable/jasperreports
```
@@ -118,7 +118,7 @@ The above command sets the JasperReports administrator account username and pass
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
$ helm install --name my-release -f values.yaml stable/jasperreports
$ helm install my-release -f values.yaml stable/jasperreports
```
> **Tip**: You can use the default [values.yaml](values.yaml)

2
upstreamed/joomla/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: joomla
version: 7.1.5
version: 7.1.6
appVersion: 3.9.15
description: PHP content management system (CMS) for publishing web content
keywords:

8
upstreamed/joomla/README.md
View File

@@ -5,7 +5,7 @@
## TL;DR;
```console
$ helm install stable/joomla
$ helm install my-release stable/joomla
```
## Introduction
@@ -28,7 +28,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm install --name my-release stable/joomla
$ helm install my-release stable/joomla
```
The command deploys Joomla! on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -138,7 +138,7 @@ The above parameters map to the env variables defined in [bitnami/joomla](http:/
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
$ helm install --name my-release \
$ helm install my-release \
--set joomlaUsername=admin,joomlaPassword=password,mariadb.mariadbRootPassword=secretpassword \
stable/joomla
```
@@ -148,7 +148,7 @@ The above command sets the Joomla! administrator account username and password t
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
$ helm install --name my-release -f values.yaml stable/joomla
$ helm install my-release -f values.yaml stable/joomla
```
> **Tip**: You can use the default [values.yaml](values.yaml)

2
upstreamed/kubewatch/Chart.yaml
View File

@@ -1,5 +1,5 @@
name: kubewatch
version: 1.0.4
version: 1.0.5
apiVersion: v1
appVersion: 0.0.4
home: https://github.com/bitnami-labs/kubewatch

8
upstreamed/kubewatch/README.md
View File

@@ -6,7 +6,7 @@
## TL;DR;
```console
$ helm install stable/kubewatch
$ helm install my-release stable/kubewatch
```
## Introduction
@@ -23,7 +23,7 @@ This chart bootstraps a kubewatch deployment on a [Kubernetes](http://kubernetes
To install the chart with the release name `my-release`:
```console
$ helm install stable/kubewatch --name my-release
$ helm install my-release stable/kubewatch
```
The command deploys kubewatch on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -91,14 +91,14 @@ The following table lists the configurable parameters of the kubewatch chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
$ helm install stable/kubewatch --name my-release \
$ helm install my-release stable/kubewatch \
--set=slack.channel="#bots",slack.token="XXXX-XXXX-XXXX"
```
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
$ helm install stable/kubewatch --name my-release -f values.yaml
$ helm install my-release -f values.yaml stable/kubewatch
```
> **Tip**: You can use the default [values.yaml](values.yaml)

2
upstreamed/mariadb/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: mariadb
version: 7.3.8
version: 7.3.9
appVersion: 10.3.22
description: Fast, reliable, scalable, and easy to use open-source relational database system. MariaDB Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software. Highly available MariaDB cluster.
keywords:

8
upstreamed/mariadb/README.md
View File

@@ -7,7 +7,7 @@ MariaDB is developed as open source software and as a relational database it pro
## TL;DR;
```bash
$ helm install stable/mariadb
$ helm install my-release stable/mariadb
```
## Introduction
@@ -27,7 +27,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
To install the chart with the release name `my-release`:
```bash
$ helm install --name my-release stable/mariadb
$ helm install my-release stable/mariadb
```
The command deploys MariaDB on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -200,7 +200,7 @@ The above parameters map to the env variables defined in [bitnami/mariadb](http:
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
$ helm install --name my-release \
$ helm install my-release \
--set rootUser.password=secretpassword,db.user=app_database \
stable/mariadb
```
@@ -210,7 +210,7 @@ The above command sets the MariaDB `root` account password to `secretpassword`.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
$ helm install --name my-release -f values.yaml stable/mariadb
$ helm install my-release -f values.yaml stable/mariadb
```
> **Tip**: You can use the default [values.yaml](values.yaml)

2
upstreamed/mediawiki/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: mediawiki
version: 9.1.3
version: 9.1.4
appVersion: 1.34.0
description: Extremely powerful, scalable software and a feature-rich wiki implementation that uses PHP to process and display data stored in a database.
home: http://www.mediawiki.org/

8
upstreamed/mediawiki/README.md
View File

@@ -5,7 +5,7 @@
## TL;DR;
```console
$ helm install stable/mediawiki
$ helm install my-release stable/mediawiki
```
## Introduction
@@ -28,7 +28,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm install --name my-release stable/mediawiki
$ helm install my-release stable/mediawiki
```
The command deploys MediaWiki on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -136,7 +136,7 @@ The above parameters map to the env variables defined in [bitnami/mediawiki](htt
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
$ helm install --name my-release \
$ helm install my-release \
--set mediawikiUser=admin,mediawikiPassword=password,mariadb.mariadbRootPassword=secretpassword \
stable/mediawiki
```
@@ -146,7 +146,7 @@ The above command sets the MediaWiki administrator account username and password
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
$ helm install --name my-release -f values.yaml stable/mediawiki
$ helm install my-release -f values.yaml stable/mediawiki
```
> **Tip**: You can use the default [values.yaml](values.yaml)

2
upstreamed/nats/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: nats
version: 4.3.0
version: 4.3.1
appVersion: 2.1.4
description: An open-source, cloud-native messaging system
keywords:

10
upstreamed/nats/README.md
View File

@@ -5,7 +5,7 @@
## TL;DR;
```bash
$ helm install stable/nats
$ helm install my-release stable/nats
```
## Introduction
@@ -24,7 +24,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
To install the chart with the release name `my-release`:
```bash
$ helm install --name my-release stable/nats
$ helm install my-release stable/nats
```
The command deploys NATS on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -139,7 +139,7 @@ The following table lists the configurable parameters of the NATS chart and thei
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
$ helm install --name my-release \
$ helm install my-release \
--set auth.enabled=true,auth.user=my-user,auth.password=T0pS3cr3t \
stable/nats
```
@@ -149,7 +149,7 @@ The above command enables NATS client authentication with `my-user` as user and
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
$ helm install --name my-release -f values.yaml stable/nats
$ helm install my-release -f values.yaml stable/nats
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -232,7 +232,7 @@ NATS version 2.0.0 has renamed the server binary filename from `gnatsd` to `nats
however, it is still possible to use the chart to deploy NATS version 1.x.x using the `natsFilename` property.
```bash
helm install --name nats-v1 --set natsFilename=gnatsd --set image.tag=1.4.1 stable/nats
helm install nats-v1 --set natsFilename=gnatsd --set image.tag=1.4.1 stable/nats
```
### To 1.0.0

2
upstreamed/phpmyadmin/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: phpmyadmin
version: 4.2.11
version: 4.2.12
appVersion: 5.0.1
description: phpMyAdmin is an mysql administration frontend
keywords:

8
upstreamed/phpmyadmin/README.md
View File

@@ -5,7 +5,7 @@
## TL;DR;
```console
$ helm install stable/phpmyadmin
$ helm install my-release stable/phpmyadmin
```
## Introduction
@@ -23,7 +23,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm install --name my-release stable/phpmyadmin
$ helm install my-release stable/phpmyadmin
```
The command deploys phpMyAdmin on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -95,7 +95,7 @@ For more information please refer to the [bitnami/phpmyadmin](http://github.com/
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
$ helm install --name my-release \
$ helm install my-release \
--set db.host=mymariadb,db.port=3306 stable/phpmyadmin
```
@@ -104,7 +104,7 @@ The above command sets the phpMyAdmin to connect to a database in `mymariadb` ho
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
$ helm install --name my-release -f values.yaml stable/phpmyadmin
$ helm install my-release -f values.yaml stable/phpmyadmin
```
> **Tip**: You can use the default [values.yaml](values.yaml)

2
upstreamed/postgresql/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: postgresql
version: 8.3.2
version: 8.3.3
appVersion: 11.6.0
description: Chart for PostgreSQL, an object-relational database management system (ORDBMS) with an emphasis on extensibility and on standards-compliance.
keywords:

12
upstreamed/postgresql/README.md
View File

@@ -7,7 +7,7 @@ For HA, please see [this repo](https://github.com/bitnami/charts/tree/master/bit
## TL;DR;
```console
$ helm install stable/postgresql
$ helm install my-release stable/postgresql
```
## Introduction
@@ -26,7 +26,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm install --name my-release stable/postgresql
$ helm install my-release stable/postgresql
```
The command deploys PostgreSQL on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -212,7 +212,7 @@ The following tables lists the configurable parameters of the PostgreSQL chart a
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
$ helm install --name my-release \
$ helm install my-release \
--set postgresqlPassword=secretpassword,postgresqlDatabase=my-database \
stable/postgresql
```
@@ -222,7 +222,7 @@ The above command sets the PostgreSQL `postgres` account password to `secretpass
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```console
$ helm install --name my-release -f values.yaml stable/postgresql
$ helm install my-release -f values.yaml stable/postgresql
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -387,7 +387,7 @@ From chart version 4.0.0, it is possible to use this chart with the Docker Offic
Besides specifying the new Docker repository and tag, it is important to modify the PostgreSQL data directory and volume mount point. Basically, the PostgreSQL data dir cannot be the mount point directly, it has to be a subdirectory.
```
helm install --name postgres \
helm install postgres \
--set image.repository=postgres \
--set image.tag=10.6 \
--set postgresqlDataDir=/data/pgdata \
@@ -500,7 +500,7 @@ $ kubectl get svc
```console
$ helm repo update
$ helm install --name my-release stable/postgresql
$ helm install my-release stable/postgresql
```
- Connect to the new pod (you can obtain the name by running `kubectl get pods`):

2
upstreamed/rabbitmq/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: rabbitmq
version: 6.17.1
version: 6.17.2
appVersion: 3.8.2
description: Open source message broker software that implements the Advanced Message Queuing Protocol (AMQP)
keywords:

10
upstreamed/rabbitmq/README.md
View File

@@ -5,7 +5,7 @@
## TL;DR;
```bash
$ helm install stable/rabbitmq
$ helm install my-release stable/rabbitmq
```
## Introduction
@@ -25,7 +25,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
To install the chart with the release name `my-release`:
```bash
$ helm install --name my-release stable/rabbitmq
$ helm install my-release stable/rabbitmq
```
The command deploys RabbitMQ on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -189,7 +189,7 @@ The above parameters map to the env variables defined in [bitnami/rabbitmq](http
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
$ helm install --name my-release \
$ helm install my-release \
--set rabbitmq.username=admin,rabbitmq.password=secretpassword,rabbitmq.erlangCookie=secretcookie \
stable/rabbitmq
```
@@ -199,7 +199,7 @@ The above command sets the RabbitMQ admin username and password to `admin` and `
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
$ helm install --name my-release -f values.yaml stable/rabbitmq
$ helm install my-release -f values.yaml stable/rabbitmq
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -385,7 +385,7 @@ The chart mounts a [Persistent Volume](http://kubernetes.io/docs/user-guide/pers
1. Install the chart
```bash
$ helm install --set persistence.existingClaim=PVC_NAME rabbitmq
$ helm install my-release --set persistence.existingClaim=PVC_NAME stable/rabbitmq
```
### Adjust permissions of the persistence volume mountpoint

2
upstreamed/rabbitmq/templates/_helpers.tpl
View File

@@ -235,7 +235,7 @@ rabbitmq: LDAP
Invalid LDAP configuration. When enabling LDAP support, the parameters "ldap.server",
"ldap.port", and "ldap. user_dn_pattern" are mandatory. Please provide them:
$ helm install --name {{ .Release.Name }} stable/rabbitmq \
$ helm install {{ .Release.Name }} stable/rabbitmq \
--set ldap.enabled=true \
--set ldap.server="lmy-ldap-server" \
--set ldap.port="389" \

2
upstreamed/redis/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: redis
version: 10.4.3
version: 10.4.4
appVersion: 5.0.7
description: Open source, advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets.
keywords:

16
upstreamed/redis/README.md
View File

@@ -7,12 +7,12 @@
```bash
# Testing configuration
$ helm install stable/redis
$ helm install my-release stable/redis
```
```bash
# Production configuration
$ helm install stable/redis --values values-production.yaml
$ helm install my-release stable/redis --values values-production.yaml
```
## Introduction
@@ -32,7 +32,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
To install the chart with the release name `my-release`:
```bash
$ helm install --name my-release stable/redis
$ helm install my-release stable/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.
@@ -246,7 +246,7 @@ The following table lists the configurable parameters of the Redis chart and the
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
$ helm install --name my-release \
$ helm install my-release \
--set password=secretpassword \
stable/redis
```
@@ -256,7 +256,7 @@ The above command sets the Redis server password to `secretpassword`.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
$ helm install --name my-release -f values.yaml stable/redis
$ helm install my-release -f values.yaml stable/redis
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -376,7 +376,7 @@ By default, the chart mounts a [Persistent Volume](http://kubernetes.io/docs/use
3. Install the chart
```bash
$ helm install --set persistence.existingClaim=PVC_NAME stable/redis
$ helm install my-release --set persistence.existingClaim=PVC_NAME stable/redis
```
## NetworkPolicy
@@ -429,14 +429,14 @@ This version causes a change in the Redis Master StatefulSet definition, so the
- 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.
```
helm install stable/redis --set persistence.existingClaim=<NEW PVC>
helm install my-release stable/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
```
helm delete --purge <RELEASE>
helm install stable/redis --name <RELEASE>
helm install <RELEASE> stable/redis
```
Previous versions of the chart were not using persistence in the slaves, so this upgrade would add it to them. Another important change is that no values are inherited from master to slaves. For example, in 6.0.0 `slaves.readinessProbe.periodSeconds`, if empty, would be set to `master.readinessProbe.periodSeconds`. This approach lacked transparency and was difficult to maintain. From now on, all the slave parameters must be configured just as it is done with the masters.

2
upstreamed/testlink/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: testlink
version: 7.1.0
version: 7.1.1
appVersion: 1.9.19
description: Web-based test management system that facilitates software quality assurance.
icon: https://bitnami.com/assets/stacks/testlink/img/testlink-stack-220x234.png

8
upstreamed/testlink/README.md
View File

@@ -5,7 +5,7 @@
## TL;DR;
```console
$ helm install stable/testlink
$ helm install my-release stable/testlink
```
## Introduction
@@ -28,7 +28,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm install --name my-release stable/testlink
$ helm install my-release stable/testlink
```
The command deploys TestLink on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -121,7 +121,7 @@ The above parameters map to the env variables defined in [bitnami/testlink](http
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
$ helm install --name my-release \
$ helm install my-release \
--set testlinkUsername=admin,testlinkPassword=password,mariadb.mariadbRootPassword=secretpassword \
stable/testlink
```
@@ -131,7 +131,7 @@ The above command sets the TestLink administrator account username and password
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
$ helm install --name my-release -f values.yaml stable/testlink
$ helm install my-release -f values.yaml stable/testlink
```
> **Tip**: You can use the default [values.yaml](values.yaml)

2
upstreamed/wordpress/Chart.yaml
View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: wordpress
version: 8.1.2
version: 8.1.3
appVersion: 5.3.2
description: Web publishing platform for building blogs and websites.
icon: https://bitnami.com/assets/stacks/wordpress/img/wordpress-stack-220x234.png

10
upstreamed/wordpress/README.md
View File

@@ -5,7 +5,7 @@
## TL;DR;
```console
$ helm install stable/wordpress
$ helm install my-release stable/wordpress
```
## Introduction
@@ -28,7 +28,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm install --name my-release stable/wordpress
$ helm install my-release stable/wordpress
```
The command deploys WordPress on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -164,7 +164,7 @@ The above parameters map to the env variables defined in [bitnami/wordpress](htt
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
$ helm install --name my-release \
$ helm install my-release \
--set wordpressUsername=admin,wordpressPassword=password,mariadb.mariadbRootPassword=secretpassword \
stable/wordpress
```
@@ -174,7 +174,7 @@ The above command sets the WordPress administrator account username and password
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
$ helm install --name my-release -f values.yaml stable/wordpress
$ helm install my-release -f values.yaml stable/wordpress
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -216,7 +216,7 @@ This chart includes a `values-production.yaml` file where you can find some para
+ ## To use the /admin portal and to ensure you can scale wordpress you need to provide a
+ ## ReadWriteMany PVC, if you dont have a provisioner for this type of storage
+ ## We recommend that you install the nfs provisioner and map it to a RWO volume
+ ## helm install stable/nfs-server-provisioner --set persistence.enabled=true,persistence.size=10Gi
+ ## helm install nfs-server stable/nfs-server-provisioner --set persistence.enabled=true,persistence.size=10Gi
+ persistence.accessMode: ReadWriteMany
```

2
upstreamed/wordpress/values-production.yaml
View File

@@ -344,7 +344,7 @@ persistence:
## To use the /admin portal and to ensure you can scale wordpress you need to provide a
## ReadWriteMany PVC, if you dont have a provisioner for this type of storage
## We recommend that you install the nfs provisioner and map it to a RWO volume
## helm install stable/nfs-server-provisioner --set persistence.enabled=true,persistence.size=10Gi
## helm install nfs-server stable/nfs-server-provisioner --set persistence.enabled=true,persistence.size=10Gi
accessMode: ReadWriteMany
size: 10Gi