[bitnami/*] Update URLs to point to the new bitnami/containers monorepo (#11352)

* [bitnami/several] Update URLs to point to the new bitnami/containers monorepo

Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>

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

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

* Update bitnami/mongodb/values.yaml

Co-authored-by: Jose Antonio Carmona <jcarmona@vmware.com>

* Update bitnami/mongodb/values.yaml

Co-authored-by: Jose Antonio Carmona <jcarmona@vmware.com>

* Update bitnami/mongodb/values.yaml

Co-authored-by: Jose Antonio Carmona <jcarmona@vmware.com>

* Update bitnami/mongodb/values.yaml

Co-authored-by: Jose Antonio Carmona <jcarmona@vmware.com>

* Update bitnami/mongodb-sharded/values.yaml

Co-authored-by: Jose Antonio Carmona <jcarmona@vmware.com>

* Update bitnami/mongodb-sharded/values.yaml

Co-authored-by: Jose Antonio Carmona <jcarmona@vmware.com>

* Update bitnami/mongodb-sharded/values.yaml

Co-authored-by: Jose Antonio Carmona <jcarmona@vmware.com>

Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>
Co-authored-by: Jose Antonio Carmona <jcarmona@vmware.com>
This commit is contained in:
Carlos Rodríguez Hernández
2022-07-26 18:43:55 +02:00
committed by GitHub
parent de983f6906
commit d665af0c70
239 changed files with 889 additions and 879 deletions

View File

@@ -7,7 +7,7 @@ Redmine is an open source management application. It includes a tracking issue s
[Overview of Redmine](http://www.redmine.org/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```bash
@@ -17,7 +17,7 @@ $ helm install my-release bitnami/redmine
## Introduction
This chart bootstraps a [Redmine](https://github.com/bitnami/bitnami-docker-redmine) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
This chart bootstraps a [Redmine](https://github.com/bitnami/containers/tree/main/bitnami/redmine) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
It also packages the [Bitnami MariaDB chart](https://github.com/bitnami/charts/tree/master/bitnami/mariadb) and the [PostgreSQL chart](https://github.com/bitnami/charts/tree/master/bitnami/postgresql) which are required for bootstrapping a MariaDB/PostgreSQL deployment for the database requirements of the Redmine application.
@@ -370,7 +370,7 @@ helm install my-release bitnami/redmine --set databaseType=postgresql
| `networkPolicy.egressRules.customRules` | Custom network policy rule | `{}` |
The above parameters map to the env variables defined in [bitnami/redmine](https://github.com/bitnami/bitnami-docker-redmine). For more information please refer to the [bitnami/redmine](https://github.com/bitnami/bitnami-docker-redmine) image documentation.
The above parameters map to the env variables defined in [bitnami/redmine](https://github.com/bitnami/containers/tree/main/bitnami/redmine). For more information please refer to the [bitnami/redmine](https://github.com/bitnami/containers/tree/main/bitnami/redmine) image documentation.
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -415,7 +415,7 @@ Redmine writes uploaded files to a persistent volume. By default that volume can
### Deploying to a sub-URI
(adapted from https://github.com/bitnami/bitnami-docker-redmine)
(adapted from https://github.com/bitnami/containers/tree/main/bitnami/redmine)
On certain occasions, you may need that Redmine is available under a specific sub-URI path rather than the root. A common scenario to this problem may arise if you plan to set up your Redmine container behind a reverse proxy. To deploy your Redmine container using a certain sub-URI you just need to follow these steps:
@@ -486,7 +486,7 @@ readinessProbe:
## Persistence
The [Bitnami Redmine](https://github.com/bitnami/bitnami-docker-redmine) image stores the Redmine data and configurations at the `/bitnami/redmine` path of the container.
The [Bitnami Redmine](https://github.com/bitnami/containers/tree/main/bitnami/redmine) image stores the Redmine data and configurations at the `/bitnami/redmine` path of the container.
Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube. The volume is created using dynamic volume provisioning. Clusters configured with NFS mounts require manually managed volumes and claims.