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

[bitnami/*] Unify READMEs (#14472)

Browse Source 
* [bitnami/*] Unify READMEs

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

* Fix typo

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

Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
This commit is contained in:
Carlos Rodríguez Hernández
2023-01-20 17:15:06 +01:00
committed by GitHub
parent 2ed7bf9767
commit 2064fb8dcc
98 changed files with 678 additions and 660 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/airflow/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ Apache Airflow is a tool to express and execute workflows as directed acyclic gr
[Overview of Apache Airflow](https://airflow.apache.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
```console
bitnami/apache/README.md
+6 -6
View File
@@ -7,10 +7,10 @@ Apache HTTP Server is an open-source HTTP server. The goal of this project is to
[Overview of Apache](https://httpd.apache.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
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/apache
```
@@ -34,7 +34,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/apache
```
@@ -47,7 +47,7 @@ These commands deploy Apache on the Kubernetes cluster in the default configurat
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -249,7 +249,7 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set imagePullPolicy=Always \
my-repo/apache
@@ -259,7 +259,7 @@ The above command sets the `imagePullPolicy` to `Always`.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/apache
```
bitnami/appsmith/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ Appsmith is an open source platform for building and maintaining internal tools,
[Overview of Appsmith](https://www.appsmith.com/)
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
```console
@@ -37,7 +37,8 @@ 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 my-release my-repo/appsmith
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/appsmith
```
The command deploys Appsmith on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -49,7 +50,7 @@ The command deploys Appsmith on the Kubernetes cluster in the default configurat
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -454,7 +455,7 @@ The above parameters map to the env variables defined in [bitnami/appsmith](http
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set appsmithUsername=admin \
--set appsmithPassword=password \
--set mariadb.auth.rootPassword=secretpassword \
@@ -468,7 +469,7 @@ The above command sets the appsmith 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 my-release -f values.yaml my-repo/appsmith
$ helm install my-release -f values.yaml my-repo/appsmith
```
> **Tip**: You can use the default [values.yaml](values.yaml)
bitnami/argo-cd/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ Argo CD is a continuous delivery tool for Kubernetes based on GitOps.
[Overview of Argo CD](https://argoproj.github.io/cd)
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
```console
@@ -33,7 +33,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm install my-release my-repo/argo-cd
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/argo-cd
```
The command deploys argo-cd on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -45,7 +46,7 @@ The command deploys argo-cd on the Kubernetes cluster in the default configurati
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -753,7 +754,7 @@ The above parameters map to the env variables defined in [bitnami/argo-cd](https
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set controller.replicaCount=2 \
--set server.metrics.enabled=true \
my-repo/argo-cd
@@ -766,7 +767,7 @@ The above command sets the argo-cd controller replicas to 2, and enabled argo-cd
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/argo-cd
$ helm install my-release -f values.yaml my-repo/argo-cd
```
> **Tip**: You can use the default [values.yaml](values.yaml)
bitnami/argo-workflows/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ Argo Workflows is meant to orchestrate Kubernetes jobs in parallel. It uses DAG
[Overview of Argo Workflows](https://argoproj.github.io/workflows)
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
```console
@@ -33,7 +33,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm install my-release my-repo/argo-workflows
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/argo-workflows
```
The command deploys Argo Workflows on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -45,7 +46,7 @@ The command deploys Argo Workflows on the Kubernetes cluster in the default conf
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -379,7 +380,7 @@ The above parameters map to the env variables defined in [bitnami/argo-workflow-
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set argo-workflowsUsername=admin \
--set argo-workflowsPassword=password \
--set mysql.auth.rootPassword=secretpassword \
@@ -393,7 +394,7 @@ The above command sets the Argo Workflows administrator account username and pas
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/argo-workflows
$ helm install my-release -f values.yaml my-repo/argo-workflows
```
> **Tip**: You can use the default [values.yaml](values.yaml)
bitnami/aspnet-core/README.md
+8 -8
View File
@@ -7,12 +7,12 @@ ASP.NET Core is an open-source framework for web application development created
[Overview of ASP.NET](https://github.com/dotnet/aspnetcore)
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
```console
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/aspnet-core
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/aspnet-core
```
## Introduction
@@ -32,7 +32,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/aspnet-core
```
@@ -45,7 +45,7 @@ These commands deploy a ASP.NET Core application on the Kubernetes cluster in th
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -241,15 +241,15 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
helm install my-release --set replicaCount=2 my-repo/aspnet-core
```console
$ helm install my-release --set replicaCount=2 my-repo/aspnet-core
```
The above command install ASP.NET Core chart with 2 replicas.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/aspnet-core
```
bitnami/cassandra/README.md
+7 -7
View File
@@ -7,7 +7,7 @@ Apache Cassandra is an open source distributed database management system design
[Overview of Apache Cassandra](http://cassandra.apache.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
```console
@@ -305,7 +305,7 @@ The above parameters map to the env variables defined in [bitnami/cassandra](htt
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set dbUser.user=admin,dbUser.password=password \
my-repo/cassandra
```
@@ -313,7 +313,7 @@ helm install my-release \
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/cassandra
$ helm install my-release -f values.yaml my-repo/cassandra
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -385,7 +385,7 @@ Find more information about how to deal with common errors related to Bitnami's
It's necessary to set the `dbUser.password` parameter when upgrading for readiness/liveness probes to work properly. When you install this chart for the first time, some notes will be displayed providing the credentials you must use. Please note down the password and run the command below to upgrade your chart:
```bash
```console
$ helm upgrade my-release my-repo/cassandra --set dbUser.password=[PASSWORD]
```
@@ -442,9 +442,9 @@ The `minimumAvailable` option has been renamed to `minAvailable` for consistency
An issue in StatefulSet manifest of the 4.x chart series rendered chart upgrades to be broken. The 5.0.0 series fixes this issue. To upgrade to the 5.x series you need to manually delete the Cassandra StatefulSet before executing the `helm upgrade` command.
```bash
kubectl delete sts -l release=<RELEASE_NAME>
helm upgrade <RELEASE_NAME> ...
```console
$ kubectl delete sts -l release=<RELEASE_NAME>
$ helm upgrade <RELEASE_NAME> ...
```
### To 4.0.0
bitnami/cert-manager/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ cert-manager is a Kubernetes add-on to automate the management and issuance of T
[Overview of cert-manager](https://github.com/jetstack/cert-manager)
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
```console
bitnami/clickhouse/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ ClickHouse is an open-source column-oriented OLAP database management system. Us
[Overview of ClickHouse](https://clickhouse.com/)
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
```console
@@ -41,7 +41,8 @@ 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 my-release my-repo/clickhouse
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/clickhouse
```
The command deploys ClickHouse on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -53,7 +54,7 @@ The command deploys ClickHouse on the Kubernetes cluster in the default configur
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -353,7 +354,7 @@ The above parameters map to the env variables defined in [bitnami/clickhouse](ht
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set auth.username=admin \
--set auth.password=password \
my-repo/clickhouse
@@ -366,7 +367,7 @@ The above command sets the ClickHouse administrator account username and passwor
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/clickhouse
$ helm install my-release -f values.yaml my-repo/clickhouse
```
> **Tip**: You can use the default [values.yaml](values.yaml)
bitnami/common/README.md
+1 -1
View File
@@ -11,7 +11,7 @@ dependencies:
repository: https://charts.bitnami.com/bitnami
```
```bash
```console
$ helm dependency update
```
bitnami/concourse/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ Concourse is an automation system written in Go. It is most commonly used for CI
[Overview of Concourse](https://concourse-ci.org/)
## TL;DR
```console
@@ -35,7 +35,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm install my-release my-repo/concourse
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/concourse
```
The command deploys concourse on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -47,7 +48,7 @@ The command deploys concourse on the Kubernetes cluster in the default configura
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -405,7 +406,7 @@ The above parameters map to the env variables defined in [bitnami/concourse](htt
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set secrets.localUsers=admin:password \
my-repo/concourse
```
@@ -417,7 +418,7 @@ The above command sets the Concourse account username and password to `admin` an
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/concourse
$ helm install my-release -f values.yaml my-repo/concourse
```
> **Tip**: You can use the default [values.yaml](values.yaml)
bitnami/consul/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ HashiCorp Consul is a tool for discovering and configuring services in your infr
[Overview of HashiCorp Consul](https://consul.io)
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
```console
bitnami/contour-operator/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ The Contour Operator extends the Kubernetes API to create, configure and manage
[Overview of Contour Operator](https://github.com/projectcontour/contour-operator)
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
```console
@@ -33,7 +33,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm install my-release my-repo/contour-operator
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/contour-operator
```
The command deploys the Contour Operator on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -45,7 +46,7 @@ The command deploys the Contour Operator on the Kubernetes cluster in the defaul
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -270,7 +271,7 @@ See [readme-generator-for-helm](https://github.com/bitnami-labs/readme-generator
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set livenessProbe.enabled=false \
my-repo/contour-operator
```
@@ -280,7 +281,7 @@ The above command disables the Operator liveness probes.
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/contour-operator
$ helm install my-release -f values.yaml my-repo/contour-operator
```
> **Tip**: You can use the default [values.yaml](values.yaml)
bitnami/contour/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ Contour is an open source Kubernetes ingress controller that works by deploying
[Overview of Contour](https://github.com/projectcontour/contour)
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
```console
bitnami/discourse/README.md
+2 -1
View File
@@ -7,7 +7,7 @@ Discourse is an open source discussion platform with built-in moderation and gov
[Overview of Discourse&reg;](http://www.discourse.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
```console
@@ -35,6 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/discourse
```
bitnami/dokuwiki/README.md
+8 -7
View File
@@ -7,7 +7,7 @@ DokuWiki is a standards-compliant wiki optimized for creating documentation. Des
[Overview of DokuWiki](https://www.splitbrain.org/projects/dokuwiki)
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
```console
@@ -33,6 +33,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/dokuwiki
```
@@ -305,8 +306,8 @@ certificates:
Secret can be created with:
```bash
kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
```console
$ kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
```
### TLS Certificate
@@ -330,13 +331,13 @@ certificates:
The certificate tls secret can be created with:
```bash
kubectl create secret tls my-secret --cert tls.crt --key tls.key
```console
$ kubectl create secret tls my-secret --cert tls.crt --key tls.key
```
The certificate chain is created with:
```bash
kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
```console
$ kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
```
## Troubleshooting
bitnami/drupal/README.md
+8 -7
View File
@@ -7,7 +7,7 @@ Drupal is one of the most versatile open source content management systems in th
[Overview of Drupal](http://drupal.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
```console
@@ -35,6 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/drupal
```
@@ -387,7 +388,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
1. Create the PersistentVolumeClaim
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/drupal
```
@@ -403,7 +404,7 @@ $ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/drupa
1. The specified `hostPath` directory must already exist (create one if it does not).
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/drupal
```
@@ -468,10 +469,10 @@ To upgrade to `9.0.0`, you have two alternatives:
Obtain the credentials and the name of the PVC used to hold the MariaDB data on your current release:
```console
export DRUPAL_PASSWORD=$(kubectl get secret --namespace default drupal -o jsonpath="{.data.drupal-password}" | base64 -d)
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default drupal-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default drupal-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=drupal -o jsonpath="{.items[0].metadata.name}")
$ export DRUPAL_PASSWORD=$(kubectl get secret --namespace default drupal -o jsonpath="{.data.drupal-password}" | base64 -d)
$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default drupal-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default drupal-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
$ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=drupal -o jsonpath="{.items[0].metadata.name}")
```
Upgrade your release (maintaining the version) disabling MariaDB and scaling Drupal replicas to 0:
bitnami/ejbca/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ EJBCA is an enterprise class PKI Certificate Authority software, built using Jav
[Overview of EJBCA](http://www.ejbca.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
```console
@@ -34,6 +34,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/ejbca
```
@@ -353,10 +354,10 @@ To upgrade to `1.0.0`, you have two alternatives:
Obtain the credentials and the name of the PVC used to hold the MariaDB data on your current release:
```console
export EJBCA_ADMIN_PASSWORD=$(kubectl get secret --namespace default ejbca -o jsonpath="{.data.ejbca-admin-password}" | base64 -d)
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default ejbca-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default ejbca-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=ejbca -o jsonpath="{.items[0].metadata.name}")
$ export EJBCA_ADMIN_PASSWORD=$(kubectl get secret --namespace default ejbca -o jsonpath="{.data.ejbca-admin-password}" | base64 -d)
$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default ejbca-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default ejbca-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
$ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=ejbca -o jsonpath="{.items[0].metadata.name}")
```
Upgrade your release (maintaining the version) disabling MariaDB and scaling EJBCA replicas to 0:
bitnami/elasticsearch/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ Elasticsearch is a distributed search and analytics engine. It is used for web s
[Overview of Elasticsearch](https://www.elastic.co/products/elasticsearch)
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
```console
bitnami/etcd/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ etcd is a distributed key-value store designed to securely store data across a c
[Overview of Etcd](https://etcd.io/)
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
```console
bitnami/external-dns/README.md
+7 -6
View File
@@ -7,7 +7,7 @@ ExternalDNS is a Kubernetes addon that configures public DNS servers with inform
[Overview of ExternalDNS](https://github.com/kubernetes-incubator/external-dns)
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
```console
@@ -30,7 +30,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/external-dns
```
@@ -347,7 +348,7 @@ $ helm install my-release \
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/external-dns
```
@@ -386,7 +387,7 @@ For instance, to install ExternalDNS on AWS, you need to:
- Install ExternalDNS chart using the command below:
> Note: replace the placeholder HOSTED_ZONE_IDENTIFIER and HOSTED_ZONE_NAME, with your hosted zoned identifier and name, respectively.
```bash
```console
$ helm install my-release \
--set provider=aws \
--set aws.zoneType=public \
@@ -414,8 +415,8 @@ No issues should be expected when upgrading.
The CRD was updated according to the latest changes in the upstream project. As a consequence, the CRD API version was moved from `apiextensions.k8s.io/v1beta1` to `apiextensions.k8s.io/v1`. If you deployed the Helm Chart using `crd.create=true` you need to manually delete the old CRD before upgrading the release.
```console
kubectl delete crd dnsendpoints.externaldns.k8s.io
helm upgrade my-release -f my-values.yaml
$ kubectl delete crd dnsendpoints.externaldns.k8s.io
$ helm upgrade my-release -f my-values.yaml
```
### To 4.3.0
bitnami/fluentd/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ Fluentd collects events from various data sources and writes them to files, RDBM
[Overview of Fluentd](https://www.fluentd.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
```console
bitnami/ghost/README.md
+3 -2
View File
@@ -7,7 +7,7 @@ Ghost is an open source publishing platform designed to create blogs, magazines,
[Overview of Ghost](https://ghost.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
```console
@@ -35,6 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/ghost
```
@@ -286,7 +287,7 @@ The above parameters map to the env variables defined in [bitnami/ghost](https:/
>
> To reserve a public IP address on GKE:
>
> ```bash
> ```console
> $ gcloud compute addresses create ghost-public-ip
> ```
>
bitnami/gitea/README.md
+4 -3
View File
@@ -7,7 +7,7 @@ Gitea is a lightweight code hosting solution. Written in Go, features low resour
[Overview of Gitea](https://gitea.io/)
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
```console
@@ -35,6 +35,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 repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/gitea
```
@@ -313,7 +314,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
1. Create the PersistentVolumeClaim
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/gitea
```
@@ -329,7 +330,7 @@ $ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/gitea
1. The specified `hostPath` directory must already exist (create one if it does not).
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/gitea
```
bitnami/grafana-loki/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ Grafana Loki is a horizontally scalable, highly available, and multi-tenant log
[Overview of Grafana Loki](https://grafana.com/oss/loki/)
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
```console
@@ -36,7 +36,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm install my-release my-repo/grafana-loki
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/grafana-loki
```
The command deploys grafana-loki on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +49,7 @@ The command deploys grafana-loki on the Kubernetes cluster in the default config
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -1211,7 +1212,7 @@ The above parameters map to the env variables defined in [bitnami/grafana-loki](
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set loki.traces.jaeger.grpc=true \
my-repo/grafana-loki
```
@@ -1221,7 +1222,7 @@ The above command enables the Jaeger GRPC traces.
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/grafana-loki
$ helm install my-release -f values.yaml my-repo/grafana-loki
```
> **Tip**: You can use the default [values.yaml](values.yaml)
bitnami/grafana-operator/README.md
+3 -3
View File
@@ -7,7 +7,7 @@ Grafana Operator is a Kubernetes operator that enables the installation and mana
[Overview of Grafana Operator](https://github.com/integr8ly/grafana-operator)
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
```console
@@ -285,7 +285,7 @@ The above command sets the `livenessProbe.successThreshold` to `5`.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/grafana-operator
```
@@ -315,7 +315,7 @@ Find more information about how to deal with common errors related to Bitnami's
## Upgrading
```bash
```console
$ helm upgrade my-release my-repo/grafana-operator
```
bitnami/grafana-tempo/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ Grafana Tempo is a distributed tracing system that has out-of-the-box integratio
[Overview of Grafana Tempo](https://github.com/grafana/tempo)
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
```console
@@ -36,7 +36,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm install my-release my-repo/grafana-tempo
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/grafana-tempo
```
The command deploys grafana-tempo on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +49,7 @@ The command deploys grafana-tempo on the Kubernetes cluster in the default confi
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -804,7 +805,7 @@ The above parameters map to the env variables defined in [bitnami/grafana-tempo]
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set tempo.traces.jaeger.grpc=true \
my-repo/grafana-tempo
```
@@ -814,7 +815,7 @@ The above command enables the Jaeger GRPC traces.
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/grafana-tempo
$ helm install my-release -f values.yaml my-repo/grafana-tempo
```
> **Tip**: You can use the default [values.yaml](values.yaml)
bitnami/grafana/README.md
+3 -3
View File
@@ -7,7 +7,7 @@ Grafana is an open source metric analytics and visualization suite for visualizi
[Overview of Grafana](https://grafana.com/)
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
```console
@@ -636,8 +636,8 @@ This major release renames several values in this chart and adds missing feature
Since the volume access mode when persistence is enabled is `ReadWriteOnce` in order to upgrade the deployment you will need to either use the `Recreate` strategy or delete the old deployment.
```console
kubectl delete deployment <deployment-name>
helm upgrade <release-name> my-repo/grafana
$ kubectl delete deployment <deployment-name>
$ helm upgrade <release-name> my-repo/grafana
```
### To 4.1.0
bitnami/haproxy/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ HAProxy is a TCP proxy and a HTTP reverse proxy. It supports SSL termination and
[Overview of HAProxy](http://www.haproxy.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
```console
@@ -35,7 +35,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm install my-release my-repo/haproxy
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/haproxy
```
The command deploys haproxy on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -47,7 +48,7 @@ The command deploys haproxy on the Kubernetes cluster in the default configurati
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -203,7 +204,7 @@ The above parameters map to the env variables defined in [bitnami/haproxy](https
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set service.type=LoadBalancer \
my-repo/haproxy
```
@@ -215,7 +216,7 @@ The above command sets the HAProxy service type as LoadBalancer.
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/haproxy
$ helm install my-release -f values.yaml my-repo/haproxy
```
> **Tip**: You can use the default [values.yaml](values.yaml)
bitnami/harbor/README.md
+10 -10
View File
@@ -7,12 +7,12 @@ Harbor is an open source trusted cloud-native registry to store, sign, and scan
[Overview of Harbor](https://goharbor.io/)
## TL;DR
```bash
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/harbor
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/harbor
```
## Introduction
@@ -42,19 +42,19 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
## Installing the Chart
Install the Harbor helm chart with a release name `my-release`:
To install the chart with the release name `my-release`:
```bash
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/harbor
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/harbor
```
## Uninstalling the Chart
To uninstall/delete the `my-release` deployment:
```bash
helm delete --purge my-release
```console
$ helm delete --purge my-release
```
Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manually delete the PVCs.
bitnami/influxdb/README.md
+2 -2
View File
@@ -7,7 +7,7 @@ InfluxDB(TM) is an open source time-series database. It is a core component of t
[Overview of InfluxDB&trade;](https://www.influxdata.com/products/influxdb-overview)
InfluxDB(TM) is a trademark owned by InfluxData, which is not affiliated with, and does not endorse, this site.
## TL;DR
```console
@@ -446,7 +446,7 @@ Find more information about how to deal with common errors related to Bitnami's
It's necessary to specify the existing passwords while performing an upgrade to ensure the secrets are not updated with invalid randomly generated passwords. Remember to specify the existing values of the `auth.admin.password`, `user.pwd`, ` auth.readUser.password` and `auth.writeUser.password` parameters when upgrading the chart:
```bash
```console
$ helm upgrade my-release my-repo/influxdb \
--set auth.admin.password=[ADMIN_USER_PASSWORD] \
--set auth.user.password=[USER_PASSWORD] \
bitnami/jaeger/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ Jaeger is a distributed tracing system. It is used for monitoring and troublesho
[Overview of Jaeger](https://jaegertracing.io/)
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
```console
bitnami/jasperreports/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ JasperReports Server is a stand-alone and embeddable reporting server. It is a c
[Overview of JasperReports](http://community.jaspersoft.com/project/jasperreports-server)
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
```console
@@ -35,6 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/jasperreports
```
@@ -418,10 +419,10 @@ To upgrade to `9.0.0`, it should be done reusing the PVCs used to hold both the
Obtain the credentials and the names of the PVCs used to hold both the MariaDB and JasperReports data on your current release:
```console
export JASPERREPORTS_PASSWORD=$(kubectl get secret --namespace default jasperreports -o jsonpath="{.data.jasperreports-password}" | base64 -d)
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default jasperreports-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default jasperreports-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=jasperreports -o jsonpath="{.items[0].metadata.name}")
$ export JASPERREPORTS_PASSWORD=$(kubectl get secret --namespace default jasperreports -o jsonpath="{.data.jasperreports-password}" | base64 -d)
$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default jasperreports-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default jasperreports-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
$ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=jasperreports -o jsonpath="{.items[0].metadata.name}")
```
Delete the JasperReports deployment and delete the MariaDB statefulset. Notice the option `--cascade=false` in the latter:
bitnami/jenkins/README.md
+8 -8
View File
@@ -7,12 +7,12 @@ Jenkins is an open source Continuous Integration and Continuous Delivery (CI/CD)
[Overview of Jenkins](http://jenkins-ci.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
```console
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/jenkins
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/jenkins
```
## Introduction
@@ -33,8 +33,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/jenkins
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/jenkins
```
These commands deploy Jenkins on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -46,7 +46,7 @@ These commands deploy Jenkins on the Kubernetes cluster in the default configura
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -239,7 +239,7 @@ The above command sets the Jenkins 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 my-release -f values.yaml my-repo/jenkins
$ helm install my-release -f values.yaml my-repo/jenkins
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -390,7 +390,7 @@ Backwards compatibility is not guaranteed unless you modify the labels used on t
Use the workaround below to upgrade from versions previous to 1.0.0. The following example assumes that the release name is jenkins:
```console
kubectl patch deployment jenkins --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
$ kubectl patch deployment jenkins --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
```
## License
bitnami/joomla/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ Joomla! is an award winning open source CMS platform for building websites and a
[Overview of Joomla!](http://www.joomla.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
```console
@@ -35,6 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/joomla
```
@@ -419,10 +420,10 @@ To upgrade to `9.0.0`, it should be done reusing the PVCs used to hold both the
Obtain the credentials and the names of the PVCs used to hold both the MariaDB and Joomla data on your current release:
```console
export JOOMLA_PASSWORD=$(kubectl get secret --namespace default joomla -o jsonpath="{.data.joomla-password}" | base64 -d)
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default joomla-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default joomla-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=joomla -o jsonpath="{.items[0].metadata.name}")
$ export JOOMLA_PASSWORD=$(kubectl get secret --namespace default joomla -o jsonpath="{.data.joomla-password}" | base64 -d)
$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default joomla-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default joomla-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
$ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=joomla -o jsonpath="{.items[0].metadata.name}")
```
Upgrade your release (maintaining the version) disabling MariaDB and scaling Joomla replicas to 0:
bitnami/jupyterhub/README.md
+2 -2
View File
@@ -7,7 +7,7 @@ JupyterHub brings the power of notebooks to groups of users. It gives users acce
[Overview of JupyterHub](https://jupyter.org/hub)
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
```console
@@ -510,7 +510,7 @@ The above command sets the `proxy.livenessProbe.successThreshold` to `5`.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/jupyterhub
```
bitnami/kafka/README.md
+16 -16
View File
@@ -7,12 +7,12 @@ Apache Kafka is a distributed streaming platform designed to build real-time pip
[Overview of Apache Kafka](http://kafka.apache.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
```console
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/kafka
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/kafka
```
## Introduction
@@ -32,8 +32,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/kafka
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/kafka
```
These commands deploy Kafka on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -45,7 +45,7 @@ These commands deploy Kafka on the Kubernetes cluster in the default configurati
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -496,7 +496,7 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set replicaCount=3 \
my-repo/kafka
```
@@ -506,7 +506,7 @@ The above command deploys Kafka with 3 brokers (replicas).
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/kafka
$ helm install my-release -f values.yaml my-repo/kafka
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -563,8 +563,8 @@ In order to configure TLS authentication/encryption, you **can** create a secret
For instance, to configure TLS authentication on a Kafka cluster with 2 Kafka brokers use the commands below to create the secrets:
```console
kubectl create secret generic kafka-jks-0 --from-file=kafka.truststore.jks=./kafka.truststore.jks --from-file=kafka.keystore.jks=./kafka-0.keystore.jks
kubectl create secret generic kafka-jks-1 --from-file=kafka.truststore.jks=./kafka.truststore.jks --from-file=kafka.keystore.jks=./kafka-1.keystore.jks
$ kubectl create secret generic kafka-jks-0 --from-file=kafka.truststore.jks=./kafka.truststore.jks --from-file=kafka.keystore.jks=./kafka-0.keystore.jks
$ kubectl create secret generic kafka-jks-1 --from-file=kafka.truststore.jks=./kafka.truststore.jks --from-file=kafka.keystore.jks=./kafka-1.keystore.jks
```
> **Note**: the command above assumes you already created the truststore and keystores files. This [script](https://raw.githubusercontent.com/confluentinc/confluent-platform-security-tools/master/kafka-generate-ssl.sh) can help you with the JKS files generation.
@@ -1009,8 +1009,8 @@ Backwards compatibility is not guaranteed when Kafka metrics are enabled, unless
Use the workaround below to upgrade from versions previous to 7.0.0. The following example assumes that the release name is kafka:
```console
helm upgrade kafka my-repo/kafka --version 6.1.8 --set metrics.kafka.enabled=false
helm upgrade kafka my-repo/kafka --version 7.0.0 --set metrics.kafka.enabled=true
$ helm upgrade kafka my-repo/kafka --version 6.1.8 --set metrics.kafka.enabled=false
$ helm upgrade kafka my-repo/kafka --version 7.0.0 --set metrics.kafka.enabled=true
```
### To 2.0.0
@@ -1019,8 +1019,8 @@ Backwards compatibility is not guaranteed unless you modify the labels used on t
Use the workaround below to upgrade from versions previous to 2.0.0. The following example assumes that the release name is kafka:
```console
kubectl delete statefulset kafka-kafka --cascade=false
kubectl delete statefulset kafka-zookeeper --cascade=false
$ kubectl delete statefulset kafka-kafka --cascade=false
$ kubectl delete statefulset kafka-zookeeper --cascade=false
```
### To 1.0.0
@@ -1029,8 +1029,8 @@ Backwards compatibility is not guaranteed unless you modify the labels used on t
Use the workaround below to upgrade from versions previous to 1.0.0. The following example assumes that the release name is kafka:
```console
kubectl delete statefulset kafka-kafka --cascade=false
kubectl delete statefulset kafka-zookeeper --cascade=false
$ kubectl delete statefulset kafka-kafka --cascade=false
$ kubectl delete statefulset kafka-zookeeper --cascade=false
```
## License
bitnami/keycloak/README.md
+8 -8
View File
@@ -7,12 +7,12 @@ Keycloak is a high performance Java-based identity and access management solutio
[Overview of Keycloak](https://www.keycloak.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
```console
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/keycloak
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/keycloak
```
## Introduction
@@ -32,7 +32,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/keycloak
```
@@ -45,7 +45,7 @@ These commands deploy a Keycloak application on the Kubernetes cluster in the de
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -350,8 +350,8 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
helm install my-release --set auth.adminPassword=secretpassword my-repo/keycloak
```console
$ helm install my-release --set auth.adminPassword=secretpassword my-repo/keycloak
```
The above command sets the Keycloak administrator password to `secretpassword`.
@@ -360,7 +360,7 @@ The above command sets the Keycloak administrator password to `secretpassword`.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/keycloak
```
bitnami/kiam/README.md
+8 -8
View File
@@ -7,12 +7,12 @@ kiam is a proxy that captures AWS Metadata API requests. It allows AWS IAM roles
[Overview of Kiam](https://github.com/uswitch/kiam)
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
```console
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/kiam
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/kiam
```
> NOTE: KIAM has been designed to work on a Kubernetes cluster deployed on top of AWS, although it is possible to deploy it in other environments.
@@ -34,7 +34,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/kiam
```
@@ -47,7 +47,7 @@ These commands deploy a kiam application on the Kubernetes cluster in the defaul
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -356,15 +356,15 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
helm install my-release --set server.resourceType=deployment my-repo/kiam
```console
$ helm install my-release --set server.resourceType=deployment my-repo/kiam
```
The above command sets the server nodes to be deployed as Deployment objects.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/kiam
```
bitnami/kibana/README.md
+5 -8
View File
@@ -7,7 +7,7 @@ Kibana is an open source, browser based analytics and search dashboard for Elast
[Overview of Kibana](https://www.elastic.co/products/kibana)
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
```console
@@ -30,19 +30,16 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
## Installing the Chart
This chart requires an Elasticsearch instance to work. You can use an already existing Elasticsearch instance.
To install the chart with the release name `my-release`:
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release \
$ helm install my-release my-repo/kibana \
--set elasticsearch.hosts[0]=<Hostname of your ES instance> \
--set elasticsearch.port=<port of your ES instance> \
my-repo/kibana
```
These commands deploy Kibana on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
This chart requires an Elasticsearch instance to work. You can use an already existing Elasticsearch instance. These commands deploy Kibana 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`
@@ -475,4 +472,4 @@ Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
limitations under the License.
bitnami/kong/README.md
+14 -14
View File
@@ -7,12 +7,12 @@ Kong is an open source Microservice API gateway and platform designed for managi
[Overview of Kong](https://konghq.com/kong-community-edition/)
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
```console
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/kong
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/kong
```
## Introduction
@@ -34,8 +34,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/kong
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/kong
```
These commands deploy kong on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -47,7 +47,7 @@ These commands deploy kong on the Kubernetes cluster in the default configuratio
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
## Parameters
@@ -352,7 +352,7 @@ To uninstall/delete the `my-release` deployment:
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set service.exposeAdmin=true my-repo/kong
```
@@ -361,7 +361,7 @@ The above command exposes the Kong admin ports inside the Kong service.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/kong
$ helm install my-release -f values.yaml my-repo/kong
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -381,13 +381,13 @@ The Bitnami Kong chart allows setting two database backends: PostgreSQL or Cassa
- Deploy the PostgreSQL sub-chart (default)
```console
helm install my-release my-repo/kong
$ helm install my-release my-repo/kong
```
- Use an external PostgreSQL database
```console
helm install my-release my-repo/kong \
$ helm install my-release my-repo/kong \
--set postgresql.enabled=false \
--set postgresql.external.host=_HOST_OF_YOUR_POSTGRESQL_INSTALLATION_ \
--set postgresql.external.password=_PASSWORD_OF_YOUR_POSTGRESQL_INSTALLATION_ \
@@ -397,7 +397,7 @@ The Bitnami Kong chart allows setting two database backends: PostgreSQL or Cassa
- Deploy the Cassandra sub-chart
```console
helm install my-release my-repo/kong \
$ helm install my-release my-repo/kong \
--set database=cassandra \
--set postgresql.enabled=false \
--set cassandra.enabled=true
@@ -406,7 +406,7 @@ The Bitnami Kong chart allows setting two database backends: PostgreSQL or Cassa
- Use an existing Cassandra installation
```console
helm install my-release my-repo/kong \
$ helm install my-release my-repo/kong \
--set database=cassandra \
--set postgresql.enabled=false \
--set cassandra.enabled=false \
@@ -518,7 +518,7 @@ Find more information about how to deal with common errors related to Bitnami's
It's necessary to specify the existing passwords while performing a upgrade to ensure the secrets are not updated with invalid randomly generated passwords. Remember to specify the existing values of the `postgresql.postgresqlPassword` or `cassandra.password` parameters when upgrading the chart:
```bash
```console
$ helm upgrade my-release my-repo/kong \
--set database=postgresql
--set postgresql.enabled=true
@@ -643,4 +643,4 @@ Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
limitations under the License.
bitnami/kube-prometheus/README.md
+10 -15
View File
@@ -7,10 +7,10 @@ Prometheus Operator provides easy monitoring definitions for Kubernetes services
[Overview of Prometheus Operator](https://github.com/coreos/prometheus-operator)
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
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/kube-prometheus
```
@@ -38,15 +38,10 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
## Installing the Chart
Add the `bitnami` charts repo to Helm:
```bash
$ helm repo add my-repo https://charts.bitnami.com/bitnami
```
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/kube-prometheus
```
@@ -58,7 +53,7 @@ The command deploys kube-prometheus on the Kubernetes cluster in the default con
To uninstall/delete the `my-release` release:
```bash
```console
$ helm delete my-release
```
@@ -704,7 +699,7 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set operator.logLevel=debug \
--set prometheus.replicaCount=5 \
@@ -715,7 +710,7 @@ The above command sets the Prometheus Operator `logLevel` to `debug`. Additional
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/kube-prometheus
```
@@ -763,7 +758,7 @@ Find more information about how to deal with common errors related to Bitnami's
## Upgrading
```bash
```console
$ helm upgrade my-release my-repo/kube-prometheus
```
@@ -885,7 +880,7 @@ The Thanos sidecar svc is transformed into a headless service by default so Than
To upgrade from version 2.0.0, previously remove the Thanos sidecar svc to avoid issues with immutable fields:
```bash
```console
$ kubectl delete svc my-relase-kube-prometheus-prometheus-thanos
$ helm upgrade my-release --set prometheus.thanos.create=true my-repo/kube-prometheus
```
@@ -918,4 +913,4 @@ Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
limitations under the License.
bitnami/kube-state-metrics/README.md
+9 -14
View File
@@ -7,10 +7,10 @@ kube-state-metrics is a simple service that listens to the Kubernetes API server
[Overview of Kube State Metrics](https://github.com/kubernetes/kube-state-metrics)
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
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/kube-state-metrics
```
@@ -28,15 +28,10 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
## Installing the Chart
Add the `bitnami` charts repo to Helm:
```bash
$ helm repo add my-repo https://charts.bitnami.com/bitnami
```
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/kube-state-metrics
```
@@ -46,7 +41,7 @@ The command deploys kube-state-metrics on the Kubernetes cluster in the default
To uninstall/delete the `my-release` release:
```bash
```console
$ helm delete my-release
```
@@ -208,13 +203,13 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example the following command sets the `replicas` of the kube-state-metrics Pods to `2`.
```bash
```console
$ helm install my-release --set replicas=2 my-repo/kube-state-metrics
```
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/kube-state-metrics
```
@@ -246,7 +241,7 @@ Find more information about how to deal with common errors related to Bitnami's
## Upgrading
```bash
```console
$ helm upgrade my-release my-repo/kube-state-metrics
```
@@ -293,4 +288,4 @@ Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
limitations under the License.
bitnami/kubeapps/README.md
+55 -57
View File
@@ -7,13 +7,12 @@ Kubeapps is a web-based UI for launching and managing applications on Kubernetes
[Overview of Kubeapps](https://github.com/vmware-tanzu/kubeapps)
## TL;DR
```bash
helm repo add my-repo https://charts.bitnami.com/bitnami
kubectl create namespace kubeapps
helm install kubeapps --namespace kubeapps my-repo/kubeapps
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/kubeapps --namespace kubeapps --create-namespace
```
> Check out the [getting started](https://github.com/vmware-tanzu/kubeapps/blob/main/site/content/docs/latest/tutorials/getting-started.md) to start deploying apps with Kubeapps.
@@ -44,12 +43,11 @@ It also packages the [Bitnami PostgreSQL chart](https://github.com/bitnami/chart
## Installing the Chart
To install the chart with the release name `kubeapps`:
To install the chart with the release name `my-release`:
```bash
helm repo add my-repo https://charts.bitnami.com/bitnami
kubectl create namespace kubeapps
helm install kubeapps --namespace kubeapps my-repo/kubeapps
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/kubeapps --namespace kubeapps --create-namespace
```
The command deploys Kubeapps on the Kubernetes cluster in the `kubeapps` namespace. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -570,8 +568,8 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
```bash
helm install kubeapps --namespace kubeapps \
```console
$ helm install kubeapps --namespace kubeapps \
--set ingress.enabled=true \
my-repo/kubeapps
```
@@ -580,8 +578,8 @@ The above command enables an Ingress Rule to expose Kubeapps.
Alternatively, a YAML file that specifies the values for parameters can be provided while installing the chart. For example,
```bash
helm install kubeapps --namespace kubeapps -f custom-values.yaml my-repo/kubeapps
```console
$ helm install kubeapps --namespace kubeapps -f custom-values.yaml my-repo/kubeapps
```
## Configuration and installation details
@@ -604,8 +602,8 @@ The simplest way to expose the Kubeapps Dashboard is to assign a LoadBalancer ty
Wait for your cluster to assign a LoadBalancer IP or Hostname to the `kubeapps` Service and access it on that address:
```bash
kubectl get services --namespace kubeapps --watch
```console
$ kubectl get services --namespace kubeapps --watch
```
#### Ingress
@@ -664,15 +662,15 @@ You can upgrade Kubeapps from the Kubeapps web interface. Select the namespace i
You can also use the Helm CLI to upgrade Kubeapps, first ensure you have updated your local chart repository cache:
```bash
helm repo update
```console
$ helm repo update
```
Now upgrade Kubeapps:
```bash
export RELEASE_NAME=kubeapps
helm upgrade $RELEASE_NAME my-repo/kubeapps
```console
$ export RELEASE_NAME=kubeapps
$ helm upgrade $RELEASE_NAME my-repo/kubeapps
```
If you find issues upgrading Kubeapps, check the [troubleshooting](#error-while-upgrading-the-chart) section.
@@ -685,11 +683,11 @@ This major updates the PostgreSQL subchart to its newest major, 12.0.0. [Here](h
To uninstall/delete the `kubeapps` deployment:
```bash
helm uninstall -n kubeapps kubeapps
```console
$ helm uninstall -n kubeapps kubeapps
# Optional: Only if there are no more instances of Kubeapps
kubectl delete crd apprepositories.kubeapps.com
$ kubectl delete crd apprepositories.kubeapps.com
```
The first command removes most of the Kubernetes components associated with the chart and deletes the release. After that, if there are no more instances of Kubeapps in the cluster you can manually delete the `apprepositories.kubeapps.com` CRD used by Kubeapps that is shared for the entire cluster.
@@ -698,8 +696,8 @@ The first command removes most of the Kubernetes components associated with the
If you have dedicated a namespace only for Kubeapps you can completely clean the remaining completed/failed jobs or any stale resources by deleting the namespace
```bash
kubectl delete namespace kubeapps
```console
$ kubectl delete namespace kubeapps
```
## FAQ
@@ -735,8 +733,8 @@ Have a look at the [dashboard documentation](https://github.com/vmware-tanzu/kub
The example below will match the URL `http://example.com` to the Kubeapps dashboard. For further configuration, please refer to your specific Ingress configuration docs (e.g., [NGINX](https://github.com/kubernetes/ingress-nginx) or [HAProxy](https://github.com/haproxytech/kubernetes-ingress)).
```bash
helm install kubeapps my-repo/kubeapps \
```console
$ helm install kubeapps my-repo/kubeapps \
--namespace kubeapps \
--set ingress.enabled=true \
--set ingress.hostname=example.com \
@@ -746,7 +744,7 @@ helm install kubeapps my-repo/kubeapps \
If you are using LDAP via Dex with OIDC or you are getting an error message like `upstream sent too big header while reading response header from upstream` it means the cookie size is too big and can't be processed by the Ingress Controller.
You can work around this problem by setting the following Nginx ingress annotations (look for similar annotations in your preferred Ingress Controller):
```bash
```
# rest of the helm install ... command
--set ingress.annotations."nginx\.ingress\.kubernetes\.io/proxy-read-timeout"=600
--set ingress.annotations."nginx\.ingress\.kubernetes\.io/proxy-buffer-size"=8k
@@ -757,8 +755,8 @@ You can work around this problem by setting the following Nginx ingress annotati
You may want to serve Kubeapps with a subpath, for instance `http://example.com/subpath`, you have to set the proper Ingress configuration. If you are using the ingress configuration provided by the Kubeapps chart, you will have to set the `ingress.hostname` and `path` parameters:
```bash
helm install kubeapps my-repo/kubeapps \
```console
$ helm install kubeapps my-repo/kubeapps \
--namespace kubeapps \
--set ingress.enabled=true \
--set ingress.hostname=example.com \
@@ -768,8 +766,8 @@ helm install kubeapps my-repo/kubeapps \
Besides, if you are using the OAuth2/OIDC login (more information at the [using an OIDC provider documentation](https://github.com/vmware-tanzu/kubeapps/blob/main/site/content/docs/latest/tutorials/using-an-OIDC-provider.md)), you will need, also, to configure the different URLs:
```bash
helm install kubeapps my-repo/kubeapps \
```console
$ helm install kubeapps my-repo/kubeapps \
--namespace kubeapps \
# ... other OIDC and ingress flags
--set authProxy.oauthLoginURI="/subpath/oauth2/login" \
@@ -879,14 +877,14 @@ Error: namespaces "kubeapps" is forbidden: User "system:serviceaccount:kube-syst
It is possible, though uncommon, that your cluster does not have Role-Based Access Control (RBAC) enabled. To check if your cluster has RBAC you can run the following command:
```bash
kubectl api-versions
```console
$ kubectl api-versions
```
If the above command does not include entries for `rbac.authorization.k8s.io` you should perform the chart installation by setting `rbac.create=false`:
```bash
helm install --name kubeapps --namespace kubeapps my-repo/kubeapps --set rbac.create=false
```console
$ helm install --name kubeapps --namespace kubeapps my-repo/kubeapps --set rbac.create=false
```
### Error while upgrading the Chart
@@ -900,43 +898,43 @@ It is possible that when upgrading Kubeapps an error appears. That can be caused
1. (Optional) Backup your personal repositories (if you have any):
```bash
kubectl get apprepository -A -o yaml > <repo name>.yaml
```console
$ kubectl get apprepository -A -o yaml > <repo name>.yaml
```
2. Delete Kubeapps:
```bash
helm del --purge kubeapps
```console
$ helm del --purge kubeapps
```
3. (Optional) Delete the App Repositories CRD:
> **Warning**: Do not run this step if you have more than one Kubeapps installation in your cluster.
```bash
kubectl delete crd apprepositories.kubeapps.com
```console
$ kubectl delete crd apprepositories.kubeapps.com
```
4. (Optional) Clean the Kubeapps namespace:
> **Warning**: Do not run this step if you have workloads other than Kubeapps in the `kubeapps` namespace.
```bash
kubectl delete namespace kubeapps
```console
$ kubectl delete namespace kubeapps
```
5. Install the latest version of Kubeapps (using any custom modifications you need):
```bash
helm repo update
helm install --name kubeapps --namespace kubeapps my-repo/kubeapps
```console
$ helm repo update
$ helm install --name kubeapps --namespace kubeapps my-repo/kubeapps
```
6. (Optional) Restore any repositories you backed up in the first step:
```bash
kubectl apply -f <repo name>.yaml
```console
$ kubectl apply -f <repo name>.yaml
```
After that you should be able to access the new version of Kubeapps. If the above doesn't work for you or you run into any other issues please open an [issue](https://github.com/vmware-tanzu/kubeapps/issues/new).
@@ -965,7 +963,7 @@ PASSWORDS ERROR: you must provide your current passwords when upgrade the releas
The error gives you generic instructions for retrieving the PostgreSQL password, but if you have installed a Kubeapps version prior to 2.3.1, the name of the secret will differ. Run the following command:
```console
export POSTGRESQL_PASSWORD=$(kubectl get secret --namespace "kubeapps" kubeapps-db -o jsonpath="{.data.postgresql-password}" | base64 -d)
$ export POSTGRESQL_PASSWORD=$(kubectl get secret --namespace "kubeapps" kubeapps-db -o jsonpath="{.data.postgresql-password}" | base64 -d)
```
> NOTE: Replace the namespace in the command with the namespace in which you have deployed Kubeapps.
@@ -981,7 +979,7 @@ Error: UPGRADE FAILED: rendered manifests contain a resource that already exists
To bypass this issue, you will need to before delete all the initialRepos from the chart values (only the `bitnami` repo by default):
```console
kubectl delete apprepositories.kubeapps.com -n kubeapps bitnami
$ kubectl delete apprepositories.kubeapps.com -n kubeapps bitnami
```
> NOTE: Replace the namespace in the command with the namespace in which you have deployed Kubeapps.
@@ -991,7 +989,7 @@ After that, you will be able to upgrade Kubeapps to 2.3.1 using the existing dat
> **WARNING**: Make sure that the variable `$POSTGRESQL_PASSWORD` is properly populated. Setting a wrong (or empty) password will corrupt the release.
```console
helm upgrade kubeapps my-repo/kubeapps -n kubeapps --set postgresql.postgresqlPassword=$POSTGRESQL_PASSWORD
$ helm upgrade kubeapps my-repo/kubeapps -n kubeapps --set postgresql.postgresqlPassword=$POSTGRESQL_PASSWORD
```
### Upgrading to 2.0.1 (Chart 5.0.0)
@@ -1015,7 +1013,7 @@ helm upgrade kubeapps my-repo/kubeapps -n kubeapps --set postgresql.postgresqlPa
> Note: The command below assumes that Kubeapps has been deployed in the kubeapps namespace using "kubeapps" as release name, if that is not the case, adapt the command accordingly.
```console
kubectl delete statefulset -n kubeapps kubeapps-postgresql-master kubeapps-postgresql-slave
$ kubectl delete statefulset -n kubeapps kubeapps-postgresql-master kubeapps-postgresql-slave
```
**Useful links**
@@ -1036,8 +1034,8 @@ Due to the last point, it is necessary to run a command before upgrading to Kube
> Note: The command below assumes that Kubeapps has been deployed in the kubeapps namespace using "kubeapps" as release name, if that is not the case, adapt the command accordingly.
```bash
kubectl delete statefulset -n kubeapps kubeapps-postgresql-master kubeapps-postgresql-slave
```console
$ kubectl delete statefulset -n kubeapps kubeapps-postgresql-master kubeapps-postgresql-slave
```
After that, you should be able to upgrade Kubeapps as always and the database will be repopulated.
@@ -1056,4 +1054,4 @@ Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
limitations under the License.
bitnami/kubernetes-event-exporter/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ Kubernetes Event Exporter makes it easy to export Kubernetes events to other too
[Overview of Kubernetes Event Exporter](https://github.com/resmoio/kubernetes-event-exporter)
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
```console
bitnami/logstash/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ Logstash is an open source data processing engine. It ingests data from multiple
[Overview of Logstash](http://logstash.net)
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
```console
bitnami/magento/README.md
+7 -6
View File
@@ -7,7 +7,7 @@ Magento is a powerful open source e-commerce platform. With easy customizations
[Overview of Magento](http://www.magento.com)
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
```console
@@ -35,6 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/magento
```
@@ -359,7 +360,7 @@ The above parameters map to the env variables defined in [bitnami/magento](https
>
> To reserve a public IP address on GKE:
>
> ```bash
> ```console
> $ gcloud compute addresses create magento-public-ip
> ```
>
@@ -554,7 +555,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
1. Create the PersistentVolumeClaim
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/magento
```
@@ -570,7 +571,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
1. The specified `hostPath` directory must already exist (create one if it does not).
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/magento
```
@@ -589,8 +590,8 @@ certificates:
```
> Tip! You can create a secret containing your CA certificates using the following command:
```bash
kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
```console
$ kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
```
## Troubleshooting
bitnami/mariadb-galera/README.md
+20 -25
View File
@@ -7,10 +7,10 @@ MariaDB Galera is a multi-primary database cluster solution for synchronous repl
[Overview of MariaDB Galera](https://mariadb.com/kb/en/library/galera-cluster/)
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
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/mariadb-galera
```
@@ -29,15 +29,10 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
## Installing the Chart
Add the `bitnami` charts repo to Helm:
```bash
$ helm repo add my-repo https://charts.bitnami.com/bitnami
```
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/mariadb-galera
```
@@ -49,13 +44,13 @@ The command deploys MariaDB Galera on the Kubernetes cluster in the default conf
For a graceful termination, set the replica count of the Pods in the `mariadb-galera` StatefulSet to `0`:
```bash
```console
$ kubectl scale sts my-release-mariadb-galera --replicas=0
```
To uninstall/delete the `my-release` release:
```bash
```console
$ helm delete --purge my-release
```
@@ -267,7 +262,7 @@ The above parameters map to the env variables defined in [bitnami/mariadb-galera
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set rootUser.password=secretpassword,
--set db.user=app_database \
@@ -280,7 +275,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
```console
$ helm install my-release -f values.yaml my-repo/mariadb-galera
```
@@ -292,7 +287,7 @@ While the chart allows you to specify the server configuration using the `.maria
For example, if you want to enable the PAM cleartext plugin, specify the command line parameter while deploying the chart like so:
```bash
```console
$ helm install my-release \
--set extraFlags="--pam-use-cleartext-plugin=ON" \
my-repo/mariadb-galera
@@ -367,7 +362,7 @@ For example:
First, create the secret with the cetificates files:
```console
kubectl create secret generic certificates-tls-secret --from-file=./cert.pem --from-file=./cert.key --from-file=./ca.pem
$ kubectl create secret generic certificates-tls-secret --from-file=./cert.pem --from-file=./cert.key --from-file=./ca.pem
```
Then, use the following parameters:
@@ -458,7 +453,7 @@ To restart the cluster you need to check the state in which it is after being st
First you need to get the name of the persistent volume claims (pvc), for example:
```bash
```console
$ kubectl get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
data-my-galera-mariadb-galera-0 Bound pvc-a496aded-f604-4a2d-b934-174907c4d235 8Gi RWO gp2 25h
@@ -468,8 +463,8 @@ data-my-galera-mariadb-galera-2 Bound pvc-61644bc9-2d7d-4e84-bf32-35e59d909
The following command will print the content of `grastate.dat` for the persistent volume claim `data-my-galera-mariadb-galera-2`. This needs to be run for each of the pvc. You will need to change this name accordingly with yours for each PVC.
```bash
kubectl run -i --rm --tty volpod --overrides='
```console
$ kubectl run -i --rm --tty volpod --overrides='
{
"apiVersion": "v1",
"kind": "Pod",
@@ -516,8 +511,8 @@ There are two possible scenarios:
In this case you will need the node number `N` and run:
```bash
helm install my-release my-repo/mariadb-galera \
```console
$ helm install my-release my-repo/mariadb-galera \
--set rootUser.password=XXXX \
--set galera.mariabackup.password=YYYY \
--set galera.bootstrap.forceBootstrap=true \
@@ -529,8 +524,8 @@ helm install my-release my-repo/mariadb-galera \
In this case the cluster was not stopped cleanly and you need to pick one to force the bootstrap from. The one to be chosen in the one with the highest `seqno` in `/bitnami/mariadb/data/grastate.dat`. The following example shows how to force bootstrap from node 3.
```bash
helm install my-release my-repo/mariadb-galera \
```console
$ helm install my-release my-repo/mariadb-galera \
--set rootUser.password=XXXX \
--set galera.mariabackup.password=YYYY \
--set galera.bootstrap.forceBootstrap=true \
@@ -544,7 +539,7 @@ helm install my-release my-repo/mariadb-galera \
After you have started the cluster by forcing the bootstraping on one of the nodes, you will need to remove the forcing so the node can restart with normality.
```
helm upgrade my-release my-repo/mariadb-galera \
$ helm upgrade my-release my-repo/mariadb-galera \
--set rootUser.password=XXXX \
--set galera.mariabackup.password=YYYY \
--set podManagementPolicy=Parallel
@@ -570,7 +565,7 @@ Find more information about how to deal with common errors related to Bitnami's
It's necessary to specify the existing passwords while performing a upgrade to ensure the secrets are not updated with invalid randomly generated passwords. Remember to specify the existing values of the `rootUser.password`, `db.password` and `galera.mariabackup.password` parameters when upgrading the chart:
```bash
```console
$ helm upgrade my-release my-repo/mariadb-galera \
--set rootUser.password=[ROOT_PASSWORD] \
--set db.password=[MARIADB_PASSWORD] \
@@ -657,4 +652,4 @@ Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
limitations under the License.
bitnami/mariadb/README.md
+9 -8
View File
@@ -7,10 +7,10 @@ MariaDB is an open source, community-developed SQL database server that is widel
[Overview of MariaDB](https://mariadb.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
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/mariadb
```
@@ -33,7 +33,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/mariadb
```
@@ -45,7 +46,7 @@ The command deploys MariaDB on the Kubernetes cluster in the default configurati
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -383,7 +384,7 @@ The above parameters map to the env variables defined in [bitnami/mariadb](https
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set auth.rootPassword=secretpassword,auth.database=app_database \
my-repo/mariadb
@@ -395,7 +396,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
```console
$ helm install my-release -f values.yaml my-repo/mariadb
```
@@ -455,7 +456,7 @@ Find more information about how to deal with common errors related to Bitnami's
It's necessary to set the `auth.rootPassword` parameter when upgrading for readiness/liveness probes to work properly. When you install this chart for the first time, some notes will be displayed providing the credentials you must use under the 'Administrator credentials' section. Please note down the password and run the command below to upgrade your chart:
```bash
```console
$ helm upgrade my-release my-repo/mariadb --set auth.rootPassword=[ROOT_PASSWORD]
```
@@ -512,7 +513,7 @@ Backwards compatibility is not guaranteed. To upgrade to `8.0.0`, install a new
- Create a backup of the database, and restore it on the new release using tools such as [mysqldump](https://mariadb.com/kb/en/mysqldump/).
- Reuse the PVC used to hold the master data on your previous release. To do so, use the `primary.persistence.existingClaim` parameter. The following example assumes that the release name is `mariadb`:
```bash
```console
$ helm install mariadb my-repo/mariadb --set auth.rootPassword=[ROOT_PASSWORD] --set primary.persistence.existingClaim=[EXISTING_PVC]
```
bitnami/mastodon/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ Mastodon is self-hosted social network server based on ActivityPub. Written in R
[Overview of Mastodon](https://joinmastodon.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
```console
@@ -36,7 +36,8 @@ 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 my-release my-repo/mastodon
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/mastodon
```
The command deploys Mastodon on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +49,7 @@ The command deploys Mastodon on the Kubernetes cluster in the default configurat
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -538,7 +539,7 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set adminUsername=admin \
--set adminPassword=password \
my-repo/mastodon
@@ -551,7 +552,7 @@ The above command sets the mastodon 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 my-release -f values.yaml my-repo/mastodon
$ helm install my-release -f values.yaml my-repo/mastodon
```
> **Tip**: You can use the default [values.yaml](values.yaml)
bitnami/matomo/README.md
+4 -3
View File
@@ -7,7 +7,7 @@ Matomo, formerly known as Piwik, is a real time web analytics program. It provid
[Overview of Matomo](https://matomo.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
```console
@@ -35,6 +35,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 repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/matomo
```
@@ -370,7 +371,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
1. Create the PersistentVolumeClaim
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/matomo
```
@@ -386,7 +387,7 @@ $ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/matom
1. The specified `hostPath` directory must already exist (create one if it does not).
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/matomo
```
bitnami/mediawiki/README.md
+7 -6
View File
@@ -7,7 +7,7 @@ MediaWiki is the free and open source wiki software that powers Wikipedia. Used
[Overview of MediaWiki](http://www.mediawiki.org/wiki/MediaWiki)
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
```console
@@ -35,6 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/mediawiki
```
@@ -450,11 +451,11 @@ To upgrade to `11.0.0`, it should be done reusing the PVCs used to hold both the
Obtain the credentials and the names of the PVCs used to hold both the MariaDB and Mediawiki data on your current release:
```console
export MEDIAWIKI_HOST=$(kubectl get svc --namespace default mediawiki --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
export MEDIAWIKI_PASSWORD=$(kubectl get secret --namespace default mediawiki -o jsonpath="{.data.mediawiki-password}" | base64 -d)
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default mediawiki-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default mediawiki-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=mediawiki -o jsonpath="{.items[0].metadata.name}")
$ export MEDIAWIKI_HOST=$(kubectl get svc --namespace default mediawiki --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
$ export MEDIAWIKI_PASSWORD=$(kubectl get secret --namespace default mediawiki -o jsonpath="{.data.mediawiki-password}" | base64 -d)
$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default mediawiki-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default mediawiki-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
$ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=mediawiki -o jsonpath="{.items[0].metadata.name}")
```
Delete the Mediawiki deployment and delete the MariaDB statefulset. Notice the option `--cascade=false` in the latter:
bitnami/memcached/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ Memcached is an high-performance, distributed memory object caching system, gene
[Overview of Memcached](http://memcached.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
```console
bitnami/metallb/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ MetalLB is a load-balancer implementation for bare metal Kubernetes clusters, us
[Overview of MetalLB](https://metallb.universe.tf/)
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
```console
bitnami/metrics-server/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ Metrics Server aggregates resource usage data, such as container CPU and memory
[Overview of Metrics Server](https://github.com/kubernetes-incubator/metrics-server)
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
```console
bitnami/minio/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ MinIO(R) is an object storage server, compatible with Amazon S3 cloud storage se
[Overview of Bitnami Object Storage based on MinIO&reg;](https://min.io/)
Disclaimer: All software products, projects and company names are trademark(TM) or registered(R) trademarks of their respective holders, and use of them does not imply any affiliation or endorsement. This software is licensed to you subject to one or more open source licenses and VMware provides the software on an AS-IS basis. MinIO(R) is a registered trademark of the MinIO Inc. in the US and other countries. Bitnami is not affiliated, associated, authorized, endorsed by, or in any way officially connected with MinIO Inc. MinIO(R) is licensed under GNU AGPL v3.0.
## TL;DR
```console
bitnami/mongodb-sharded/README.md
+8 -7
View File
@@ -7,10 +7,10 @@ MongoDB(R) is an open source NoSQL database that uses JSON for data storage. Mon
[Overview of MongoDB&reg; Sharded](http://www.mongodb.org)
Disclaimer: The respective trademarks mentioned in the offering are owned by the respective companies. We do not provide a commercial license for any of these products. This listing has an open-source license. MongoDB(R) is run and maintained by MongoDB, which is a completely separate project from Bitnami.
## TL;DR
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/mongodb-sharded
```
@@ -36,7 +36,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/mongodb-sharded
```
@@ -48,7 +49,7 @@ The command deploys MongoDB&reg; on the Kubernetes cluster in the default config
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -521,7 +522,7 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set shards=4,configsvr.replicaCount=3,shardsvr.dataNode.replicaCount=2 \
my-repo/mongodb-sharded
@@ -531,7 +532,7 @@ The above command sets the number of shards to 4, the number of replicas for the
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/mongodb-sharded
```
@@ -637,7 +638,7 @@ Find more information about how to deal with common errors related to Bitnami's
If authentication is enabled, it's necessary to set the `auth.rootPassword` and `auth.replicaSetKey` when upgrading for readiness/liveness probes to work properly. When you install this chart for the first time, some notes will be displayed providing the credentials you must use. Please note down the password, and run the command below to upgrade your chart:
```bash
```console
$ helm upgrade my-release my-repo/mongodb-sharded --set auth.rootPassword=[PASSWORD] (--set auth.replicaSetKey=[auth.replicaSetKey])
```
bitnami/mongodb/README.md
+8 -7
View File
@@ -7,10 +7,10 @@ MongoDB(R) is a relational open source NoSQL database. Easy to use, it stores da
[Overview of MongoDB&reg;](http://www.mongodb.org)
Disclaimer: The respective trademarks mentioned in the offering are owned by the respective companies. We do not provide a commercial license for any of these products. This listing has an open-source license. MongoDB(R) is run and maintained by MongoDB, which is a completely separate project from Bitnami.
## TL;DR
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/mongodb
```
@@ -31,7 +31,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/mongodb
```
@@ -43,7 +44,7 @@ The command deploys MongoDB(&reg;) on the Kubernetes cluster in the default conf
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -563,7 +564,7 @@ Refer to the [chart documentation for more information on each of these architec
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set auth.rootPassword=secretpassword,auth.username=my-user,auth.password=my-password,auth.database=my-database \
my-repo/mongodb
@@ -575,7 +576,7 @@ The above command sets the MongoDB(&reg;) `root` account password to `secretpass
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/mongodb
```
@@ -659,7 +660,7 @@ Find more information about how to deal with common errors related to Bitnami's
If authentication is enabled, it's necessary to set the `auth.rootPassword` (also `auth.replicaSetKey` when using a replicaset architecture) when upgrading for readiness/liveness probes to work properly. When you install this chart for the first time, some notes will be displayed providing the credentials you must use under the 'Credentials' section. Please note down the password, and run the command below to upgrade your chart:
```bash
```console
$ helm upgrade my-release my-repo/mongodb --set auth.rootPassword=[PASSWORD] (--set auth.replicaSetKey=[REPLICASETKEY])
```
bitnami/moodle/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ Moodle(TM) LMS is an open source online Learning Management System widely used a
[Overview of Bitnami LMS powered by Moodle&trade; LMS](http://moodle.org/)
Disclaimer: The respective trademarks mentioned in the offering are owned by the respective companies. We do not provide commercial license of any of these products. This listing has an open source license. Moodle(TM) LMS is run and maintained by Moodle HQ, that is a completely and separate project from Bitnami.
## TL;DR
```console
@@ -35,6 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/moodle
```
@@ -454,10 +455,10 @@ To upgrade to `9.0.0`, it should be done reusing the PVCs used to hold both the
Obtain the credentials and the names of the PVCs used to hold both the MariaDB and Moodle&trade; data on your current release:
```console
export MOODLE_PASSWORD=$(kubectl get secret --namespace default moodle -o jsonpath="{.data.moodle-password}" | base64 -d)
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default moodle-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default moodle-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=moodle -o jsonpath="{.items[0].metadata.name}")
$ export MOODLE_PASSWORD=$(kubectl get secret --namespace default moodle -o jsonpath="{.data.moodle-password}" | base64 -d)
$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default moodle-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default moodle-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
$ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=moodle -o jsonpath="{.items[0].metadata.name}")
```
Upgrade your release (maintaining the version) disabling MariaDB and scaling Moodle&trade; replicas to 0:
bitnami/mxnet/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ Apache MXNet (Incubating) is a flexible and efficient library for deep learning
[Overview of Apache MXNet (Incubating)](https://mxnet.incubator.apache.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
```console
bitnami/mysql/README.md
+8 -8
View File
@@ -7,10 +7,10 @@ MySQL is a fast, reliable, scalable, and easy to use open source relational data
[Overview of MySQL](http://www.mysql.com)
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
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/mysql
```
@@ -31,7 +31,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/mysql
```
@@ -44,7 +44,7 @@ These commands deploy MySQL on the Kubernetes cluster in the default configurati
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -369,7 +369,7 @@ The above parameters map to the env variables defined in [bitnami/mysql](https:/
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set auth.rootPassword=secretpassword,auth.database=app_database \
my-repo/mysql
@@ -381,7 +381,7 @@ The above command sets the MySQL `root` account password to `secretpassword`. Ad
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/mysql
```
@@ -472,7 +472,7 @@ Find more information about how to deal with common errors related to Bitnami's
It's necessary to set the `auth.rootPassword` parameter when upgrading for readiness/liveness probes to work properly. When you install this chart for the first time, some notes will be displayed providing the credentials you must use under the 'Administrator credentials' section. Please note down the password and run the command below to upgrade your chart:
```bash
```console
$ helm upgrade my-release my-repo/mysql --set auth.rootPassword=[ROOT_PASSWORD]
```
@@ -515,7 +515,7 @@ Consequences:
- Create a backup of the database, and restore it on the new release using tools such as [mysqldump](https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html).
- Reuse the PVC used to hold the master data on your previous release. To do so, use the `primary.persistence.existingClaim` parameter. The following example assumes that the release name is `mysql`:
```bash
```console
$ helm install mysql my-repo/mysql --set auth.rootPassword=[ROOT_PASSWORD] --set primary.persistence.existingClaim=[EXISTING_PVC]
```
bitnami/nats/README.md
+9 -8
View File
@@ -7,10 +7,10 @@ NATS is an open source, lightweight and high-performance messaging system. It is
[Overview of NATS](https://nats.io/)
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
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/nats
```
@@ -30,7 +30,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/nats
```
@@ -42,7 +43,7 @@ The command deploys NATS on the Kubernetes cluster in the default configuration.
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -266,7 +267,7 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set auth.enabled=true,auth.user=my-user,auth.password=T0pS3cr3t \
my-repo/nats
@@ -278,7 +279,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
```console
$ helm install my-release -f values.yaml my-repo/nats
```
@@ -331,8 +332,8 @@ Find more information about how to deal with common errors related to Bitnami's
NATS version 2.0.0 has renamed the server binary filename from `gnatsd` to `nats-server`. Therefore, the default values has been changed in the chart,
however, it is still possible to use the chart to deploy NATS version 1.x.x using the `natsFilename` property.
```bash
helm install nats-v1 --set natsFilename=gnatsd --set image.tag=1.4.1 my-repo/nats
```console
$ helm install nats-v1 --set natsFilename=gnatsd --set image.tag=1.4.1 my-repo/nats
```
### To 7.0.0
bitnami/nginx-ingress-controller/README.md
+6 -6
View File
@@ -7,10 +7,10 @@ NGINX Ingress Controller is an Ingress controller that manages external access t
[Overview of NGINX Ingress Controller](https://kubernetes.github.io/ingress-nginx/)
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
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/nginx-ingress-controller
```
@@ -32,7 +32,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/nginx-ingress-controller
```
@@ -45,7 +45,7 @@ These commands deploy nginx-ingress-controller on the Kubernetes cluster in the
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -337,7 +337,7 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set image.pullPolicy=Always \
my-repo/nginx-ingress-controller
@@ -347,7 +347,7 @@ The above command sets the `image.pullPolicy` to `Always`.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/nginx-ingress-controller
```
bitnami/nginx/README.md
+6 -6
View File
@@ -7,10 +7,10 @@ NGINX Open Source is a web server that can be also used as a reverse proxy, load
[Overview of NGINX Open Source](http://nginx.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
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/nginx
```
@@ -32,7 +32,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/nginx
```
@@ -45,7 +45,7 @@ These commands deploy NGINX Open Source on the Kubernetes cluster in the default
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -281,7 +281,7 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set imagePullPolicy=Always \
my-repo/nginx
@@ -291,7 +291,7 @@ The above command sets the `imagePullPolicy` to `Always`.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/nginx
```
bitnami/node-exporter/README.md
+8 -13
View File
@@ -7,10 +7,10 @@ Prometheus exporter for hardware and OS metrics exposed by UNIX kernels, with pl
[Overview of Node Exporter](https://prometheus.io/)
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
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/node-exporter
```
@@ -28,15 +28,10 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
## Installing the Chart
Add the `bitnami` charts repo to Helm:
```bash
$ helm repo add my-repo https://charts.bitnami.com/bitnami
```
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/node-exporter
```
@@ -46,7 +41,7 @@ The command deploys Node Exporter on the Kubernetes cluster in the default confi
To uninstall/delete the `my-release` release:
```bash
```console
$ helm delete my-release
```
@@ -181,13 +176,13 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example the following command sets the `minReadySeconds` of the Node Exporter Pods to `120` seconds.
```bash
```console
$ helm install my-release --set minReadySeconds=120 my-repo/node-exporter
```
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/node-exporter
```
@@ -213,7 +208,7 @@ Find more information about how to deal with common errors related to Bitnami's
## Upgrading
```bash
```console
$ helm upgrade my-release my-repo/node-exporter
```
bitnami/oauth2-proxy/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ A reverse proxy and static file server that provides authentication using Provid
[Overview of OAuth2 Proxy](https://github.com/oauth2-proxy/oauth2-proxy)
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
```console
@@ -35,7 +35,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm install my-release my-repo/oauth2-proxy
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/oauth2-proxy
```
The command deploys OAuth2 Proxy on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -47,7 +48,7 @@ The command deploys OAuth2 Proxy on the Kubernetes cluster in the default config
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -255,7 +256,7 @@ The above parameters map to the env variables defined in [bitnami/oauth2-proxy](
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set replicaCount=2 \
my-repo/oauth2-proxy
```
@@ -267,7 +268,7 @@ The above command increase the default number of replicas.
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/oauth2-proxy
$ helm install my-release -f values.yaml my-repo/oauth2-proxy
```
> **Tip**: You can use the default [values.yaml](values.yaml)
bitnami/odoo/README.md
+2 -1
View File
@@ -7,7 +7,7 @@ Odoo is an open source ERP and CRM platform, formerly known as OpenERP, that can
[Overview of Odoo](https://www.odoo.com/)
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
```console
@@ -35,6 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/odoo
```
bitnami/opencart/README.md
+9 -8
View File
@@ -7,7 +7,7 @@ OpenCart is free open source ecommerce platform for online merchants. OpenCart p
[Overview of OpenCart](http://www.opencart.com)
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
```console
@@ -35,6 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/opencart
```
@@ -308,7 +309,7 @@ The above parameters map to the env variables defined in [bitnami/opencart](http
>
> To reserve a public IP address on GKE:
>
> ```bash
> ```console
> $ gcloud compute addresses create opencart-public-ip
> ```
>
@@ -379,7 +380,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
1. Create the PersistentVolumeClaim
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/prestashop
```
@@ -395,7 +396,7 @@ $ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/prest
1. The specified `hostPath` directory must already exist (create one if it does not).
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/prestashop
```
@@ -464,10 +465,10 @@ This release includes several breaking changes which are listed below. To upgrad
Obtain the credentials and the name of the PVC used to hold the MariaDB data on your current release:
```console
export OPENCART_PASSWORD=$(kubectl get secret --namespace default opencart -o jsonpath="{.data.opencart-password}" | base64 -d)
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default opencart-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default opencart-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
export MARIADB_PVC=$(kubectl get pvc -l app.kubernetes.io/instance=opencart,app.kubernetes.io/name=mariadb,app.kubernetes.io/component=primary -o jsonpath="{.items[0].metadata.name}")
$ export OPENCART_PASSWORD=$(kubectl get secret --namespace default opencart -o jsonpath="{.data.opencart-password}" | base64 -d)
$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default opencart-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default opencart-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
$ export MARIADB_PVC=$(kubectl get pvc -l app.kubernetes.io/instance=opencart,app.kubernetes.io/name=mariadb,app.kubernetes.io/component=primary -o jsonpath="{.items[0].metadata.name}")
```
#### New volume mount locations
bitnami/osclass/README.md
+7 -6
View File
@@ -7,7 +7,7 @@ Osclass allows you to easily create a classifieds site without any technical kno
[Overview of Osclass](https://osclass-classifieds.com)
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
```console
@@ -35,6 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/osclass
```
@@ -512,11 +513,11 @@ To upgrade to `8.0.0`, it should be done reusing the PVCs used to hold both the
Obtain the credentials and the names of the PVCs used to hold both the MariaDB and Osclass data on your current release:
```console
export OSCLASS_HOST=$(kubectl get svc --namespace default osclass --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
export OSCLASS_PASSWORD=$(kubectl get secret --namespace default osclass -o jsonpath="{.data.osclass-password}" | base64 -d)
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default osclass-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default osclass-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=osclass -o jsonpath="{.items[0].metadata.name}")
$ export OSCLASS_HOST=$(kubectl get svc --namespace default osclass --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
$ export OSCLASS_PASSWORD=$(kubectl get secret --namespace default osclass -o jsonpath="{.data.osclass-password}" | base64 -d)
$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default osclass-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default osclass-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
$ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=osclass -o jsonpath="{.items[0].metadata.name}")
```
Delete the Osclass deployment and delete the MariaDB statefulset. Notice the option `--cascade=false` in the latter:
bitnami/parse/README.md
+3 -2
View File
@@ -7,7 +7,7 @@ Parse is a platform that enables users to add a scalable and powerful backend to
[Overview of Parse Server](http://parseplatform.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
```console
@@ -33,6 +33,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/parse
```
@@ -329,7 +330,7 @@ The above parameters map to the env variables defined in [bitnami/parse](https:/
>
> To reserve a public IP address on GKE:
>
> ```bash
> ```console
> $ gcloud compute addresses create parse-public-ip
> ```
>
bitnami/phpbb/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ phpBB is a popular bulletin board that features robust messaging capabilities su
[Overview of phpBB](http://www.phpbb.com)
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
```console
@@ -35,6 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/phpbb
```
@@ -418,10 +419,10 @@ To upgrade to `9.0.0`, it should be done reusing the PVCs used to hold both the
Obtain the credentials and the names of the PVCs used to hold both the MariaDB and phpBB data on your current release:
```console
export PHPBB_PASSWORD=$(kubectl get secret --namespace default phpbb -o jsonpath="{.data.phpbb-password}" | base64 -d)
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default phpbb-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default phpbb-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=phpbb -o jsonpath="{.items[0].metadata.name}")
$ export PHPBB_PASSWORD=$(kubectl get secret --namespace default phpbb -o jsonpath="{.data.phpbb-password}" | base64 -d)
$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default phpbb-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default phpbb-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
$ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=phpbb -o jsonpath="{.items[0].metadata.name}")
```
Upgrade your release (maintaining the version) disabling MariaDB and scaling phpBB replicas to 0:
bitnami/phpmyadmin/README.md
+5 -4
View File
@@ -7,7 +7,7 @@ phpMyAdmin is a free software tool written in PHP, intended to handle the admini
[Overview of phpMyAdmin](https://www.phpmyadmin.net/)
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
```console
@@ -33,6 +33,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/phpmyadmin
```
@@ -474,9 +475,9 @@ To upgrade to `7.0.0`, it should be done reusing the PVCs used to hold both the
Obtain the credentials and the names of the PVCs used to hold both the MariaDB and phpMyAdmin data on your current release:
```console
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default phpmyadmin-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default phpmyadmin-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=phpmyadmin -o jsonpath="{.items[0].metadata.name}")
$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default phpmyadmin-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default phpmyadmin-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
$ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=phpmyadmin -o jsonpath="{.items[0].metadata.name}")
```
Delete the phpMyAdmin deployment and delete the MariaDB statefulsets:
bitnami/pinniped/README.md
+6 -5
View File
@@ -7,7 +7,7 @@ Pinniped is an identity service provider for Kubernetes. It supplies a consisten
[Overview of Pinniped](https://pinniped.dev/)
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
```console
@@ -35,7 +35,8 @@ 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 my-release my-repo/pinniped
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/pinniped
```
The command deploys pinniped on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -47,7 +48,7 @@ The command deploys pinniped on the Kubernetes cluster in the default configurat
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -323,7 +324,7 @@ The above parameters map to the env variables defined in [bitnami/pinniped](http
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set supervisor.enabled=false \
my-repo/pinniped
```
@@ -333,7 +334,7 @@ The above command sets disables the supervisor compoment deployment.
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/pinniped
$ helm install my-release -f values.yaml my-repo/pinniped
```
> **Tip**: You can use the default [values.yaml](values.yaml)
bitnami/postgresql-ha/README.md
+16 -16
View File
@@ -7,7 +7,7 @@ This PostgreSQL cluster solution includes the PostgreSQL replication manager, an
[Overview of PostgreSQL HA](https://www.postgresql.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
```console
@@ -33,7 +33,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
## Installing the Chart
Install the PostgreSQL HA helm chart with a release name `my-release`:
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
@@ -562,7 +562,7 @@ LDAP support can be enabled in the chart by specifying the `ldap.` parameters wh
For example:
```bash
```
ldap.enabled="true"
ldap.uri="ldap://my_ldap_server"
ldap.base="dc=example\,dc=org"
@@ -608,7 +608,7 @@ The allowed extensions are `.sh`, `.sql` and `.sql.gz` in the **postgresql** con
In more complex scenarios, we may have the following tree of dependencies
```bash
```
+--------------+
| |
+------------+ Chart 1 +-----------+
@@ -628,7 +628,7 @@ In more complex scenarios, we may have the following tree of dependencies
The three charts below depend on the parent chart Chart 1. However, subcharts 1 and 2 may need to connect to PostgreSQL HA as well. In order to do so, subcharts 1 and 2 need to know the PostgreSQL HA credentials, so one option for deploying could be deploy Chart 1 with the following parameters:
```bash
```
postgresql.postgresqlPassword=testtest
subchart1.postgresql.postgresqlPassword=testtest
subchart2.postgresql.postgresqlPassword=testtest
@@ -639,7 +639,7 @@ subchart2.postgresql.postgresqlDatabase=db1
If the number of dependent sub-charts increases, installing the chart with parameters can become increasingly difficult. An alternative would be to set the credentials using global variables as follows:
```bash
```
global.postgresql.postgresqlPassword=testtest
global.postgresql.postgresqlDatabase=db1
```
@@ -665,7 +665,7 @@ Find more information about how to deal with common errors related to Bitnami's
It's necessary to specify the existing passwords while performing a upgrade to ensure the secrets are not updated with invalid randomly generated passwords. Remember to specify the existing values of the `postgresql.password` and `postgresql.repmgrPassword` parameters when upgrading the chart:
```bash
```console
$ helm upgrade my-release my-repo/postgresql-ha \
--set postgresql.password=[POSTGRES_PASSWORD] \
--set postgresql.repmgrPassword=[REPMGR_PASSWORD]
@@ -707,7 +707,7 @@ A new major version of repmgr (5.3) was included. To upgrade to this major versi
- Reduce your PostgreSQL setup to one replica (primary node) and upgrade to `8.0.0`, enabling the repmgr extension upgrade:
```bash
```console
$ helm upgrade my-release --version 8.0.0 my-repo/postgresql-ha \
--set postgresql.password=[POSTGRESQL_PASSWORD] \
--set postgresql.repmgrPassword=[REPMGR_PASSWORD] \
@@ -717,7 +717,7 @@ $ helm upgrade my-release --version 8.0.0 my-repo/postgresql-ha \
- Scale your PostgreSQL setup to the original number of replicas:
```bash
```console
$ helm upgrade my-release --version 8.0.0 my-repo/postgresql-ha \
--set postgresql.password=[POSTGRESQL_PASSWORD] \
--set postgresql.repmgrPassword=[REPMGR_PASSWORD] \
@@ -760,7 +760,7 @@ A new version of repmgr (5.2.0) was included. To upgrade to this version, it's
- Reduce your PostgreSQL setup to one replica (primary node) and upgrade to `5.2.0`, enabling the repmgr extension upgrade:
```bash
```console
$ helm upgrade my-release --version 5.2.0 my-repo/postgresql-ha \
--set postgresql.password=[POSTGRESQL_PASSWORD] \
--set postgresql.repmgrPassword=[REPMGR_PASSWORD] \
@@ -770,7 +770,7 @@ $ helm upgrade my-release --version 5.2.0 my-repo/postgresql-ha \
- Scale your PostgreSQL setup to the original number of replicas:
```bash
```console
$ helm upgrade my-release --version 5.2.0 my-repo/postgresql-ha \
--set postgresql.password=[POSTGRESQL_PASSWORD] \
--set postgresql.repmgrPassword=[REPMGR_PASSWORD] \
@@ -786,7 +786,7 @@ This version is next major version to v3.x.y
- To upgrade to this version you will need to delete the deployment, keep the PVCs and launch a new deployment keeping the deployment name.
```bash
```console
$ # e.g. Previous deployment v3.9.1
$ helm install my-release \
--set postgresql.password=[POSTGRESQL_PASSWORD] \
@@ -814,7 +814,7 @@ A new major version of repmgr (5.1.0) was included. To upgrade to this major ver
- Reduce your PostgreSQL setup to one replica (primary node) and upgrade to `3.0.0`, enabling the repmgr extension upgrade:
```bash
```console
$ helm upgrade my-release --version 3.0.0 my-repo/postgresql-ha \
--set postgresql.password=[POSTGRESQL_PASSWORD] \
--set postgresql.repmgrPassword=[REPMGR_PASSWORD] \
@@ -824,7 +824,7 @@ $ helm upgrade my-release --version 3.0.0 my-repo/postgresql-ha \
- Scale your PostgreSQL setup to the original number of replicas:
```bash
```console
$ helm upgrade my-release --version 3.0.0 my-repo/postgresql-ha \
--set postgresql.password=[POSTGRESQL_PASSWORD] \
--set postgresql.repmgrPassword=[REPMGR_PASSWORD] \
@@ -848,7 +848,7 @@ A new major version of repmgr (5.0.0) was included. To upgrade to this major ver
- Reduce your PostgreSQL setup to one replica (primary node) and upgrade to `1.0.0`, enabling the repmgr extension upgrade:
```bash
```console
$ helm upgrade my-release --version 1.0.0 my-repo/postgresql-ha \
--set postgresql.password=[POSTGRESQL_PASSWORD] \
--set postgresql.repmgrPassword=[REPMGR_PASSWORD] \
@@ -858,7 +858,7 @@ $ helm upgrade my-release --version 1.0.0 my-repo/postgresql-ha \
- Scale your PostgreSQL setup to the original number of replicas:
```bash
```console
$ helm upgrade my-release --version 1.0.0 my-repo/postgresql-ha \
--set postgresql.password=[POSTGRESQL_PASSWORD] \
--set postgresql.repmgrPassword=[REPMGR_PASSWORD] \
bitnami/postgresql/README.md
+15 -14
View File
@@ -7,12 +7,12 @@ PostgreSQL (Postgres) is an open source object-relational database known for rel
[Overview of PostgreSQL](http://www.postgresql.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
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/postgresql
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/postgresql
```
## Introduction
@@ -33,8 +33,9 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
helm install my-release my-repo/postgresql
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/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.
@@ -46,15 +47,15 @@ The command deploys PostgreSQL on the Kubernetes cluster in the default configur
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components but PVC's associated with the chart and deletes the release.
To delete the PVC's associated with `my-release`:
```bash
kubectl delete pvc -l release=my-release
```console
$ kubectl delete pvc -l release=my-release
```
> **Note**: Deleting the PVC's will delete postgresql data as well. Please be cautious before doing it.
@@ -466,7 +467,7 @@ kubectl delete pvc -l release=my-release
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set auth.postgresPassword=secretpassword
my-repo/postgresql
@@ -480,8 +481,8 @@ 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,
```bash
helm install my-release -f values.yaml my-repo/postgresql
```console
$ helm install my-release -f values.yaml my-repo/postgresql
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -639,8 +640,8 @@ To enable network policy for PostgreSQL, install [a networking plugin that imple
For Kubernetes v1.5 & v1.6, you must also turn on NetworkPolicy by setting the DefaultDeny namespace annotation. Note: this will enforce policy for _all_ pods in the namespace:
```bash
kubectl annotate namespace default "net.beta.kubernetes.io/network-policy={\"ingress\":{\"isolation\":\"DefaultDeny\"}}"
```console
$ kubectl annotate namespace default "net.beta.kubernetes.io/network-policy={\"ingress\":{\"isolation\":\"DefaultDeny\"}}"
```
With NetworkPolicy enabled, traffic will be limited to just port 5432.
bitnami/prestashop/README.md
+9 -8
View File
@@ -7,7 +7,7 @@ PrestaShop is a powerful open source eCommerce platform used by over 250,000 onl
[Overview of PrestaShop](http://www.prestashop.com)
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
```console
@@ -35,6 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/prestashop
```
@@ -315,7 +316,7 @@ The above parameters map to the env variables defined in [bitnami/prestashop](ht
>
> To reserve a public IP address on GKE:
>
> ```bash
> ```console
> $ gcloud compute addresses create prestashop-public-ip
> ```
>
@@ -386,7 +387,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
1. Create the PersistentVolumeClaim
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/prestashop
```
@@ -402,7 +403,7 @@ $ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/prest
1. The specified `hostPath` directory must already exist (create one if it does not).
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/prestashop
```
@@ -485,10 +486,10 @@ To upgrade to `11.0.0`, you have two alternatives:
Obtain the credentials and the name of the PVC used to hold the MariaDB data on your current release:
```console
export PRESTASHOP_PASSWORD=$(kubectl get secret --namespace default prestashop -o jsonpath="{.data.prestashop-password}" | base64 -d)
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default prestashop-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default prestashop-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
export MARIADB_PVC=$(kubectl get pvc -l app.kubernetes.io/instance=prestashop,app.kubernetes.io/name=mariadb,app.kubernetes.io/component=primary -o jsonpath="{.items[0].metadata.name}")
$ export PRESTASHOP_PASSWORD=$(kubectl get secret --namespace default prestashop -o jsonpath="{.data.prestashop-password}" | base64 -d)
$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default prestashop-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default prestashop-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
$ export MARIADB_PVC=$(kubectl get pvc -l app.kubernetes.io/instance=prestashop,app.kubernetes.io/name=mariadb,app.kubernetes.io/component=primary -o jsonpath="{.items[0].metadata.name}")
```
Upgrade your release (maintaining the version) disabling MariaDB and scaling Prestashop replicas to 0:
bitnami/pytorch/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ PyTorch is a deep learning platform that accelerates the transition from researc
[Overview of PyTorch](https://pytorch.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
```console
bitnami/rabbitmq-cluster-operator/README.md
+11 -10
View File
@@ -7,7 +7,7 @@ The RabbitMQ Cluster Kubernetes Operator automates provisioning, management, and
[Overview of RabbitMQ Cluster Operator](https://github.com/rabbitmq/cluster-operator)
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
```console
@@ -34,7 +34,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm install my-release my-repo/rabbitmq-cluster-operators
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/rabbitmq-cluster-operators
```
The command deploy the RabbitMQ Cluster Kubernetes Operator on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -46,7 +47,7 @@ The command deploy the RabbitMQ Cluster Kubernetes Operator on the Kubernetes cl
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -397,7 +398,7 @@ The above parameters map to the env variables defined in [bitnami/rabbitmq-clust
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
helm install my-release \
$ helm install my-release \
--set livenessProbe.enabled=false \
my-repo/rabbitmq-cluster-operator
```
@@ -407,7 +408,7 @@ The above command disables the Operator liveness probes.
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/rabbitmq-cluster-operator
$ helm install my-release -f values.yaml my-repo/rabbitmq-cluster-operator
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -478,9 +479,9 @@ In order to upgrade the CRD objects, perform the following steps:
- Execute the following commands (replace the VERSION placeholder):
```console
helm fetch bitnami/rabbitmq-cluster-operator --version VERSION
tar xf rabbitmq-cluster-operator-VERSION.tar.gz
kubectl apply -f rabbitmq-cluster-operator/crds
$ helm fetch bitnami/rabbitmq-cluster-operator --version VERSION
$ tar xf rabbitmq-cluster-operator-VERSION.tar.gz
$ kubectl apply -f rabbitmq-cluster-operator/crds
```
### To 2.0.0
@@ -502,8 +503,8 @@ The CRD was updated according to the latest changes in the upstream project. Tha
You need to manually delete the old CRD before upgrading the release.
```console
kubectl delete crd rabbitmqclusters.rabbitmq.com
helm upgrade my-release my-repo/rabbitmq-cluster-operator
$ kubectl delete crd rabbitmqclusters.rabbitmq.com
$ helm upgrade my-release my-repo/rabbitmq-cluster-operator
```
## License
bitnami/rabbitmq/README.md
+8 -8
View File
@@ -7,10 +7,10 @@ RabbitMQ is an open source general-purpose message broker that is designed for c
[Overview of RabbitMQ](https://www.rabbitmq.com)
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
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/rabbitmq
```
@@ -31,7 +31,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/rabbitmq
```
@@ -44,7 +44,7 @@ The command deploys RabbitMQ on the Kubernetes cluster in the default configurat
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -360,7 +360,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
```console
$ helm install my-release \
--set auth.username=admin,auth.password=secretpassword,auth.erlangCookie=secretcookie \
my-repo/rabbitmq
@@ -372,7 +372,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
```console
$ helm install my-release -f values.yaml my-repo/rabbitmq
```
@@ -543,7 +543,7 @@ The chart mounts a [Persistent Volume](https://kubernetes.io/docs/concepts/stora
1. Create the PersistentVolumeClaim
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/rabbitmq
```
@@ -578,7 +578,7 @@ Find more information about how to deal with common errors related to Bitnami's
It's necessary to set the `auth.password` and `auth.erlangCookie` parameters when upgrading for readiness/liveness probes to work properly. When you install this chart for the first time, some notes will be displayed providing the credentials you must use under the 'Credentials' section. Please note down the password and the cookie, and run the command below to upgrade your chart:
```bash
```console
$ helm upgrade my-release my-repo/rabbitmq --set auth.password=[PASSWORD] --set auth.erlangCookie=[RABBITMQ_ERLANG_COOKIE]
```
bitnami/redis-cluster/README.md
+15 -14
View File
@@ -7,10 +7,10 @@ Redis(R) is an open source, scalable, distributed in-memory cache for applicatio
[Overview of Redis&reg; Cluster](http://redis.io)
Disclaimer: Redis is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd. Any use by Bitnami is for referential purposes only and does not indicate any sponsorship, endorsement, or affiliation between Redis Ltd.
## TL;DR
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/redis-cluster
```
@@ -43,7 +43,8 @@ The main features of each chart are the following:
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/redis-cluster
```
@@ -52,7 +53,7 @@ The command deploys Redis&reg; on the Kubernetes cluster in the default configur
NOTE: if you get a timeout error waiting for the hook to complete increase the default timeout (300s) to a higher one, for example:
```
helm install --timeout 600s myrelease my-repo/redis-cluster
$ helm install --timeout 600s myrelease my-repo/redis-cluster
```
> **Tip**: List all releases using `helm list`
@@ -61,7 +62,7 @@ helm install --timeout 600s myrelease my-repo/redis-cluster
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -343,7 +344,7 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set password=secretpassword \
my-repo/redis-cluster
@@ -355,7 +356,7 @@ The above command sets the Redis&reg; 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
```console
$ helm install my-release -f values.yaml my-repo/redis-cluster
```
@@ -406,7 +407,7 @@ There is a job that will be executed using a `post-upgrade` hook that will allow
The following will be an example to add one more node:
```
helm upgrade --timeout 600s <release> --set "password=${REDIS_PASSWORD},cluster.nodes=7,cluster.update.addNodes=true,cluster.update.currentNumberOfNodes=6" my-repo/redis-cluster
$ helm upgrade --timeout 600s <release> --set "password=${REDIS_PASSWORD},cluster.nodes=7,cluster.update.addNodes=true,cluster.update.currentNumberOfNodes=6" my-repo/redis-cluster
```
Where `REDIS_PASSWORD` is the password obtained with the command that appears after the first installation of the Helm Chart.
@@ -417,7 +418,7 @@ The cluster will continue up while restarting pods one by one as the quorum is n
If you are using external access, to add a new node you will need to perform two upgrades. First upgrade the release to add a new Redis&reg; node and to get a LoadBalancerIP service. For example:
```
helm upgrade <release> --set "password=${REDIS_PASSWORD},cluster.externalAccess.enabled=true,cluster.externalAccess.service.type=LoadBalancer,cluster.externalAccess.service.loadBalancerIP[0]=<loadBalancerip-0>,cluster.externalAccess.service.loadBalancerIP[1]=<loadbalanacerip-1>,cluster.externalAccess.service.loadBalancerIP[2]=<loadbalancerip-2>,cluster.externalAccess.service.loadBalancerIP[3]=<loadbalancerip-3>,cluster.externalAccess.service.loadBalancerIP[4]=<loadbalancerip-4>,cluster.externalAccess.service.loadBalancerIP[5]=<loadbalancerip-5>,cluster.externalAccess.service.loadBalancerIP[6]=,cluster.nodes=7,cluster.init=false my-repo/redis-cluster
$ 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 my-repo/redis-cluster
```
> Important here to provide the loadBalancerIP parameters for the new nodes empty to not get an index error.
@@ -428,7 +429,7 @@ At this point, you will have a new Redis&reg; Pod that will remain in `crashLoop
Now, wait until the cluster provides the new LoadBalancerIP for the new service and perform the second upgrade:
```
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]=<loadbalancerip-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]=<loadbalancerip-6>,cluster.nodes=7,cluster.init=false,cluster.update.addNodes=true,cluster.update.newExternalIPs[0]=<load-balancerip-6>" my-repo/redis-cluster
$ 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]=<loadbalancerip-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]=<loadbalancerip-6>,cluster.nodes=7,cluster.init=false,cluster.update.addNodes=true,cluster.update.newExternalIPs[0]=<load-balancerip-6>" my-repo/redis-cluster
```
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.
@@ -442,7 +443,7 @@ To scale down the Redis&reg; Cluster, follow these steps:
First perform a normal upgrade setting the `cluster.nodes` value to the desired number of nodes. It should not be less than `6` and the difference between current number of nodes and the desired should be less or equal to `cluster.replicas` to avoid removing master node an its slaves at the same time. Also it is needed to provide the password using the `password`. For example, having more than 6 nodes, to scale down the cluster to 6 nodes:
```
helm upgrade --timeout 600s <release> --set "password=${REDIS_PASSWORD},cluster.nodes=6" .
$ helm upgrade --timeout 600s <release> --set "password=${REDIS_PASSWORD},cluster.nodes=6" .
```
The cluster will continue working during the update as long as the quorum is not lost.
@@ -500,7 +501,7 @@ For example:
First, create the secret with the certificates files:
```console
kubectl create secret generic certificates-tls-secret --from-file=./cert.pem --from-file=./cert.key --from-file=./ca.pem
$ kubectl create secret generic certificates-tls-secret --from-file=./cert.pem --from-file=./cert.key --from-file=./ca.pem
```
Then, use the following parameters:
@@ -634,8 +635,8 @@ This major release renames several values in this chart and adds missing feature
Since this version performs changes in the statefulset, in order to upgrade from previous versions you need to delete the statefulset object before the upgrade.
```console
kubectl delete statefulset <statefulsetName>
helm upgrade <release-name> my-repo/redis-cluster --set redis.password=<REDIS_PASSWORD>
$ kubectl delete statefulset <statefulsetName>
$ helm upgrade <release-name> my-repo/redis-cluster --set redis.password=<REDIS_PASSWORD>
```
### To 6.0.0
bitnami/redis/README.md
+17 -16
View File
@@ -7,10 +7,10 @@ Redis(R) is an open source, advanced key-value store. It is often referred to as
[Overview of Redis&reg;](http://redis.io)
Disclaimer: Redis is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd. Any use by Bitnami is for referential purposes only and does not indicate any sponsorship, endorsement, or affiliation between Redis Ltd.
## TL;DR
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/redis
```
@@ -46,7 +46,8 @@ The main features of each chart are the following:
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/redis
```
@@ -58,7 +59,7 @@ The command deploys Redis&reg; on the Kubernetes cluster in the default configur
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -548,7 +549,7 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set auth.password=secretpassword \
my-repo/redis
@@ -560,7 +561,7 @@ The above command sets the Redis&reg; 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
```console
$ helm install my-release -f values.yaml my-repo/redis
```
@@ -723,7 +724,7 @@ By default, the chart mounts a [Persistent Volume](https://kubernetes.io/docs/co
2. Create the PersistentVolumeClaim
3. Install the chart
```bash
```console
$ helm install my-release --set master.persistence.existingClaim=PVC_NAME my-repo/redis
```
@@ -799,7 +800,7 @@ Backwards compatibility is not guaranteed. To upgrade to `14.0.0`, install a new
- Create a backup of the database, and restore it on the new release as explained in the [Backup and restore](#backup-and-restore) section.
- Reuse the PVC used to hold the master data on your previous release. To do so, use the `master.persistence.existingClaim` parameter. The following example assumes that the release name is `redis`:
```bash
```console
$ helm install redis my-repo/redis --set auth.password=[PASSWORD] --set master.persistence.existingClaim=[EXISTING_PVC]
```
@@ -872,14 +873,14 @@ This version causes a change in the Redis&reg; Master StatefulSet definition, so
- Recommended: Create a clone of the Redis&reg; 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 my-repo/redis --set persistence.existingClaim=<NEW PVC>
$ helm install my-release my-repo/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&reg; Master StatefulSet. As a consequence, the following commands can be done to upgrade the release
```
helm delete --purge <RELEASE>
helm install <RELEASE> my-repo/redis
$ helm delete --purge <RELEASE>
$ helm install <RELEASE> my-repo/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.
@@ -919,15 +920,15 @@ Finally, it fixes https://github.com/helm/charts/issues/7803 by removing mutable
In order to upgrade, delete the Redis&reg; StatefulSet before upgrading:
```bash
kubectl delete statefulsets.apps --cascade=false my-release-redis-master
```console
$ kubectl delete statefulsets.apps --cascade=false my-release-redis-master
```
And edit the Redis&reg; slave (and metrics if enabled) deployment:
```bash
kubectl patch deployments my-release-redis-slave --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
kubectl patch deployments my-release-redis-metrics --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
```console
$ kubectl patch deployments my-release-redis-slave --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
$ kubectl patch deployments my-release-redis-metrics --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
```
## License
bitnami/redmine/README.md
+15 -14
View File
@@ -7,10 +7,10 @@ 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
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/redmine
```
@@ -34,7 +34,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/redmine
```
@@ -46,7 +47,7 @@ The command deploys Redmine on the Kubernetes cluster in the default configurati
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -57,7 +58,7 @@ The command removes all the Kubernetes components associated with the chart and
This chart includes the option to use a PostgreSQL database for Redmine instead of MariaDB. To use this, set the `databaseType` parameter to `postgresql`:
```
helm install my-release my-repo/redmine --set databaseType=postgresql
$ helm install my-release my-repo/redmine --set databaseType=postgresql
```
## Parameters
@@ -376,7 +377,7 @@ The above parameters map to the env variables defined in [bitnami/redmine](https
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set redmineUsername=admin,redminePassword=password,mariadb.mariadb.auth.rootPassword=secretpassword \
my-repo/redmine
@@ -388,7 +389,7 @@ The above command sets the Redmine 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,
```bash
```console
$ helm install my-release -f values.yaml my-repo/redmine
```
@@ -503,7 +504,7 @@ The following example includes two PVCs, one for Redmine and another for MariaDB
1. Create the directory, on a worker
1. Install the chart
```bash
```console
$ helm install test --set persistence.existingClaim=PVC_REDMINE,mariadb.persistence.existingClaim=PVC_MARIADB my-repo/redmine
```
@@ -526,8 +527,8 @@ certificates:
Secret can be created with:
```bash
kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
```console
$ kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
```
### TLS Certificate
@@ -551,14 +552,14 @@ certificates:
The certificate tls secret can be created with:
```bash
kubectl create secret tls my-secret --cert tls.crt --key tls.key
```console
$ kubectl create secret tls my-secret --cert tls.crt --key tls.key
```
The certificate chain is created with:
```bash
kubectl create secret generic my-cert-chain --from-file chain.pem
```console
$ kubectl create secret generic my-cert-chain --from-file chain.pem
```
## Troubleshooting
bitnami/schema-registry/README.md
+18 -18
View File
@@ -7,12 +7,12 @@ Confluent Schema Registry provides a RESTful interface by adding a serving layer
[Overview of Confluent Schema Registry](https://www.confluent.io)
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
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/schema-registry
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/schema-registry
```
## Introduction
@@ -32,9 +32,9 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
To install the chart with the release name `my-release`:
```bash
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/schema-registry
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/schema-registry
```
These commands deploy Schema Registry on the Kubernetes cluster with the default configuration. The [parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -45,8 +45,8 @@ These commands deploy Schema Registry on the Kubernetes cluster with the default
To uninstall/delete the `my-release` chart:
```bash
helm delete my-release
```console
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -255,8 +255,8 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
helm install my-release \
```console
$ helm install my-release \
--set replicaCount=2 \
my-repo/schema-registry
```
@@ -265,8 +265,8 @@ The above command installs Schema Registry chart with 2 replicas.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
helm install my-release -f values.yaml my-repo/schema-registry
```console
$ helm install my-release -f values.yaml my-repo/schema-registry
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -314,9 +314,9 @@ In order to configure TLS authentication/encryption, you **can** create a secret
For instance, to configure TLS authentication on a cluster with 2 Kafka brokers, and 1 Schema Registry replica use the commands below to create the secrets:
```console
kubectl create secret generic schema-registry-jks --from-file=/schema-registry.truststore.jks --from-file=./schema-registry-0.keystore.jks
kubectl create secret generic kafka-jks-0 --from-file=kafka.truststore.jks=./kafka.truststore.jks --from-file=kafka.keystore.jks=./kafka-0.keystore.jks
kubectl create secret generic kafka-jks-1 --from-file=kafka.truststore.jks=./kafka.truststore.jks --from-file=kafka.keystore.jks=./kafka-1.keystore.jks
$ kubectl create secret generic schema-registry-jks --from-file=/schema-registry.truststore.jks --from-file=./schema-registry-0.keystore.jks
$ kubectl create secret generic kafka-jks-0 --from-file=kafka.truststore.jks=./kafka.truststore.jks --from-file=kafka.keystore.jks=./kafka-0.keystore.jks
$ kubectl create secret generic kafka-jks-1 --from-file=kafka.truststore.jks=./kafka.truststore.jks --from-file=kafka.keystore.jks=./kafka-1.keystore.jks
```
> **Note**: the command above assumes you already created the truststore and keystores files. This [script](https://raw.githubusercontent.com/confluentinc/confluent-platform-security-tools/master/kafka-generate-ssl.sh) can help you with the JKS files generation.
@@ -337,8 +337,8 @@ kafka.auth.tls.password=jksPassword
In case you want to ignore hostname verification on Kafka certificates, set the parameter `auth.kafka.tls.endpointIdentificationAlgorithm` with an empty string `""`. In this case, you can reuse the same truststore and keystore for every Kafka broker and Schema Registry replica. For instance, to configure TLS authentication on a cluster with 2 Kafka brokers, and 1 Schema Registry replica use the commands below to create the secrets:
```console
kubectl create secret generic schema-registry-jks --from-file=schema-registry.truststore.jks=common.truststore.jks --from-file=schema-registry-0.keystore.jks=common.keystore.jks
kubectl create secret generic kafka-jks --from-file=kafka.truststore.jks=common.truststore.jks --from-file=kafka.keystore.jks=common.keystore.jks
$ kubectl create secret generic schema-registry-jks --from-file=schema-registry.truststore.jks=common.truststore.jks --from-file=schema-registry-0.keystore.jks=common.keystore.jks
$ kubectl create secret generic kafka-jks --from-file=kafka.truststore.jks=common.truststore.jks --from-file=kafka.keystore.jks=common.keystore.jks
```
### Adding extra flags
bitnami/sealed-secrets/README.md
+7 -6
View File
@@ -7,7 +7,7 @@ Sealed Secrets are "one-way" encrypted K8s Secrets that can be created by anyone
[Overview of Sealed Secrets](https://github.com/bitnami-labs/sealed-secrets)
## TL;DR
```console
@@ -33,7 +33,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm install my-release my-repo/sealed-secrets
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/sealed-secrets
```
The command deploys the Sealed Secrets controller on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -45,7 +46,7 @@ The command deploys the Sealed Secrets controller on the Kubernetes cluster in t
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -228,7 +229,7 @@ The above command sets the `livenessProbe.successThreshold` to `5`.
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
```console
helm install my-release -f values.yaml my-repo/sealed-secrets
$ helm install my-release -f values.yaml my-repo/sealed-secrets
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -241,8 +242,8 @@ The easiest way to interact with the Sealed Secrets controller is using the **ku
Once installed, you can start using it to encrypt your secrets or fetching the controller public certificate as shown in the example below:
```bash
kubeseal --fetch-cert \
```console
$ kubeseal --fetch-cert \
--controller-name=my-release \
--controller-namespace=my-release-namespace \
> pub-cert.pem
bitnami/solr/README.md
+3 -3
View File
@@ -7,7 +7,7 @@ Apache Solr is an extremely powerful, open source enterprise search platform bui
[Overview of Apache Solr](http://lucene.apache.org/solr/)
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
```console
@@ -30,7 +30,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
## Installing the Chart
To install the chart with the release name `my-release`:
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
@@ -502,4 +502,4 @@ Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
limitations under the License.
bitnami/sonarqube/README.md
+2 -1
View File
@@ -7,7 +7,7 @@ SonarQube(TM) is an open source quality management platform that analyzes and me
[Overview of SonarQube&trade;](http://www.sonarqube.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. SonarQube is a registered trademark of SonarSource SA.
## TL;DR
```console
@@ -31,6 +31,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/sonarqube
```
bitnami/spark/README.md
+2 -2
View File
@@ -7,7 +7,7 @@ Apache Spark is a high-performance engine for large-scale computing tasks, such
[Overview of Apache Spark](https://spark.apache.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
```console
@@ -372,7 +372,7 @@ To submit an application to the Apache Spark cluster, use the `spark-submit` scr
The command below illustrates the process of deploying one of the sample applications included with Apache Spark. Replace the `k8s-apiserver-host`, `k8s-apiserver-port`, `spark-master-svc`, and `spark-master-port` placeholders with the correct master host/IP address and port for your deployment.
```bash
```console
$ ./bin/spark-submit \
--class org.apache.spark.examples.SparkPi \
--conf spark.kubernetes.container.image=bitnami/spark:3 \
bitnami/spring-cloud-dataflow/README.md
+33 -33
View File
@@ -7,12 +7,12 @@ Spring Cloud Data Flow is a microservices-based toolkit for building streaming a
[Overview of Spring Cloud Data Flow](https://github.com/spring-cloud/spring-cloud-dataflow)
## TL;DR
```bash
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/spring-cloud-dataflow
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/spring-cloud-dataflow
```
## Introduction
@@ -31,9 +31,9 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/spring-cloud-dataflow
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/spring-cloud-dataflow
```
These commands deploy Spring Cloud Data Flow on the Kubernetes cluster with the default configuration. The [parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -44,8 +44,8 @@ These commands deploy Spring Cloud Data Flow on the Kubernetes cluster with the
To uninstall/delete the `my-release` chart:
```bash
helm uninstall my-release
```console
$ helm uninstall my-release
```
## Parameters
@@ -467,16 +467,16 @@ helm uninstall my-release
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
helm install my-release --set server.replicaCount=2 my-repo/spring-cloud-dataflow
```console
$ helm install my-release --set server.replicaCount=2 my-repo/spring-cloud-dataflow
```
The above command installs Spring Cloud Data Flow chart with 2 Dataflow server replicas.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
helm install my-release -f values.yaml my-repo/spring-cloud-dataflow
```console
$ helm install my-release -f values.yaml my-repo/spring-cloud-dataflow
```
> **Tip**: You can use the default [values.yaml](https://github.com/bitnami/charts/blob/main/bitnami/spring-cloud-dataflow/values.yaml)
@@ -712,16 +712,16 @@ To upgrade to *6.0.0* from *5.x* using Kafka as messaging solution, it should be
1. Obtain the credentials on your current release:
```bash
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default scdf-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default scdf-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
```console
$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default scdf-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default scdf-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
```
2. Upgrade your release using the same Kafka version:
```bash
export CURRENT_KAFKA_VERSION=$(kubectl exec scdf-kafka-0 -- bash -c 'echo $BITNAMI_IMAGE_VERSION')
helm upgrade scdf my-repo/spring-cloud-dataflow \
```console
$ export CURRENT_KAFKA_VERSION=$(kubectl exec scdf-kafka-0 -- bash -c 'echo $BITNAMI_IMAGE_VERSION')
$ helm upgrade scdf my-repo/spring-cloud-dataflow \
--set rabbitmq.enabled=false \
--set kafka.enabled=true \
--set kafka.image.tag=$CURRENT_KAFKA_VERSION \
@@ -774,14 +774,14 @@ This major updates the Kafka subchart to its newest major 13.0.0. For more infor
### v0.x.x
```bash
helm upgrade my-release my-repo/spring-cloud-dataflow --set mariadb.rootUser.password=[MARIADB_ROOT_PASSWORD] --set rabbitmq.auth.password=[RABBITMQ_PASSWORD] --set rabbitmq.auth.erlangCookie=[RABBITMQ_ERLANG_COOKIE]
```console
$ helm upgrade my-release my-repo/spring-cloud-dataflow --set mariadb.rootUser.password=[MARIADB_ROOT_PASSWORD] --set rabbitmq.auth.password=[RABBITMQ_PASSWORD] --set rabbitmq.auth.erlangCookie=[RABBITMQ_ERLANG_COOKIE]
```
### v1.x.x
```bash
helm upgrade my-release my-repo/spring-cloud-dataflow --set mariadb.auth.rootPassword=[MARIADB_ROOT_PASSWORD] --set rabbitmq.auth.password=[RABBITMQ_PASSWORD] --set rabbitmq.auth.erlangCookie=[RABBITMQ_ERLANG_COOKIE]
```console
$ helm upgrade my-release my-repo/spring-cloud-dataflow --set mariadb.auth.rootPassword=[MARIADB_ROOT_PASSWORD] --set rabbitmq.auth.password=[RABBITMQ_PASSWORD] --set rabbitmq.auth.erlangCookie=[RABBITMQ_ERLANG_COOKIE]
```
### To 1.0.0
@@ -794,18 +794,18 @@ To upgrade to `1.0.0`, you will need to reuse the PVC used to hold the MariaDB d
Obtain the credentials and the name of the PVC used to hold the MariaDB data on your current release:
```bash
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default dataflow-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default dataflow-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=dataflow -o jsonpath="{.items[0].metadata.name}")
export RABBITMQ_PASSWORD=$(kubectl get secret --namespace default dataflow-rabbitmq -o jsonpath="{.data.rabbitmq-password}" | base64 -d)
export RABBITMQ_ERLANG_COOKIE=$(kubectl get secret --namespace default dataflow-rabbitmq -o jsonpath="{.data.rabbitmq-erlang-cookie}" | base64 -d)
```console
$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default dataflow-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default dataflow-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
$ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=dataflow -o jsonpath="{.items[0].metadata.name}")
$ export RABBITMQ_PASSWORD=$(kubectl get secret --namespace default dataflow-rabbitmq -o jsonpath="{.data.rabbitmq-password}" | base64 -d)
$ export RABBITMQ_ERLANG_COOKIE=$(kubectl get secret --namespace default dataflow-rabbitmq -o jsonpath="{.data.rabbitmq-erlang-cookie}" | base64 -d)
```
Upgrade your release (maintaining the version) disabling MariaDB and scaling Data Flow replicas to 0:
```bash
helm upgrade dataflow my-repo/spring-cloud-dataflow --version 0.7.4 \
```console
$ helm upgrade dataflow my-repo/spring-cloud-dataflow --version 0.7.4 \
--set server.replicaCount=0 \
--set skipper.replicaCount=0 \
--set mariadb.enabled=false \
@@ -815,8 +815,8 @@ helm upgrade dataflow my-repo/spring-cloud-dataflow --version 0.7.4 \
Finally, upgrade you release to 1.0.0 reusing the existing PVC, and enabling back MariaDB:
```bash
helm upgrade dataflow my-repo/spring-cloud-dataflow \
```console
$ helm upgrade dataflow my-repo/spring-cloud-dataflow \
--set mariadb.primary.persistence.existingClaim=$MARIADB_PVC \
--set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD \
--set mariadb.auth.password=$MARIADB_PASSWORD \
bitnami/suitecrm/README.md
+10 -9
View File
@@ -7,7 +7,7 @@ SuiteCRM is a completely open source, enterprise-grade Customer Relationship Man
[Overview of SuiteCRM](http://www.suitecrm.com/)
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
```console
@@ -37,6 +37,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/suitecrm
```
@@ -326,7 +327,7 @@ The above parameters map to the env variables defined in [bitnami/suitecrm](http
>
> To reserve a public IP address on GKE:
>
> ```bash
> ```console
> $ gcloud compute addresses create suitecrm-public-ip
> ```
>
@@ -397,7 +398,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
1. Create the PersistentVolumeClaim
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/suitecrm
```
@@ -413,7 +414,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
1. The specified `hostPath` directory must already exist (create one if it does not).
1. Install the chart
```bash
```console
$ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/suitecrm
```
@@ -497,11 +498,11 @@ To upgrade to `9.0.0`, you can either install a new SuiteCRM chart and migrate y
Obtain the credentials and the names of the PVCs used to hold both the MariaDB and SuiteCRM data on your current release:
```console
export SUITECRM_HOST=$(kubectl get svc --namespace default suitecrm --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
export SUITECRM_PASSWORD=$(kubectl get secret --namespace default suitecrm -o jsonpath="{.data.suitecrm-password}" | base64 -d)
export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default suitecrm-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
export MARIADB_PASSWORD=$(kubectl get secret --namespace default suitecrm-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=suitecrm -o jsonpath="{.items[0].metadata.name}")
$ export SUITECRM_HOST=$(kubectl get svc --namespace default suitecrm --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
$ export SUITECRM_PASSWORD=$(kubectl get secret --namespace default suitecrm -o jsonpath="{.data.suitecrm-password}" | base64 -d)
$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default suitecrm-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default suitecrm-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
$ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=suitecrm -o jsonpath="{.items[0].metadata.name}")
```
Upgrade your release (maintaining the version) disabling MariaDB and scaling SuiteCRM replicas to 0:
bitnami/tensorflow-resnet/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ TensorFlow ResNet is a client utility for use with TensorFlow Serving and ResNet
[Overview of TensorFlow ResNet](https://github.com/tensorflow/models)
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
```console
bitnami/thanos/README.md
+17 -17
View File
@@ -7,12 +7,12 @@ Thanos is a highly available metrics system that can be added on top of existing
[Overview of Thanos](https://thanos.io/)
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
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/thanos
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/thanos
```
## Introduction
@@ -31,9 +31,9 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```bash
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/thanos
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/thanos
```
These commands deploy Thanos on the Kubernetes cluster with the default configuration. The [configuration](#configuration-and-installation-details) section lists the parameters that can be configured during installation.
@@ -44,8 +44,8 @@ These commands deploy Thanos on the Kubernetes cluster with the default configur
To uninstall/delete the `my-release` chart:
```bash
helm uninstall my-release
```console
$ helm uninstall my-release
```
## Architecture
@@ -1183,16 +1183,16 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
helm install my-release --set query.replicaCount=2 my-repo/thanos
```console
$ helm install my-release --set query.replicaCount=2 my-repo/thanos
```
The above command install Thanos chart with 2 Thanos Query replicas.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
helm install my-release -f values.yaml my-repo/thanos
```console
$ helm install my-release -f values.yaml my-repo/thanos
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -1356,13 +1356,13 @@ minio:
For Helm 3:
```bash
kubectl create namespace monitoring
helm install kube-prometheus \
```console
$ kubectl create namespace monitoring
$ helm install kube-prometheus \
--set prometheus.thanos.create=true \
--namespace monitoring \
bitnami/kube-prometheus
helm install thanos \
$ helm install thanos \
--values values.yaml \
--namespace monitoring \
my-repo/thanos
bitnami/tomcat/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ Apache Tomcat is an open-source web server designed to host and run Java-based w
[Overview of Apache Tomcat](http://tomcat.apache.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
```console
bitnami/wavefront-hpa-adapter/README.md
+3 -3
View File
@@ -7,7 +7,7 @@ Wavefront HPA Adapter for Kubernetes is a Kubernetes Horizontal Pod Autoscaler a
[Overview of Wavefront HPA Adapter for Kubernetes](https://github.com/wavefrontHQ/wavefront-kubernetes-adapter)
## TL;DR
```console
@@ -188,7 +188,7 @@ The above command sets the `livenessProbe.successThreshold` to `5`.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/wavefront-hpa-adapter
```
@@ -210,7 +210,7 @@ Find more information about how to deal with common errors related to Bitnami's
## Upgrading
```bash
```console
$ helm upgrade my-release my-repo/wavefront-hpa-adapter
```
bitnami/wavefront-prometheus-storage-adapter/README.md
+3 -3
View File
@@ -7,7 +7,7 @@ Wavefront Storage Adapter is a Prometheus integration to transfer metrics from P
[Overview of Wavefront Prometheus Adapter](https://github.com/wavefrontHQ/prometheus-storage-adapter)
## TL;DR
```console
@@ -196,7 +196,7 @@ The above command sets the `livenessProbe.successThreshold` to `5`.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/wavefront-prometheus-storage-adapter
```
@@ -231,7 +231,7 @@ Find more information about how to deal with common errors related to Bitnami's
## Upgrading
```bash
```console
$ helm upgrade my-release my-repo/wavefront-prometheus-storage-adapter
```
bitnami/wavefront/README.md
+8 -10
View File
@@ -7,13 +7,12 @@ Wavefront is a high-performance streaming analytics platform for monitoring and
[Overview of Wavefront](https://github.com/wavefrontHQ/wavefront-collector-for-kubernetes)
## TL;DR
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ kubectl create namespace wavefront
$ helm install my-release my-repo/wavefront --namespace wavefront \
$ helm install my-release my-repo/wavefront --namespace wavefront --create-namespace \
--set clusterName=<K8s-CLUSTER-NAME> \
--set wavefront.url=https://<YOUR_CLUSTER>.wavefront.com \
--set wavefront.token=<YOUR_API_TOKEN>
@@ -35,12 +34,11 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
## Installing the Chart
To install the chart with the release name `my-release` (if not already done, create a `wavefront` namespace):
To install the chart with the release name `my-release`:
```console
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ kubectl create namespace wavefront
$ helm install my-release my-repo/wavefront --namespace wavefront \
$ helm install my-release my-repo/wavefront --namespace wavefront --create-namespace\
--set clusterName=<K8s-CLUSTER-NAME> \
--set wavefront.url=https://<YOUR_CLUSTER>.wavefront.com \
--set wavefront.token=<YOUR_API_TOKEN>
@@ -56,7 +54,7 @@ The **required** parameters are `clusterName`, `wavefront.url` and `wavefront.to
To uninstall/delete the `my-release` deployment:
```bash
```console
$ helm delete my-release
```
@@ -278,7 +276,7 @@ The command removes all the Kubernetes components associated with the chart and
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```bash
```console
$ helm install my-release \
--set proxy.replicaCount=3 \
my-repo/wavefront
@@ -288,7 +286,7 @@ The above command sets 3 proxy replicas.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```bash
```console
$ helm install my-release -f values.yaml my-repo/wavefront
```
@@ -374,4 +372,4 @@ Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
limitations under the License.
bitnami/wildfly/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ Wildfly is a lightweight, open source application server, formerly known as JBos
[Overview of WildFly](http://www.wildfly.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
```console
bitnami/wordpress/README.md
+11 -10
View File
@@ -7,7 +7,7 @@ WordPress is the world's most popular blogging and content management platform.
[Overview of WordPress](http://www.wordpress.org)
## TL;DR
```console
@@ -35,7 +35,8 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm install my-release my-repo/wordpress
$ helm repo add my-repo https://charts.bitnami.com/bitnami
$ helm install my-release my-repo/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.
@@ -47,7 +48,7 @@ The command deploys WordPress on the Kubernetes cluster in the default configura
To uninstall/delete the `my-release` deployment:
```console
helm delete my-release
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -387,7 +388,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 my-release \
$ helm install my-release \
--set wordpressUsername=admin \
--set wordpressPassword=password \
--set mariadb.auth.rootPassword=secretpassword \
@@ -401,7 +402,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 my-release -f values.yaml my-repo/wordpress
$ helm install my-release -f values.yaml my-repo/wordpress
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -421,9 +422,9 @@ When performing admin operations that require activating the maintenance mode (s
To avoid that, you can manually activate/deactivate the maintenance mode on every replica using the WP CLI. For instance, if you installed WP with three replicas, you can run the commands below to activate the maintenance mode in all of them (assuming that the release name is `wordpress`):
```console
kubectl exec $(kubectl get pods -l app.kubernetes.io/name=wordpress -o jsonpath='{.items[0].metadata.name}') -c wordpress -- wp maintenance-mode activate
kubectl exec $(kubectl get pods -l app.kubernetes.io/name=wordpress -o jsonpath='{.items[1].metadata.name}') -c wordpress -- wp maintenance-mode activate
kubectl exec $(kubectl get pods -l app.kubernetes.io/name=wordpress -o jsonpath='{.items[2].metadata.name}') -c wordpress -- wp maintenance-mode activate
$ kubectl exec $(kubectl get pods -l app.kubernetes.io/name=wordpress -o jsonpath='{.items[0].metadata.name}') -c wordpress -- wp maintenance-mode activate
$ kubectl exec $(kubectl get pods -l app.kubernetes.io/name=wordpress -o jsonpath='{.items[1].metadata.name}') -c wordpress -- wp maintenance-mode activate
$ kubectl exec $(kubectl get pods -l app.kubernetes.io/name=wordpress -o jsonpath='{.items[2].metadata.name}') -c wordpress -- wp maintenance-mode activate
```
### External database support
@@ -626,8 +627,8 @@ Backwards compatibility is not guaranteed unless you modify the labels used on t
Use the workaround below to upgrade from versions previous to `3.0.0`. The following example assumes that the release name is `wordpress`:
```console
kubectl patch deployment wordpress-wordpress --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
kubectl delete statefulset wordpress-mariadb --cascade=false
$ kubectl patch deployment wordpress-wordpress --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
$ kubectl delete statefulset wordpress-mariadb --cascade=false
```
## License
bitnami/zookeeper/README.md
+1 -1
View File
@@ -7,7 +7,7 @@ Apache ZooKeeper provides a reliable, centralized register of configuration data
[Overview of Apache ZooKeeper](https://zookeeper.apache.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
```console