[bitnami/*] Fix markdown linter issues (#14874)

* [bitnami/*] Fix markdown linter issues

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

* Fix more issues

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

* Fix petetes

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

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

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

---------

Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>

.github/PULL_REQUEST_TEMPLATE.md

@@ -25,7 +25,7 @@
 ### Applicable issues
 
 <!-- Enter any applicable Issues here (You can reference an issue using #) -->
-  - fixes #
+- fixes #
 
 ### Additional information
 

CODE_OF_CONDUCT.md

@@ -12,6 +12,6 @@ If you are subjected to or witness unacceptable behavior, or have any other conc
 
 If you have suggestions to improve this Code of Conduct, please submit an issue or PR.
 
-**Attribution**
+## Attribution
 
-This Code of Conduct is adapted from the Angular project available at this page: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md
+This Code of Conduct is adapted from the Angular project available at this page: <https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md>

CONTRIBUTING.md

@@ -14,6 +14,7 @@ Any type of contribution is welcome; from new features, bug fixes, [tests](#test
 ### Technical Requirements
 
 When submitting a PR make sure that it:
+
 - Must pass CI jobs for linting and test the changes on top of different k8s platforms. (Automatically done by the Bitnami CI/CD pipeline).
 - Must follow [Helm best practices](https://helm.sh/docs/chart_best_practices/).
 - Any change to a chart requires a version bump following [semver](https://semver.org/) principles. This is the version that is going to be merged in the GitHub repository, then our CI/CD system is going to publish in the Helm registry a new patch version including your changes and the latest images and dependencies.
@@ -32,14 +33,14 @@ If you set your `user.name` and `user.email` git configs, you can sign your comm
 
 Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this:
 
-```
-Author: Joe Smith <joe.smith@example.com>
-Date:   Thu Feb 2 11:41:15 2018 -0800
+    ```text
+    Author: Joe Smith <joe.smith@example.com>
+    Date:   Thu Feb 2 11:41:15 2018 -0800
 
-    Update README
+        Update README
 
-    Signed-off-by: Joe Smith <joe.smith@example.com>
-```
+        Signed-off-by: Joe Smith <joe.smith@example.com>
+    ```
 
 Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check.
 
@@ -68,6 +69,7 @@ Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will
 ### Adding a new chart to the repository
 
 There are three major technical requirements to add a new Helm chart to our catalog:
+
 - The chart should use Bitnami based container images. If they don't exist, you can [open a GitHub issue](https://github.com/bitnami/charts/issues/new/choose) and we will work together to create them.
 - Follow the same structure/patterns that the rest of the Bitnami charts (you can find a basic scaffolding in the [`template` directory](https://github.com/bitnami/charts/tree/main/template)) and the [Best Practices for Creating Production-Ready Helm charts](https://docs.bitnami.com/tutorials/production-ready-charts/) guide.
 - Use an [OSI approved license](https://opensource.org/licenses) for all the software.

README.md

@@ -8,9 +8,9 @@ Popular applications, provided by [Bitnami](https://bitnami.com), ready to launc
 ## TL;DR
 
 ```bash
-$ helm repo add bitnami https://charts.bitnami.com/bitnami
-$ helm search repo bitnami
-$ helm install my-release bitnami/<chart>
+helm repo add bitnami https://charts.bitnami.com/bitnami
+helm search repo bitnami
+helm install my-release bitnami/<chart>
 ```
 
 ![Installing a chart](demo.gif)
@@ -39,7 +39,6 @@ The quickest way to setup a Kubernetes cluster to install Bitnami Charts is foll
 - [Get Started with Bitnami Charts using the Azure Kubernetes Service (AKS)](https://docs.bitnami.com/kubernetes/get-started-aks/)
 - [Get Started with Bitnami Charts using the Amazon Elastic Container Service for Kubernetes (EKS)](https://docs.bitnami.com/kubernetes/get-started-eks/)
 - [Get Started with Bitnami Charts using the Google Kubernetes Engine (GKE)](https://docs.bitnami.com/kubernetes/get-started-gke/)
-- [Get Started with Bitnami Charts using the IBM Cloud Kubernetes Service (IKS)](https://docs.bitnami.com/kubernetes/get-started-charts-iks/)
 
 For setting up Kubernetes on other cloud platforms or bare-metal servers refer to the Kubernetes [getting started guide](https://kubernetes.io/docs/getting-started-guides/).
 
@@ -54,7 +53,7 @@ To install Helm, refer to the [Helm install guide](https://github.com/helm/helm#
 The following command allows you to download and install all the charts from this repository:
 
 ```bash
-$ helm repo add bitnami https://charts.bitnami.com/bitnami
+helm repo add bitnami https://charts.bitnami.com/bitnami
 ```
 
 > **_NOTE:_** It is important to note that the above mentioned repo is truncated so it only contains entries for the releases produced in the last 6 months. In case you need a full index, you can use it from the [archive-full-index branch](https://raw.githubusercontent.com/bitnami/charts/archive-full-index/bitnami/index.yaml) in the bitnami/charts Github repository.
@@ -70,9 +69,10 @@ Once you have installed the Helm client, you can deploy a Bitnami Helm Chart int
 Please refer to the [Quick Start guide](https://helm.sh/docs/intro/quickstart/) if you wish to get running in just a few commands, otherwise the [Using Helm Guide](https://helm.sh/docs/intro/using_helm/) provides detailed instructions on how to use the Helm client to manage packages on your Kubernetes cluster.
 
 Useful Helm Client Commands:
-* View available charts: `helm search repo`
-* Install a chart: `helm install my-release bitnami/<package-name>`
-* Upgrade your application: `helm upgrade`
+
+- View available charts: `helm search repo`
+- Install a chart: `helm install my-release bitnami/<package-name>`
+- Upgrade your application: `helm upgrade`
 
 ## License
 
@@ -82,7 +82,7 @@ Licensed under the Apache License, Version 2.0 (the "License"); you may not use
 
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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.

TESTING.md

@@ -20,16 +20,17 @@ In this section, we will discuss:
 * [Test types and tools](#test-types-and-tools)
 * [Generic acceptance criteria](#generic-acceptance-criteria)
 * [Cypress](#cypress)
-  * [Run it locally](#run-it-locally)
-  * [Useful information](#useful-information)
-  * [Specific acceptance criteria](#specific-acceptance-criteria)
+  * [Run Cypress locally](#run-cypress-locally)
+  * [Useful Cypress information](#useful-cypress-information)
+  * [Specific Cypress acceptance criteria](#specific-cypress-acceptance-criteria)
 * [Ginkgo](#ginkgo)
-  * [Run it locally](#run-it-locally-1)
-  * [Specific acceptance criteria](#specific-acceptance-criteria-1)
+  * [Run Ginkgo locally](#run-ginkgo-locally)
+  * [Useful Ginkgo information](#useful-ginkgo-information)
+  * [Specific Ginkgo acceptance criteria](#specific-ginkgo-acceptance-criteria)
 * [GOSS](#goss)
-  * [Run it locally](#run-it-locally-2)
-  * [Useful information](#useful-information-1)
-  * [Specific acceptance criteria](#specific-acceptance-criteria-2)
+  * [Run GOSS locally](#run-goss-locally)
+  * [Useful GOSS information](#useful-goss-information)
+  * [Specific GOSS acceptance criteria](#specific-goss-acceptance-criteria)
 
 ## Where to find the tests
 
@@ -123,10 +124,11 @@ Hence, tweaking the files allows to define different action policies depending o
 The general aim of the tests should be to verify the Chart package works as expected. As such, the focus IS NOT on the application OR the container images, which should be regarded as trustful components (i.e. they should have been respectively tested at a previous stage), but in the Chart itself and the different features it provides. It is expected though to assert the CORE functionality (or functionalities) of the application works, but checks defined in this repository should never aim to replace the official test suite.
 
 Some examples on the suitability of tests for the `bitnami/wordpress` chart:
- * ✅ Creating a blog post (represents the CORE functionality of the asset)
- * ❌ Creating a comment in a post (far too specific, not useful)
- * ❌ Installing a plugin through the admin panel (far too specific, not useful)
- * ✅ Specifying a different UID using the `containerSecurityContext.runAsUser` in `values.yaml` and checking it (checks a feature intrinsic to the Chart)
+
+* ✅ Creating a blog post (represents the CORE functionality of the asset)
+* ❌ Creating a comment in a post (far too specific, not useful)
+* ❌ Installing a plugin through the admin panel (far too specific, not useful)
+* ✅ Specifying a different UID using the `containerSecurityContext.runAsUser` in `values.yaml` and checking it (checks a feature intrinsic to the Chart)
 
 The tests may be regarded as _deployment_ tests since their goal is to verify that the software is correctly deployed with all the inherent features. Both functional and non-functional characteristics are evaluated in these tests, focusing on the installation aspect.
 
@@ -136,9 +138,9 @@ Before writing any test scenario, understand the primary purpose of the chart an
 
 As Charts are usually composed of a number of different components, it is also essential to test their integrations and the Chart as a whole. As a general guideline, testing a `bitnami/chart` can be reduced to:
 
-1. Identifying the components of the Chart and verifying their integration. *e.g. WordPress + MariaDB + PHP + Data Volume*
-1. Summarizing the main area features the asset offers and asserting the Chart delivers them. *e.g. Creating a post in a blog*
-1. Focusing on the unique features the Chart offers. *e.g. ConfigMaps, PVCs, Services, secrets, etc.*
+1. Identifying the components of the Chart and verifying their integration. _e.g. WordPress + MariaDB + PHP + Data Volume_
+1. Summarizing the main area features the asset offers and asserting the Chart delivers them. _e.g. Creating a post in a blog_
+1. Focusing on the unique features the Chart offers. _e.g. ConfigMaps, PVCs, Services, secrets, etc._
 
 It is easily noticeable though that Charts are usually highly configurable artifacts. Through parameters exposed in `values.yaml`, it is fairly common to perform customizations that range from enabling simple features (e.g. exporting metrics to Prometheus) to complete changes in the architecture of the application that will be deployed (e.g. standalone vs. main-secondary replication in DBs). In order to cope with this high variability, we should:
 
@@ -256,7 +258,7 @@ In order for VIB to execute Cypress tests, the following block of code needs to
 
 > ℹ️❗️ Cypress tests needs the UI to be accessible from outside the K8s testing cluster. This means (in most cases) that the service of the chart which exposes such UI should be set to use a `LoadBalancer` type and port `80` or `443`.
 
-### Run it locally
+### Run Cypress locally
 
 Sometimes it is of interest to run the tests locally, for example during development. Though there may be different approaches, you may follow the steps below to execute the tests locally:
 
@@ -333,7 +335,7 @@ Sometimes it is of interest to run the tests locally, for example during develop
     ✔  All specs passed!                        371ms        1        1
     ```
 
-### Useful information
+### Useful Cypress information
 
 * In most cases, a single test which covers the following topics is enough:
   * Login/Logout: Checks the UI, app, and DB are working together
@@ -343,7 +345,7 @@ Sometimes it is of interest to run the tests locally, for example during develop
 
 * If the asset exposes an API, Cypress is an excellent option to test this feature!
 
-### Specific acceptance criteria
+### Specific Cypress acceptance criteria
 
 * [ ] Test file name has the following format: Helm chart name + spec (ex: `wordpress_spec.js`)
 * [ ] No `describe()` blocks should be present
@@ -389,7 +391,7 @@ In order for VIB to execute Ginkgo tests, the following block of code needs to b
         }
 ```
 
-### Run it locally
+### Run Ginkgo locally
 
 Sometimes it is of interest to run the tests locally, for example during development. Though there may be different approaches, you may follow the steps below to execute the tests locally:
 
@@ -420,7 +422,7 @@ Sometimes it is of interest to run the tests locally, for example during develop
       Test Suite Passed
     ```
 
-### Useful information
+### Useful Ginkgo information
 
 Ginkgo provides extreme flexibility when it comes to tests. Nonetheless, here are the most frequent use cases we have used it for so far:
 
@@ -428,7 +430,7 @@ Ginkgo provides extreme flexibility when it comes to tests. Nonetheless, here ar
 * Deploying, managing and interacting with K8s resources: CRDs, Ingresses, Secrets... Really useful for **K8s operators**
 * Directly interacting (instead of managing) resources deployed at installation time using the `extraDeploy` param, available in bitnami charts
 
-### Specific acceptance criteria
+### Specific Ginkgo acceptance criteria
 
 * [ ] Test file name has the following format: Helm chart name + `test` (ex: `metallb_test.go`)
 * [ ] Helper functions should be placed in an additional file named `integration_suite_test.go`
@@ -457,21 +459,7 @@ In order for VIB to execute GOSS tests, the following block of code needs to be
         }
 ```
 
-### Useful information
-
-As our Charts implement some standardized properties, there are a number of test cases that have been found recurrently throughout the catalog:
-
-* Correct user ID and Group of the running container
-* Reachability of the different ports exposed through services
-* Existence of mounted volumes
-* Correct configuration was applied to a config file or enviroment variable
-* Existence of a created Service Account
-* Restricted capabilities are applied to a running container
-* Valuable CLI checks (when available)
-
-[Kong](https://github.com/bitnami/charts/blob/main/.vib/kong/goss/goss.yaml) or [MetalLB](https://github.com/bitnami/charts/blob/main/.vib/metallb/goss/goss.yaml) are two good examples of tests implementing some of the above.
-
-### Run it locally
+### Run GOSS locally
 
 Sometimes it is of interest to run the tests locally, for example during development. Though there may be different approaches, you may follow the steps below to execute the tests locally:
 
@@ -495,6 +483,7 @@ Sometimes it is of interest to run the tests locally, for example during develop
     $ kubectl cp .vib/nginx/goss/goss.yaml nginx-5fbc8786f-95rpl:/tmp/
     $ kubectl cp .vib/nginx/goss/vars.yaml nginx-5fbc8786f-95rpl:/tmp/
     ```
+
 1. Grant execution permissions to the binary and launch the tests
 
     ```bash
@@ -506,10 +495,24 @@ Sometimes it is of interest to run the tests locally, for example during develop
     Count: 9, Failed: 0, Skipped: 0
     ```
 
-### Specific acceptance criteria
+### Useful GOSS information
+
+As our Charts implement some standardized properties, there are a number of test cases that have been found recurrently throughout the catalog:
+
+* Correct user ID and Group of the running container
+* Reachability of the different ports exposed through services
+* Existence of mounted volumes
+* Correct configuration was applied to a config file or enviroment variable
+* Existence of a created Service Account
+* Restricted capabilities are applied to a running container
+* Valuable CLI checks (when available)
+
+[Kong](https://github.com/bitnami/charts/blob/main/.vib/kong/goss/goss.yaml) or [MetalLB](https://github.com/bitnami/charts/blob/main/.vib/metallb/goss/goss.yaml) are two good examples of tests implementing some of the above.
+
+### Specific GOSS acceptance criteria
 
 * [ ] Main test file name should be `goss.yaml`
 * [ ] Deployment-related parameters should be specified in a file named `vars.yaml`. This is a subset of the `runtime_parameters`
 * [ ] Use templating to parametrize tests with the help of the `vars.yaml` file
 * [ ] Tests should not rely on system packages (e.g. `curl`). Favor built-in GOSS primitives instead
-* [ ] Prefer checking the exit status of a command rather than looking for a specific output. This will avoid most of the potential flakiness
+* [ ] Prefer checking the exit status of a command rather than looking for a specific output. This will avoid most of the potential flakiness

bitnami/airflow/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/airflow
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/airflow
 ```
 
 ## Introduction
@@ -31,8 +31,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/airflow
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/airflow
 ```
 
 These commands deploy Airflow on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -44,7 +44,7 @@ These commands deploy Airflow 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.
@@ -75,6 +75,7 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the the deployment(s)/statefulset(s)                   | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the the deployment(s)/statefulset(s)                      | `["infinity"]`  |
 
+
 ### Airflow common parameters
 
 | Name                     | Description                                                                                                                                                               | Value                   |
@@ -180,6 +181,7 @@ The command removes all the Kubernetes components associated with the chart and
 | `web.pdb.minAvailable`                      | Maximum number/percentage of unavailable Airflow web replicas                                                            | `1`                  |
 | `web.pdb.maxUnavailable`                    | Maximum number/percentage of unavailable Airflow web replicas                                                            | `""`                 |
 
+
 ### Airflow scheduler parameters
 
 | Name                                              | Description                                                                                                              | Value                       |
@@ -493,7 +495,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalRedis.existingSecretPasswordKey`    | Name of an existing secret key containing the Redis&trade credentials                                  | `""`              |
 
 
-Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
 $ helm install my-release \
@@ -511,7 +512,7 @@ The above command sets the credentials to access the Airflow web UI.
 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/airflow
+helm install my-release -f values.yaml my-repo/airflow
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -655,6 +656,7 @@ Local executor runs tasks by spawning processes in the Scheduler pods. To enable
 executor=LocalExecutor
 redis.enabled=false
 ```
+
 ### LocalKubernetesExecutor
 
 The LocalKubernetesExecutor is introduced in Airflow 2.3 and is a combination of both the Local and the Kubernetes executors. Tasks will be executed in the scheduler by default, but those tasks that require it can be executed in a Kubernetes pod using the 'kubernetes' queue.
@@ -707,10 +709,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/apache/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/apache
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/apache
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/apache
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/apache
 ```
 
 These commands deploy Apache on the Kubernetes cluster in the default configuration.
@@ -48,7 +48,7 @@ These commands deploy Apache 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.
@@ -247,7 +247,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRule.rules`             | Prometheus Rule definitions                                                                                                               | `[]`                      |
 
 
-Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
 $ helm install my-release \
@@ -260,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/apache
+helm install my-release -f values.yaml my-repo/apache
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -331,7 +330,7 @@ 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 apache:
 
 ```console
-$ kubectl patch deployment apache --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl patch deployment apache --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
 ```
 
 ## License
@@ -342,10 +341,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/appsmith/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/appsmith
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/appsmith
 ```
 
 ## Introduction
@@ -37,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ 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.
@@ -50,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.
@@ -450,8 +450,6 @@ The command removes all the Kubernetes components associated with the chart and
 
 
 
-The above parameters map to the env variables defined in [bitnami/appsmith](https://github.com/bitnami/containers/tree/main/bitnami/appsmith). For more information please refer to the [bitnami/appsmith](https://github.com/bitnami/containers/tree/main/bitnami/appsmith) image documentation.
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -469,7 +467,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)
@@ -558,10 +556,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/argo-cd/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ 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
 ```
 
 ## 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/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.
@@ -46,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.
@@ -749,7 +749,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `redisWait.securityContext`               | Security context for init container                                                                   | `{}`                 |
 
 
-The above parameters map to the env variables defined in [bitnami/argo-cd](https://github.com/bitnami/containers/tree/main/bitnami/argo-cd). For more information please refer to the [bitnami/argo-cd](https://github.com/bitnami/containers/tree/main/bitnami/argo-cd) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
@@ -767,7 +766,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)
@@ -802,7 +801,6 @@ For more information about each configmap or secret check the references at the
 In order to use SSO you need to enable Dex by setting `dex.enabled=true`. You can follow [this guide](https://argo-cd.readthedocs.io/en/stable/operator-manual/user-management/#1-register-the-application-in-the-identity-provider) to configure your Argo CD deployment into your identity provider. After that, you need to configure Argo CD like described [here](https://argo-cd.readthedocs.io/en/stable/operator-manual/user-management/#2-configure-argo-cd-for-sso). You can set the Dex configuration at `server.config.dex\.config` that will populate the `argocd-cm` config map.
 
 > NOTE: `dex.config` is the key of the object. IF you are using the Helm CLI to set the parameter you need to scape the `.` like `--set server.config.dex\.config`.
-
 > IMPORTANT: if you enable Dex without configuring it you will get an error similar to `msg="dex is not configured"`, and the Dex pod will never reach the running state.
 
 ### Additional environment variables
@@ -844,10 +842,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/argo-workflows/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ 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
 ```
 
 ## 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/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.
@@ -46,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.
@@ -373,7 +373,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.type`           | Either postgresql or mysql                                                  | `""`                |
 
 
-See https://github.com/bitnami-labs/readme-generator-for-helm to create the table
 
 The above parameters map to the env variables defined in [bitnami/argo-workflow-cli](https://github.com/bitnami/containers/tree/main/bitnami/argo-workflow-cli). For more information please refer to the [bitnami/argo-workflow-cli](https://github.com/bitnami/containers/tree/main/bitnami/argo-workflow-cli) image documentation.
 
@@ -394,7 +393,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)
@@ -415,7 +414,7 @@ You may want to have Argo Workflows controller connected to a database to store
 postgresql.enabled=true
 ```
 
-If your installation does not require to to store controller evidences, you can disable the controller persistence by setting `postgresql.enabled=false`, `mysql.enabled=false` and ` externalDatabase.enabled=false`.
+If your installation does not require to to store controller evidences, you can disable the controller persistence by setting `postgresql.enabled=false`, `mysql.enabled=false` and `externalDatabase.enabled=false`.
 
 #### External database
 
@@ -490,10 +489,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/aspnet-core/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## 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
@@ -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/aspnet-core
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/aspnet-core
 ```
 
 These commands deploy a ASP.NET Core application on the Kubernetes cluster in the default configuration.
@@ -46,7 +46,7 @@ These commands deploy a ASP.NET Core application on the Kubernetes cluster in th
 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,10 +239,9 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.automountServiceAccountToken` | Automount service account token                      | `true` |
 
 
-Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
-$ helm install my-release --set replicaCount=2 my-repo/aspnet-core
+helm install my-release --set replicaCount=2 my-repo/aspnet-core
 ```
 
 The above command install ASP.NET Core chart with 2 replicas.
@@ -250,7 +249,7 @@ 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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/aspnet-core
+helm install my-release -f values.yaml my-repo/aspnet-core
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -436,24 +435,24 @@ No issues should be expected when upgrading.
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ## License
 
@@ -463,10 +462,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/cassandra/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/cassandra
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/cassandra
 ```
 
 ## 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/cassandra
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/cassandra
 ```
 
 These commands deploy one node with Apache Cassandra 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 one node with Apache Cassandra on the Kubernetes cluster i
 To uninstall/delete the `my-release` release:
 
 ```console
-$ helm delete my-release
+helm delete my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -300,7 +300,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `tls.tlsEncryptionSecretName` | Secret with the encryption of the TLS certificates                                            | `""`    |
 
 
-The above parameters map to the env variables defined in [bitnami/cassandra](https://github.com/bitnami/containers/tree/main/bitnami/cassandra). For more information please refer to the [bitnami/cassandra](https://github.com/bitnami/containers/tree/main/bitnami/cassandra) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
@@ -313,7 +312,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)
@@ -330,8 +329,8 @@ Bitnami will release a new chart updating its containers if a new version of the
 
 This chart supports TLS between client and server and between nodes, as explained below:
 
-* For internode cluster encryption, set the `tls.internodeEncryption` chart parameter to a value different from `none`. Available values are `all`, `dc` or `rack`.
-* For client-server encryption, set the `tls.clientEncryption` chart parameter to `true`.
+- For internode cluster encryption, set the `tls.internodeEncryption` chart parameter to a value different from `none`. Available values are `all`, `dc` or `rack`.
+- For client-server encryption, set the `tls.clientEncryption` chart parameter to `true`.
 
 In both cases, it is also necessary to create a secret containing the keystore and truststore certificates and their corresponding protection passwords. This secret is to be passed to the chart via the `tls.existingSecret` parameter at deployment-time.
 
@@ -370,8 +369,8 @@ If you encounter errors when working with persistent volumes, refer to our [trou
 
 As the image run as non-root by default, it is necessary to adjust the ownership of the persistent volume so that the container can write data into it. There are two approaches to achieve this:
 
-* Use Kubernetes SecurityContexts by setting the `podSecurityContext.enabled` and `containerSecurityContext.enabled` to `true`. This option is enabled by default in the chart. However, this feature does not work in all Kubernetes distributions.
-* Use an init container to change the ownership of the volume before mounting it in the final destination. Enable this container by setting the `volumePermissions.enabled` parameter to `true`.
+- Use Kubernetes SecurityContexts by setting the `podSecurityContext.enabled` and `containerSecurityContext.enabled` to `true`. This option is enabled by default in the chart. However, this feature does not work in all Kubernetes distributions.
+- Use an init container to change the ownership of the volume before mounting it in the final destination. Enable this container by setting the `volumePermissions.enabled` parameter to `true`.
 
 ## Backup and restore
 
@@ -386,12 +385,13 @@ 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:
 
 ```console
-$ helm upgrade my-release my-repo/cassandra --set dbUser.password=[PASSWORD]
+helm upgrade my-release my-repo/cassandra --set dbUser.password=[PASSWORD]
 ```
 
-| Note: you need to substitute the placeholder _[PASSWORD]_ with the value obtained in the installation notes.
+| Note: you need to substitute the placeholder *[PASSWORD]* with the value obtained in the installation notes.
 
 ### To 9.0.0
+
 This major release renames several values in this chart and adds missing features, in order to be inline with the rest of assets in the Bitnami charts repository.
 
 Affected values:
@@ -407,10 +407,10 @@ Affected values:
 
 Cassandra's version was bumped to `4.0`, [the new major](https://cassandra.apache.org/_/blog/Apache-Cassandra-4.0-is-Here.html) considered LTS. Among other features, this release removes support for [Thrift](https://issues.apache.org/jira/browse/CASSANDRA-11115), which means that the following properties of the chart will no longer be available:
 
-  - `cluster.enableRPC`
-  - `service.thriftPort`
-  - `service.nodePorts.thrift`
-  - `containerPorts.thrift`
+- `cluster.enableRPC`
+- `service.thriftPort`
+- `service.nodePorts.thrift`
+- `containerPorts.thrift`
 
 For this version, there have been [intensive efforts](https://cwiki.apache.org/confluence/display/CASSANDRA/4.0+Quality%3A+Components+and+Test+Plans) from Apache to ensure that a safe cluster upgrade can be performed. Nevertheless, a backup creation prior to undergoing the upgrade process is recommended. Please, refer to the [official guide](https://cassandra.apache.org/doc/latest/operating/backups.html#snapshots) for further information.
 
@@ -443,8 +443,8 @@ 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.
 
 ```console
-$ kubectl delete sts -l release=<RELEASE_NAME>
-$ helm upgrade <RELEASE_NAME> ...
+kubectl delete sts -l release=<RELEASE_NAME>
+helm upgrade <RELEASE_NAME> ...
 ```
 
 ### To 4.0.0
@@ -467,10 +467,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/cert-manager/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/cert-manager
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/cert-manager
 ```
 
 ## 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/cert-manager
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/cert-manager
 ```
 
 > **Tip**: List all releases using `helm list`
@@ -45,7 +45,7 @@ $ helm install my-release my-repo/cert-manager
 To uninstall/delete the `my-release` helm release:
 
 ```console
-$ helm uninstall my-release
+helm uninstall my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -294,7 +294,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `rbac.create` | Specifies whether RBAC resources should be created | `true` |
 
 
-Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
 $ helm install my-release my-repo/cert-manager \
@@ -304,7 +303,7 @@ $ helm install my-release my-repo/cert-manager \
 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/cert-manager
+helm install my-release -f values.yaml my-repo/cert-manager
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -383,10 +382,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/clickhouse/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/clickhouse
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/clickhouse
 ```
 
 ## Introduction
@@ -34,15 +34,15 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
 
 > If you are using Kubernetes 1.18, the following code needs to be commented out.
 > seccompProfile:
->    type: "RuntimeDefault"
+> type: "RuntimeDefault"
 
 ## Installing the Chart
 
 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/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.
@@ -54,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.
@@ -347,7 +347,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `zookeeper.service.ports.client` | Zookeeper client port         | `2181` |
 
 
-See https://github.com/bitnami-labs/readme-generator-for-helm to create the table
 
 The above parameters map to the env variables defined in [bitnami/clickhouse](https://github.com/bitnami/containers/tree/main/bitnami/clickhouse). For more information please refer to the [bitnami/clickhouse](https://github.com/bitnami/containers/tree/main/bitnami/clickhouse) image documentation.
 
@@ -367,7 +366,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)
@@ -380,7 +379,6 @@ It is strongly recommended to use immutable tags in a production environment. Th
 
 Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
 
-
 ### ClickHouse keeper support
 
 You can set `keeper.enabled` to use ClickHouse keeper. If `keeper.enabled=true`, Zookeeper settings will not be ignore.
@@ -512,10 +510,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/common/README.md

@@ -12,7 +12,7 @@ dependencies:
 ```
 
 ```console
-$ helm dependency update
+helm dependency update
 ```
 
 ```yaml
@@ -37,124 +37,6 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
 
 ## Parameters
 
-The following table lists the helpers available in the library which are scoped in different sections.
-
-### Affinities
-
-| Helper identifier             | Description                                          | Expected Input                                 |
-|-------------------------------|------------------------------------------------------|------------------------------------------------|
-| `common.affinities.nodes.soft`  | Return a soft nodeAffinity definition                 | `dict "key" "FOO" "values" (list "BAR" "BAZ")`  |
-| `common.affinities.nodes.hard`  | Return a hard nodeAffinity definition                 | `dict "key" "FOO" "values" (list "BAR" "BAZ")`  |
-| `common.affinities.pods.soft`   | Return a soft podAffinity/podAntiAffinity definition  | `dict "component" "FOO" "context" $`            |
-| `common.affinities.pods.hard`   | Return a hard podAffinity/podAntiAffinity definition  | `dict "component" "FOO" "context" $`            |
-| `common.affinities.topologyKey` | Return a topologyKey definition                       | `dict "topologyKey" "FOO"`                      |
-
-### Capabilities
-
-| Helper identifier                              | Description                                                                                    | Expected Input    |
-|------------------------------------------------|------------------------------------------------------------------------------------------------|-------------------|
-| `common.capabilities.kubeVersion`              | Return the target Kubernetes version (using client default if .Values.kubeVersion is not set). | `.` Chart context |
-| `common.capabilities.cronjob.apiVersion`       | Return the appropriate apiVersion for cronjob.                                                 | `.` Chart context |
-| `common.capabilities.deployment.apiVersion`    | Return the appropriate apiVersion for deployment.                                              | `.` Chart context |
-| `common.capabilities.statefulset.apiVersion`   | Return the appropriate apiVersion for statefulset.                                             | `.` Chart context |
-| `common.capabilities.ingress.apiVersion`       | Return the appropriate apiVersion for ingress.                                                 | `.` Chart context |
-| `common.capabilities.rbac.apiVersion`          | Return the appropriate apiVersion for RBAC resources.                                          | `.` Chart context |
-| `common.capabilities.crd.apiVersion`           | Return the appropriate apiVersion for CRDs.                                                    | `.` Chart context |
-| `common.capabilities.policy.apiVersion`        | Return the appropriate apiVersion for podsecuritypolicy.                                       | `.` Chart context |
-| `common.capabilities.networkPolicy.apiVersion` | Return the appropriate apiVersion for networkpolicy.                                           | `.` Chart context |
-| `common.capabilities.apiService.apiVersion`    | Return the appropriate apiVersion for APIService.                                              | `.` Chart context |
-| `common.capabilities.hpa.apiVersion`           | Return the appropriate apiVersion for Horizontal Pod Autoscaler                                | `.` Chart context |
-| `common.capabilities.supportsHelmVersion`      | Returns true if the used Helm version is 3.3+                                                  | `.` Chart context |
-
-### Errors
-
-| Helper identifier                       | Description                                                                                                                                                            | Expected Input                                                                      |
-|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|
-| `common.errors.upgrade.passwords.empty` | It will ensure required passwords are given when we are upgrading a chart. If `validationErrors` is not empty it will throw an error and will stop the upgrade action. | `dict "validationErrors" (list $validationError00 $validationError01)  "context" $` |
-
-### Images
-
-| Helper identifier           | Description                                          | Expected Input                                                                                          |
-|-----------------------------|------------------------------------------------------|---------------------------------------------------------------------------------------------------------|
-| `common.images.image`       | Return the proper and full image name                | `dict "imageRoot" .Values.path.to.the.image "global" $`, see [ImageRoot](#imageroot) for the structure. |
-| `common.images.pullSecrets` | Return the proper Docker Image Registry Secret Names (deprecated: use common.images.renderPullSecrets instead) | `dict "images" (list .Values.path.to.the.image1, .Values.path.to.the.image2) "global" .Values.global` |
-| `common.images.renderPullSecrets` | Return the proper Docker Image Registry Secret Names (evaluates values as templates) | `dict "images" (list .Values.path.to.the.image1, .Values.path.to.the.image2) "context" $` |
-
-### Ingress
-
-| Helper identifier                         | Description                                                                                                       | Expected Input                                                                                                                                                                   |
-|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `common.ingress.backend`                  | Generate a proper Ingress backend entry depending on the API version                                              | `dict "serviceName" "foo" "servicePort" "bar"`, see the [Ingress deprecation notice](https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/) for the syntax differences |
-| `common.ingress.supportsPathType`         | Prints "true" if the pathType field is supported                                                                  | `.` Chart context                                                                                                                                                                |
-| `common.ingress.supportsIngressClassname` | Prints "true" if the ingressClassname field is supported                                                          | `.` Chart context                                                                                                                                                                |
-| `common.ingress.certManagerRequest`       | Prints "true" if required cert-manager annotations for TLS signed certificates are set in the Ingress annotations | `dict "annotations" .Values.path.to.the.ingress.annotations`                                                                                                                     |
-
-### Labels
-
-| Helper identifier           | Description                                                                 | Expected Input    |
-|-----------------------------|-----------------------------------------------------------------------------|-------------------|
-| `common.labels.standard`    | Return Kubernetes standard labels                                           | `.` Chart context |
-| `common.labels.matchLabels` | Labels to use on `deploy.spec.selector.matchLabels` and `svc.spec.selector` | `.` Chart context |
-
-### Names
-
-| Helper identifier                 | Description                                                           | Expected Input    |
-|-----------------------------------|-----------------------------------------------------------------------|-------------------|
-| `common.names.name`               | Expand the name of the chart or use `.Values.nameOverride`            | `.` Chart context |
-| `common.names.fullname`           | Create a default fully qualified app name.                            | `.` Chart context |
-| `common.names.namespace`          | Allow the release namespace to be overridden                          | `.` Chart context |
-| `common.names.fullname.namespace` | Create a fully qualified app name adding the installation's namespace | `.` Chart context |
-| `common.names.chart`              | Chart name plus version                                               | `.` Chart context |
-
-### Secrets
-
-| Helper identifier                 | Description                                                  | Expected Input                                                                                                                                                                                                                  |
-|-----------------------------------|--------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `common.secrets.name`             | Generate the name of the secret.                             | `dict "existingSecret" .Values.path.to.the.existingSecret "defaultNameSuffix" "mySuffix" "context" $` see [ExistingSecret](#existingsecret) for the structure.                                                                  |
-| `common.secrets.key`              | Generate secret key.                                         | `dict "existingSecret" .Values.path.to.the.existingSecret "key" "keyName"` see [ExistingSecret](#existingsecret) for the structure.                                                                                             |
-| `common.secrets.passwords.manage` | Generate secret password or retrieve one if already created. | `dict "secret" "secret-name" "key" "keyName" "providedValues" (list "path.to.password1" "path.to.password2") "length" 10 "strong" false "chartName" "chartName" "context" $`, length, strong and chartNAme fields are optional. |
-| `common.secrets.exists`           | Returns whether a previous generated secret already exists.  | `dict "secret" "secret-name" "context" $`                                                                                                                                                                                       |
-
-### Storage
-
-| Helper identifier             | Description                           | Expected Input                                                                                                      |
-|-------------------------------|---------------------------------------|---------------------------------------------------------------------------------------------------------------------|
-| `common.storage.class` | Return  the proper Storage Class | `dict "persistence" .Values.path.to.the.persistence "global" $`, see [Persistence](#persistence) for the structure. |
-
-### TplValues
-
-| Helper identifier         | Description                            | Expected Input                                                                                                                                           |
-|---------------------------|----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `common.tplvalues.render` | Renders a value that contains template | `dict "value" .Values.path.to.the.Value "context" $`, value is the value should rendered as template, context frequently is the chart context `$` or `.` |
-
-### Utils
-
-| Helper identifier              | Description                                                                              | Expected Input                                                         |
-|--------------------------------|------------------------------------------------------------------------------------------|------------------------------------------------------------------------|
-| `common.utils.fieldToEnvVar`   | Build environment variable name given a field.                                           | `dict "field" "my-password"`                                           |
-| `common.utils.secret.getvalue` | Print instructions to get a secret value.                                                | `dict "secret" "secret-name" "field" "secret-value-field" "context" $` |
-| `common.utils.getValueFromKey` | Gets a value from `.Values` object given its key path                                    | `dict "key" "path.to.key" "context" $`                                 |
-| `common.utils.getKeyFromList`  | Returns first `.Values` key with a defined value or first of the list if all non-defined | `dict "keys" (list "path.to.key1" "path.to.key2") "context" $`         |
-
-### Validations
-
-| Helper identifier                                | Description                                                                                                                   | Expected Input                                                                                                                                                                                                                                                           |
-|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `common.validations.values.single.empty`         | Validate a value must not be empty.                                                                                           | `dict "valueKey" "path.to.value" "secret" "secret.name" "field" "my-password" "subchart" "subchart" "context" $` secret, field and subchart are optional. In case they are given, the helper will generate a how to get instruction. See [ValidateValue](#validatevalue) |
-| `common.validations.values.multiple.empty`       | Validate a multiple values must not be empty. It returns a shared error for all the values.                                   | `dict "required" (list $validateValueConf00 $validateValueConf01) "context" $`. See [ValidateValue](#validatevalue)                                                                                                                                                      |
-| `common.validations.values.mariadb.passwords`    | This helper will ensure required password for MariaDB are not empty. It returns a shared error for all the values.            | `dict "secret" "mariadb-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use mariadb chart and the helper.                                                                                      |
-| `common.validations.values.mysql.passwords`      | This helper will ensure required password for MySQL are not empty. It returns a shared error for all the values.              | `dict "secret" "mysql-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use mysql chart and the helper.                                                                                      |
-| `common.validations.values.postgresql.passwords` | This helper will ensure required password for PostgreSQL are not empty. It returns a shared error for all the values.         | `dict "secret" "postgresql-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use postgresql chart and the helper.                                                                                |
-| `common.validations.values.redis.passwords`      | This helper will ensure required password for Redis® are not empty. It returns a shared error for all the values. | `dict "secret" "redis-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use redis chart and the helper.                                                                                          |
-| `common.validations.values.cassandra.passwords`  | This helper will ensure required password for Cassandra are not empty. It returns a shared error for all the values.          | `dict "secret" "cassandra-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use cassandra chart and the helper.                                                                                  |
-| `common.validations.values.mongodb.passwords`    | This helper will ensure required password for MongoDB® are not empty. It returns a shared error for all the values.            | `dict "secret" "mongodb-secret" "subchart" "true" "context" $` subchart field is optional and could be true or false it depends on where you will use mongodb chart and the helper.                                                                                      |
-
-### Warnings
-
-| Helper identifier            | Description                      | Expected Input                                             |
-|------------------------------|----------------------------------|------------------------------------------------------------|
-| `common.warnings.rollingTag` | Warning about using rolling tag. | `ImageRoot` see [ImageRoot](#imageroot) for the structure. |
-
 ## Special input schemas
 
 ### ImageRoot
@@ -316,23 +198,23 @@ $ helm install test mychart --set path.to.value00="",path.to.value01=""
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Use `type: library`. [Here](https://v3.helm.sh/docs/faq/#library-chart-support) you can find more information.
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ## License
 
@@ -342,7 +224,7 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,

bitnami/concourse/README.md

@@ -6,13 +6,11 @@ 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
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/concourse
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/concourse
 ```
 
 ## Introduction
@@ -35,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/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.
@@ -48,7 +46,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.
@@ -400,7 +398,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.existingSecretPasswordKey` | Name of an existing secret key containing the database credentials      | `""`                |
 
 
-See https://github.com/bitnami-labs/readme-generator-for-helm to create the table
 
 The above parameters map to the env variables defined in [bitnami/concourse](https://github.com/bitnami/containers/tree/main/bitnami/concourse). For more information please refer to the [bitnami/concourse](https://github.com/bitnami/containers/tree/main/bitnami/concourse) image documentation.
 
@@ -419,7 +416,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)
@@ -498,10 +495,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/consul/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/consul
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/consul
 ```
 
 ## 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/consul
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/consul
 ```
 
 These commands deploy HashiCorp Consul on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -45,12 +45,13 @@ These commands deploy HashiCorp Consul on the Kubernetes cluster in the default
 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. Remove also the chart using `--purge` option:
 
 ```console
-$ helm delete --purge my-release
+helm delete --purge my-release
 ```
 
 ## Parameters
@@ -264,10 +265,9 @@ $ helm delete --purge my-release
 | `metrics.serviceMonitor.labels`                 | Used to pass Labels that are used by the Prometheus installed in your cluster to select Service Monitors to work with                | `{}`                      |
 
 
-Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
-$ helm install my-release --set domain=consul-domain,gossipKey=secretkey my-repo/consul
+helm install my-release --set domain=consul-domain,gossipKey=secretkey my-repo/consul
 ```
 
 The above command sets the HashiCorp Consul domain to `consul-domain` and sets the gossip key to `secretkey`.
@@ -277,7 +277,7 @@ The above command sets the HashiCorp Consul domain to `consul-domain` and sets 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/consul
+helm install my-release -f values.yaml my-repo/consul
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -356,7 +356,7 @@ You must manually create a secret containing your PEM-encoded certificate author
 
 If the secret is specified, the chart will locate those files at `/opt/bitnami/consul/certs/`, so you will want to use the below snippet to configure HashiCorp Consul TLS encryption in your config map:
 
-```
+```json
   "ca_file": "/opt/bitnami/consul/certs/ca.pem",
   "cert_file": "/opt/bitnami/consul/certs/consul.pem",
   "key_file": "/opt/bitnami/consul/certs/consul-key.pem",
@@ -446,28 +446,29 @@ Affected values:
 - `service.port` renamed as `service.port.http`.
 - `service.nodePort` renamed as `service.nodePorts.http`.
 - `updateStrategy` changed from String type (previously default to 'rollingUpdate') to Object type, allowing users to configure other updateStrategy parameters, similar to other charts.
+
 ### To 9.0.0
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 8.0.0
 
@@ -486,8 +487,8 @@ Consul pods are now deployed in parallel in order to bootstrap the cluster and b
 The field `podManagementPolicy` can't be updated in a StatefulSet, so you need to destroy it before you upgrade the chart to this version.
 
 ```console
-$ kubectl delete statefulset consul
-$ helm upgrade <DEPLOYMENT_NAME> my-repo/consul
+kubectl delete statefulset consul
+helm upgrade <DEPLOYMENT_NAME> my-repo/consul
 ```
 
 ### To 6.0.0
@@ -498,14 +499,14 @@ This release updates the Bitnami Consul container to `1.6.1-debian-9-r6`, which
 
 Consul container was moved to a non-root approach. There shouldn't be any issue when upgrading since the corresponding `securityContext` is enabled by default. Both the container image and the chart can be upgraded by running the command below:
 
-```
-$ helm upgrade my-release my-repo/consul
+```console
+helm upgrade my-release my-repo/consul
 ```
 
 If you use a previous container image (previous to **1.4.0-r16**) disable the `securityContext` by running the command below:
 
-```
-$ helm upgrade my-release my-repo/consul --set securityContext.enabled=false,image.tag=XXX
+```console
+helm upgrade my-release my-repo/consul --set securityContext.enabled=false,image.tag=XXX
 ```
 
 ### To 2.0.0
@@ -514,7 +515,7 @@ 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 consul:
 
 ```console
-$ kubectl delete statefulset consul --cascade=false
+kubectl delete statefulset consul --cascade=false
 ```
 
 ## License
@@ -525,10 +526,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/contour-operator/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ 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
 ```
 
 ## 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/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.
@@ -46,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.
@@ -57,7 +57,7 @@ In the Bitnami catalog we offer both the *bitnami/contour* and *bitnami/contour-
 
 The *bitnami/contour* chart deploys a single Contour installation using a Kubernetes Deployment object (together with Services, PVCs, ConfigMaps, etc.). The figure below shows a simplified view of the deployed objects in the cluster after executing *helm install*:
 
-```
+```text
                     +--------------+                +-------------+
                     |              |                |             |
  Service            |   Contour    |                |    Envoy    |
@@ -78,7 +78,7 @@ Its lifecycle is managed using Helm.
 
 The *bitnami/contour-operator* chart deploys a Contour Operator installation using a Kubernetes Deployment. The figure below shows the Contour Operator deployment after executing *helm install*:
 
-```
+```text
 +--------------------+
 |                    |      +---------------+
 |  Contour Operator  |      |               |
@@ -93,7 +93,7 @@ The *bitnami/contour-operator* chart deploys a Contour Operator installation usi
 
 The operator will extend the Kubernetes API with the *Contour* object, among others. From that moment, the user will be able to deploy objects of these kinds and the previously deployed Operator will take care of deploying all the required Deployments, ConfigMaps and Services for running a Contour instance. Its lifecycle is managed using *kubectl* on the Contour objects. The following figure shows a simplified view of the deployed objects after deploying a *Contour* object using *kubectl*:
 
-```
+```text
   +--------------------+
   |                    |      +---------------+
   |  Contour Operator  |      |               |
@@ -266,7 +266,6 @@ This solution allows to easily deploy multiple Contour instances compared to the
 | `metrics.serviceMonitor.selector`          | Prometheus instance selector labels                                              | `[]`        |
 
 
-See [readme-generator-for-helm](https://github.com/bitnami-labs/readme-generator-for-helm) to create the table.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
@@ -281,7 +280,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)
@@ -384,10 +383,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/contour/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/contour
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/contour
 ```
 
 ## 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/contour
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/contour
 ```
 
 These commands deploy contour on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -47,13 +47,13 @@ These commands deploy contour on the Kubernetes cluster in the default configura
 :warning: Uninstalling this chart will also remove CRDs. Removing CRDs will **remove all instances of it's Custom Resources**. If you wish to retain your Custom Resources for the future, run the following commands before uninstalling.
 
 ```console
-$ kubectl get -o yaml extensionservice,httpproxy,tlscertificatedelegation -A > backup.yaml
+kubectl get -o yaml extensionservice,httpproxy,tlscertificatedelegation -A > backup.yaml
 ```
 
 To uninstall/delete the `my-release` helm release:
 
 ```console
-$ helm uninstall my-release
+helm uninstall my-release
 ```
 
 ## Parameters
@@ -425,7 +425,6 @@ $ helm uninstall my-release
 | `tlsExistingSecret` | Name of the existingSecret to be use in both contour and envoy. If it is not nil `contour.certgen` will be disabled. | `""`   |
 
 
-Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
 $ helm install my-release \
@@ -551,7 +550,7 @@ Find more information about how to deal with common errors related to Bitnami's
 
 ## Upgrading
 
-Please carefully read through the guide "Upgrading Contour" at https://projectcontour.io/resources/upgrading/.
+Please carefully read through the guide "Upgrading Contour" at <https://projectcontour.io/resources/upgrading/>.
 
 ### To 7.0.0
 
@@ -571,7 +570,7 @@ This version updates the chart to use Contour's latest release, `1.19.0`. Among
 
 Additionally, exisiting CRDs have been syncronised with the official [Contour repository](https://github.com/projectcontour/contour/blob/main/examples/render/contour.yaml)
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 If you are installing a fresh chart, you can ignore this section.
 
@@ -579,13 +578,13 @@ If you are upgrading from 5.x of this Helm chart, this is a breaking change as t
 
 ### To 5.2.0
 
-This version bumps the Envoy container from 1.17.X to 1.19.X; this Envoy version is officially supported by Contour since 1.18.0, see https://github.com/projectcontour/contour/releases/tag/v1.18.0
+This version bumps the Envoy container from 1.17.X to 1.19.X; this Envoy version is officially supported by Contour since 1.18.0, see <https://github.com/projectcontour/contour/releases/tag/v1.18.0>
 
 ### To 5.0.0
 
 In this version it was synchronized CRD with the official [Contour repository](https://github.com/projectcontour/contour/blob/main/examples/render/contour.yaml)
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 If you are installing a fresh chart, you can ignore this section.
 
@@ -595,12 +594,12 @@ If you are upgrading from 4.x of this Helm chart, this is a breaking change as t
 
 The 4.0 version of this chart introduces changes to handle Contour CRD upgrades. While Helm 3.x introduced the `crd` folder to place CRDs, Helm explicitly does not handle the [CRD upgrade scenario](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#some-caveats-and-explanations).
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - The `resources` directory was added that contains all the Contour CRDs, which are imported by the `templates/00-crds.yaml` manifest on installation and upgrade.
 - If you do not wish for this chart to manage Contour CRDs, set the flag `contour.manageCRDs` to `false` when running Helm.
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 If you are installing a fresh chart, or if you are upgrading from a 4.x version of this chart, you can ignore this section.
 
@@ -609,51 +608,51 @@ If you are upgrading from 3.x of this Helm chart, this is a breaking change as t
 If required, back up your existing Custom Resources:
 
 ```console
-$ kubectl get -o yaml extensionservice,httpproxy,tlscertificatedelegation -A > backup.yaml
+kubectl get -o yaml extensionservice,httpproxy,tlscertificatedelegation -A > backup.yaml
 ```
 
 Delete the existing Contour CRDs. Note that this step will *also delete* the associated CRs and impact availability until the upgrade is complete and the backup restored:
 
 ```console
-$ kubectl delete extensionservices.projectcontour.io
-$ kubectl delete httpproxies.projectcontour.io
-$ kubectl delete tlscertificatedelegations.projectcontour.io
+kubectl delete extensionservices.projectcontour.io
+kubectl delete httpproxies.projectcontour.io
+kubectl delete tlscertificatedelegations.projectcontour.io
 ```
 
 Upgrade the Contour chart with the release name `my-release`:
 
 ```console
-$ helm upgrade my-release my-repo/contour
+helm upgrade my-release my-repo/contour
 ```
 
 If you made a backup earlier, restore the objects:
 
 ```console
-$ kubectl apply -f backup.yaml
+kubectl apply -f backup.yaml
 ```
 
 ### To 3.0.0
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 2.0.0
 
@@ -664,7 +663,7 @@ Most important changes are:
 - Sync CRDs with [upstream project examples](https://github.com/projectcontour/contour/tree/main/examples/contour). Please remember that helm does not touch existing CRDs. As of today, the most reliable way to update the CRDs is, to do it outside helm (Use `--skip-crds` when using helm v3 and `--set contour.installCRDs=false` when using helm v2). Read [Upgrading Contour](https://projectcontour.io/resources/upgrading/) and execute the following `kubectl` command before helm upgrade:
 
 ```console
-$ kubectl apply -f https://raw.githubusercontent.com/projectcontour/contour/release-{{version}}/examples/contour/01-crds.yaml
+kubectl apply -f https://raw.githubusercontent.com/projectcontour/contour/release-{{version}}/examples/contour/01-crds.yaml
 ```
 
 This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
@@ -677,10 +676,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/discourse/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/discourse
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/discourse
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/discourse
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/discourse
 ```
 
 The command deploys Discourse on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys Discourse 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.
@@ -335,7 +335,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalRedis.existingSecretPasswordKey` | Name of an existing secret key containing the Redis&trade credentials      | `redis-password` |
 
 
-The above parameters map to the env variables defined in [bitnami/discourse](https://github.com/bitnami/containers/tree/main/bitnami/discourse). For more information please refer to the [bitnami/discourse](https://github.com/bitnami/containers/tree/main/bitnami/discourse) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
@@ -352,7 +351,7 @@ The above command sets the Discourse 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/discourse
+helm install my-release -f values.yaml my-repo/discourse
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -378,7 +377,7 @@ $ helm install my-release my-repo/discourse
 ...
 ```
 
-2. Wait for the release to complete and Discourse to be running successfully.
+1. Wait for the release to complete and Discourse to be running successfully.
 
 ```console
 $ kubectl get pods
@@ -388,10 +387,10 @@ my-release-postgresql-0                 1/1     Running   0          5m10s
 my-release-redis-master-0               1/1     Running   0          5m11s
 ```
 
-3. Perform an upgrade specifying the number of replicas and the credentials used.
+1. Perform an upgrade specifying the number of replicas and the credentials used.
 
 ```console
-$ helm upgrade my-release --set replicaCount=2,discourse.skipInstall=true my-repo/discourse
+helm upgrade my-release --set replicaCount=2,discourse.skipInstall=true my-repo/discourse
 ```
 
 Note that for this to work properly, you need to provide ReadWriteMany PVCs. If you don't have a provisioner for this type of storage, we recommend that you install the NFS provisioner chart (with the correct parameters, such as `persistence.enabled=true` and `persistence.size=10Gi`) and map it to a RWO volume.
@@ -509,10 +508,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/dokuwiki/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/dokuwiki
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/dokuwiki
 ```
 
 ## 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/dokuwiki
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/dokuwiki
 ```
 
 The command deploys DokuWiki 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 @@ The command deploys DokuWiki 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.
@@ -243,7 +243,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `certificates.image.pullSecrets`                     | Container sidecar image pull secrets                                                                              | `[]`                                     |
 
 
-The above parameters map to the env variables defined in [bitnami/dokuwiki](https://github.com/bitnami/containers/tree/main/bitnami/dokuwiki). For more information please refer to the [bitnami/dokuwiki](https://github.com/bitnami/containers/tree/main/bitnami/dokuwiki) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
@@ -260,7 +259,7 @@ The above command sets the DokuWiki 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/dokuwiki
+helm install my-release -f values.yaml my-repo/dokuwiki
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -307,7 +306,7 @@ certificates:
 Secret can be created with:
 
 ```console
-$ kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
+kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
 ```
 
 ### TLS Certificate
@@ -332,12 +331,13 @@ certificates:
 The certificate tls secret can be created with:
 
 ```console
-$ kubectl create secret tls my-secret --cert tls.crt --key tls.key
+kubectl create secret tls my-secret --cert tls.crt --key tls.key
 ```
 
 The certificate chain is created with:
+
 ```console
-$ kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
+kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
 ```
 
 ## Troubleshooting
@@ -363,24 +363,24 @@ This version standardizes the way of defining Ingress rules. When configuring a
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 7.0.0
 
@@ -399,7 +399,7 @@ To upgrade to `7.0.0`, backup Drupal data and the previous MariaDB databases, in
 
 Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
 
-In https://github.com/helm/charts/pull/17294 the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
+In <https://github.com/helm/charts/pull/17294> the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
 
 This major version signifies this change.
 
@@ -409,7 +409,7 @@ 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 dokuwiki:
 
 ```console
-$ kubectl patch deployment dokuwiki-dokuwiki --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl patch deployment dokuwiki-dokuwiki --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
 ```
 
 ## Community supported solution
@@ -428,10 +428,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/drupal/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/drupal
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/drupal
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/drupal
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/drupal
 ```
 
 The command deploys Drupal on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys Drupal on the Kubernetes cluster in the default configuratio
 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.
@@ -321,7 +321,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                                 | `{}`    |
 
 
-The above parameters map to the env variables defined in [bitnami/drupal](https://github.com/bitnami/containers/tree/main/bitnami/drupal). For more information please refer to the [bitnami/drupal](https://github.com/bitnami/containers/tree/main/bitnami/drupal) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
@@ -338,7 +337,7 @@ The above command sets the Drupal administrator account username and password to
 Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/drupal
+helm install my-release -f values.yaml my-repo/drupal
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -389,7 +388,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
 1. Install the chart
 
 ```console
-$ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/drupal
+helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/drupal
 ```
 
 ### Host path
@@ -405,7 +404,7 @@ $ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/drupa
 1. Install the chart
 
     ```console
-    $ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/drupal
+    helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/drupal
     ```
 
     This will mount the `drupal-data` volume into the `hostPath` directory. The site data will be persisted if the mount path contains valid data, else the site data will be initialized at first launch.
@@ -420,6 +419,7 @@ Find more information about how to deal with common errors related to Bitnami's
 ### To 12.0.0
 
 This major release bumps the MariaDB version to 10.6. Follow the [upstream instructions](https://mariadb.com/kb/en/upgrading-from-mariadb-105-to-mariadb-106/) for upgrading from MariaDB 10.5 to 10.6. No major issues are expected during the upgrade.
+
 ### To 11.0.0
 
 This major release renames several values in this chart and adds missing features, in order to be inline with the rest of assets in the Bitnami charts repository.
@@ -436,24 +436,24 @@ Additionally also updates the MariaDB subchart to it newest major, 10.0.0, which
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 9.0.0
 
@@ -469,22 +469,22 @@ 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:
 
 ```console
-$ helm upgrade drupal my-repo/drupal --set drupalPassword=$DRUPAL_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 8.2.1
+helm upgrade drupal my-repo/drupal --set drupalPassword=$DRUPAL_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 8.2.1
 ```
 
 Finally, upgrade you release to 9.0.0 reusing the existing PVC, and enabling back MariaDB:
 
 ```console
-$ helm upgrade drupal my-repo/drupal --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set drupalPassword=$DRUPAL_PASSWORD
+helm upgrade drupal my-repo/drupal --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set drupalPassword=$DRUPAL_PASSWORD
 ```
 
 You should see the lines below in MariaDB container logs:
@@ -514,7 +514,7 @@ This upgrade also adapts the chart to the latest Bitnami good practices. Check t
 
 Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
 
-In https://github.com/helm/charts/pull/17295 the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
+In <https://github.com/helm/charts/pull/17295> the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
 
 This major version signifies this change.
 
@@ -524,8 +524,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 drupal:
 
 ```console
-$ kubectl patch deployment drupal-drupal --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl delete statefulset drupal-mariadb --cascade=false
+kubectl patch deployment drupal-drupal --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl delete statefulset drupal-mariadb --cascade=false
 ```
 
 ## Community supported solution
@@ -544,10 +544,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/ejbca/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/ejbca
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/ejbca
 ```
 
 ## 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/ejbca
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/ejbca
 ```
 
 The command deploys EJBCA 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 @@ The command deploys EJBCA on the Kubernetes cluster in the default configuration
 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.
@@ -241,7 +241,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                                | `{}`    |
 
 
-The above parameters map to the env variables defined in [bitnami/ejbca](https://github.com/bitnami/containers/tree/main/bitnami/ejbca). For more information please refer to the [bitnami/ejbca](https://github.com/bitnami/containers/tree/main/bitnami/ejbca) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
@@ -258,7 +257,7 @@ The above command sets the EJBCA administrator account username and password to
 Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/ejbca
+helm install my-release -f values.yaml my-repo/ejbca
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -354,22 +353,22 @@ 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:
 
 ```console
-$ helm upgrade ejbca my-repo/ejbca --set ejbcaAdminPassword=$EJBCA_ADMIN_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 0.4.0
+helm upgrade ejbca my-repo/ejbca --set ejbcaAdminPassword=$EJBCA_ADMIN_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 0.4.0
 ```
 
 Finally, upgrade you release to 1.0.0 reusing the existing PVC, and enabling back MariaDB:
 
 ```console
-$ helm upgrade ejbca my-repo/ejbca --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set ejbcaAdminPassword=$EJBCA_ADMIN_PASSWORD
+helm upgrade ejbca my-repo/ejbca --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set ejbcaAdminPassword=$EJBCA_ADMIN_PASSWORD
 ```
 
 You should see the lines below in MariaDB container logs:
@@ -390,10 +389,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/elasticsearch/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/elasticsearch
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/elasticsearch
 ```
 
 ## 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/elasticsearch
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/elasticsearch
 ```
 
 These commands deploy Elasticsearch on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -45,13 +45,13 @@ These commands deploy Elasticsearch on the Kubernetes cluster in the default con
 To uninstall/delete the `my-release` release:
 
 ```console
-$ helm delete my-release
+helm delete my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release. Remove also the chart using `--purge` option:
 
 ```console
-$ helm delete --purge my-release
+helm delete --purge my-release
 ```
 
 ## Parameters
@@ -640,7 +640,6 @@ $ helm delete --purge my-release
 | `kibana.elasticsearch.port`  | Port to connect Kibana and ES instance. Used to generate the URL          | `{{ include "elasticsearch.service.ports.restAPI" . }}` |
 
 
-Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
 $ helm install my-release \
@@ -653,7 +652,7 @@ The above command sets the Elasticsearch cluster name to `my-elastic` and REST p
 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/elasticsearch
+helm install my-release -f values.yaml my-repo/elasticsearch
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml).
@@ -775,7 +774,6 @@ snapshotRepoPath: "/snapshots"
 
 If you have a need for additional containers to run within the same pod as Elasticsearch components (e.g. an additional metrics or logging exporter), you can do so via the `XXX.sidecars` parameter(s), where XXX is placeholder you need to replace with the actual component(s). Simply define your container according to the Kubernetes container spec.
 
-
 ```yaml
 sidecars:
   - name: your-image-name
@@ -838,10 +836,10 @@ This major release refactors the bitnami/elasticsearch chart, adding some organi
 - Renamed several values to be in line with the rest of the catalog.
 
 This major release also upgrades Elasticsearch to its version 8.x.x and the updates Kibana subchart.
+
 - Upgrade to Elasticsearch 8
 - Upgrade Kibana subchart.
 
-
 In addition, several modifications have been performed adding missing features and renaming values, in order to get aligned with the rest of the assets in the Bitnami charts repository.
 
 The following values have been modified:
@@ -888,30 +886,30 @@ This version standardizes the way of defining Ingress rules in the Kibana subcha
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 12.0.0
 
 Several changes were introduced that breaks backwards compatibility:
 
-- Ports names were prefixed with the protocol to comply with Istio (see https://istio.io/docs/ops/deployment/requirements/).
+- Ports names were prefixed with the protocol to comply with Istio (see <https://istio.io/docs/ops/deployment/requirements/>).
 - Labels are adapted to follow the Helm charts best practices.
 - Elasticsearch data pods are now deployed in parallel in order to bootstrap the cluster and be discovered.
 
@@ -922,8 +920,8 @@ Elasticsearch master pods are now deployed in parallel in order to bootstrap the
 The field `podManagementPolicy` can't be updated in a StatefulSet, so you need to destroy it before you upgrade the chart to this version.
 
 ```console
-$ kubectl delete statefulset elasticsearch-master
-$ helm upgrade <DEPLOYMENT_NAME> my-repo/elasticsearch
+kubectl delete statefulset elasticsearch-master
+helm upgrade <DEPLOYMENT_NAME> my-repo/elasticsearch
 ```
 
 ### TO 10.0.0
@@ -957,11 +955,11 @@ 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 elasticsearch:
 
 ```console
-$ kubectl patch deployment elasticsearch-coordinating --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl patch deployment elasticsearch-ingest --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl patch deployment elasticsearch-master --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl patch deployment elasticsearch-metrics --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl delete statefulset elasticsearch-data --cascade=false
+kubectl patch deployment elasticsearch-coordinating --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl patch deployment elasticsearch-ingest --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl patch deployment elasticsearch-master --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl patch deployment elasticsearch-metrics --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl delete statefulset elasticsearch-data --cascade=false
 ```
 
 ## License
@@ -972,10 +970,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/etcd/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/etcd
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/etcd
 ```
 
 ## 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/etcd
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/etcd
 ```
 
 These commands deploy etcd 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 etcd on the Kubernetes cluster in the default configuratio
 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.
@@ -316,7 +316,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `pdb.maxUnavailable` | Maximum number/percentage of pods that may be made unavailable | `""`   |
 
 
-Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
 $ helm install my-release \
@@ -330,7 +329,7 @@ The above command sets the etcd `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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/etcd
+helm install my-release -f values.yaml my-repo/etcd
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -396,6 +395,7 @@ extraEnvVars:
 Since etcd keeps an exact history of its keyspace, this history should be periodically compacted to avoid performance degradation and eventual storage space exhaustion. Compacting the keyspace history drops all information about keys superseded prior to a given keyspace revision. The space used by these keys then becomes available for additional writes to the keyspace.
 
 `autoCompactionMode`, by default periodic. Valid values: "periodic", "revision".
+
 - 'periodic' for duration based retention, defaulting to hours if no time unit is provided (e.g. "5m").
 - 'revision' for revision number based retention.
 `autoCompactionRetention` for mvcc key value store in hour, by default 0, means disabled.
@@ -526,7 +526,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 etcd:
 
 ```console
-$ kubectl delete statefulset etcd --cascade=false
+kubectl delete statefulset etcd --cascade=false
 ```
 
 ## License
@@ -537,10 +537,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/external-dns/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/external-dns
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/external-dns
 ```
 
 ## Introduction
@@ -31,8 +31,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/external-dns
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/external-dns
 ```
 
 The command deploys ExternalDNS on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -44,7 +44,7 @@ The command deploys ExternalDNS on the Kubernetes cluster in the default configu
 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.
@@ -339,7 +339,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.googlePodMonitor.endpoint`           | The endpoint for Google Managed Prometheus scraping the metrics                                                                                                              | `/metrics`                |
 
 
-Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
 $ helm install my-release \
@@ -349,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/external-dns
+helm install my-release -f values.yaml my-repo/external-dns
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -369,11 +368,14 @@ This chart allows you to set your custom affinity using the `affinity` parameter
 As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
 
 ### Using IRSA
+
 If you are deploying to AWS EKS and you want to leverage [IRSA](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html). You will need to override `fsGroup` and `runAsUser` with `65534`(nfsnobody) and `0` respectively. Otherwise service account token will not be properly mounted.
 You can use the following arguments:
-```
+
+```console
 --set podSecurityContext.fsGroup=65534 --set podSecurityContext.runAsUser=0
 ```
+
 ## Tutorials
 
 Find information about the requirements for each DNS provider on the link below:
@@ -387,6 +389,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.
+
 ```console
 $ helm install my-release \
   --set provider=aws \
@@ -399,6 +402,7 @@ $ helm install my-release \
 ## Troubleshooting
 
 Find more information about how to deal with common errors related to Bitnami's Helm charts in [this troubleshooting guide](https://docs.bitnami.com/general/how-to/troubleshoot-helm-chart-issues).
+
 ## Upgrading
 
 ### To 6.0.0
@@ -415,8 +419,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
@@ -427,22 +431,22 @@ This version also introduces `bitnami/common`, a [library chart](https://helm.sh
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 3.0.0
 
@@ -458,8 +462,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 `my-release`:
 
 ```console
-$ kubectl delete deployment my-release-external-dns
-$ helm upgrade my-release my-repo/external-dns
+kubectl delete deployment my-release-external-dns
+helm upgrade my-release my-repo/external-dns
 ```
 
 Other mayor changes included in this major version are:
@@ -480,10 +484,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/fluentd/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/fluentd
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/fluentd
 ```
 
 ## 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/fluentd
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/fluentd
 ```
 
 These commands deploy Fluentd 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 Fluentd on the Kubernetes cluster in the default configura
 To uninstall/delete the `my-release` resources:
 
 ```console
-$ helm delete my-release
+helm delete my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release. Use the option `--purge` to delete all history too.
@@ -331,7 +331,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `tls.aggregator.existingSecret`                                | Name of the existing secret containing the TLS certificates for the Fluentd aggregator                                                                             | `""`                                                       |
 
 
-Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
 $ helm install my-release \
@@ -343,7 +342,7 @@ The above command sets the aggregators to listen on port 24444.
 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/fluentd
+helm install my-release -f values.yaml my-repo/fluentd
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -360,8 +359,6 @@ Bitnami will release a new chart updating its containers if a new version of the
 
 By default, the aggregators in this chart will send the processed logs to the standard output. However, a common practice is to send them to another service, like Elasticsearch, instead. This can be achieved with this Helm Chart by mounting your own configuration files. For example:
 
-**configmap.yaml**
-
 ```yaml
 apiVersion: v1
 kind: ConfigMap
@@ -530,22 +527,22 @@ This version also introduces `bitnami/common`, a [library chart](https://helm.sh
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
-- The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
+- The different fields present in the _Chart.yaml_ file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 2.0.0
 
@@ -591,10 +588,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/ghost/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/ghost
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/ghost
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/ghost
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/ghost
 ```
 
 The command deploys Ghost on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys Ghost on the Kubernetes cluster in the default configuration
 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.
@@ -277,7 +277,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.annotations`                                  | Annotations for service account. Evaluated as a template. Only used if `create` is `true`.                                | `{}`    |
 
 
-The above parameters map to the env variables defined in [bitnami/ghost](https://github.com/bitnami/containers/tree/main/bitnami/ghost). For more information please refer to the [bitnami/ghost](https://github.com/bitnami/containers/tree/main/bitnami/ghost) image documentation.
 
 > **Note**:
 >
@@ -308,7 +307,7 @@ The above command sets the Ghost administrator account username and password to
 Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/ghost
+helm install my-release -f values.yaml my-repo/ghost
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -387,7 +386,6 @@ Find more information about how to deal with common errors related to Bitnami's
 
 ## Upgrading
 
-
 ### To 19.0.0
 
 This major release changes database management system from MariaDB to MySQL. Since a new DB will be used, you need to create a back up beforehand and restore it in order to keep your data. See [the official migration docs](https://ghost.org/docs/migration/ghost/).
@@ -428,30 +426,30 @@ In this major there were two main changes introduced:
 
 Please read the update notes carefully.
 
-**1. Adaptation to Helm v2 EOL**
+#### 1. Adaptation to Helm v2 EOL
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+##### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+##### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+##### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
-**2. Updated MariaDB dependency version**
+#### 2. Updated MariaDB dependency version**
 
 In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-800) for more information.
 
@@ -462,31 +460,31 @@ To upgrade to `11.0.0`, it should be done reusing the PVCs used to hold both the
 Obtain the credentials and the name of the PVC used to hold the MariaDB data on your current release:
 
 ```console
-$ export GHOST_HOST=$(kubectl get svc --namespace default ghost --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
-$ export GHOST_PASSWORD=$(kubectl get secret --namespace default ghost -o jsonpath="{.data.ghost-password}" | base64 -d)
-$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default ghost-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
-$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default ghost-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
-$ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=ghost -o jsonpath="{.items[0].metadata.name}")
+export GHOST_HOST=$(kubectl get svc --namespace default ghost --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
+export GHOST_PASSWORD=$(kubectl get secret --namespace default ghost -o jsonpath="{.data.ghost-password}" | base64 -d)
+export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default ghost-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
+export MARIADB_PASSWORD=$(kubectl get secret --namespace default ghost-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
+export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=ghost -o jsonpath="{.items[0].metadata.name}")
 ```
 
 Delete the Ghost deployment and delete the MariaDB statefulset. Notice the option `--cascade=false` in the latter.
 
   ```console
-  $ kubectl delete deployments.apps ghost
+  kubectl delete deployments.apps ghost
 
-  $ kubectl delete statefulsets.apps ghost-mariadb --cascade=false
+  kubectl delete statefulsets.apps ghost-mariadb --cascade=false
   ```
 
 Upgrade you release to 11.0.0 reusing the existing PVC, and enabling back MariaDB:
 
 ```console
-$ helm upgrade ghost my-repo/ghost --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set ghostPassword=$GHOST_PASSWORD --set ghostHost=$GHOST_HOST
+helm upgrade ghost my-repo/ghost --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set ghostPassword=$GHOST_PASSWORD --set ghostHost=$GHOST_HOST
 ```
 
 You will need to kill the existing MariaDB pod now as the new statefulset is going to create a new one:
 
 ```console
-$ kubectl delete pod ghost-mariadb-0
+kubectl delete pod ghost-mariadb-0
 ```
 
 You should see the lines below in MariaDB container logs:
@@ -516,7 +514,7 @@ Also, `allowEmptyPassword` has changed its value type from string to boolean, if
 
 Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
 
-In https://github.com/helm/charts/pulls/17297 the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
+In <https://github.com/helm/charts/pulls/17297> the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
 
 This major version signifies this change.
 
@@ -526,8 +524,8 @@ Backwards compatibility is not guaranteed unless you modify the labels used on t
 Use the workaround below to upgrade from versions previous to 5.0.0. The following example assumes that the release name is ghost:
 
 ```console
-$ kubectl patch deployment ghost-ghost --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl delete statefulset ghost-mariadb --cascade=false
+kubectl patch deployment ghost-ghost --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl delete statefulset ghost-mariadb --cascade=false
 ```
 
 ## Community supported solution
@@ -546,10 +544,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/gitea/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/gitea
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/gitea
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/gitea
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/gitea
 ```
 
 The command deploys Gitea on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys Gitea on the Kubernetes cluster in the default configuration
 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.
@@ -249,8 +249,6 @@ 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 \
   --set adminUsername=user,giteaPassword=password,postgresql.auth.rootPassword=secretpassword \
@@ -264,7 +262,7 @@ The above command sets the Gitea administrator account username and password to
 Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/gitea
+helm install my-release -f values.yaml my-repo/gitea
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -315,7 +313,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
 1. Install the chart
 
 ```console
-$ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/gitea
+helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/gitea
 ```
 
 ### Host path
@@ -331,7 +329,7 @@ $ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/gitea
 1. Install the chart
 
     ```console
-    $ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/gitea
+    helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/gitea
     ```
 
     This will mount the `gitea-data` volume into the `hostPath` directory. The site data will be persisted if the mount path contains valid data, else the site data will be initialized at first launch.
@@ -349,10 +347,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/grafana-loki/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ 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
 ```
 
 ## Introduction
@@ -36,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ 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.
@@ -49,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.
@@ -786,7 +786,7 @@ The command removes all the Kubernetes components associated with the chart and
 | `queryScheduler.initContainers`                        | Add additional init containers to the queryScheduler pod(s)                                              | `[]`            |
 
 
-### Query Frontend Traffic Exposure Parameters
+### Query Scheduler Traffic Exposure Parameters
 
 | Name                                              | Description                                                      | Value       |
 | ------------------------------------------------- | ---------------------------------------------------------------- | ----------- |
@@ -1205,7 +1205,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `memcachedindexwrites.service.ports.memcached` | Memcached service port                                                                                    | `11211`               |
 
 
-See https://github.com/bitnami-labs/readme-generator-for-helm to create the table
 
 The above parameters map to the env variables defined in [bitnami/grafana-loki](https://github.com/bitnami/containers/tree/main/bitnami/grafana-loki). For more information please refer to the [bitnami/grafana-loki](https://github.com/bitnami/containers/tree/main/bitnami/grafana-loki) image documentation.
 
@@ -1222,7 +1221,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)
@@ -1234,6 +1233,7 @@ $ helm install my-release -f values.yaml my-repo/grafana-loki
 It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
 
 Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
+
 ### Loki configuration
 
 The loki configuration file `loki.yaml` is shared across the different components: `distributor`, `compactor`, `ingester`, `querier` and `queryFrontend`. This is set in the `loki.configuration` value. Check the official [Loki Grafana documentation](https://grafana.com/docs/loki/latest/configuration/) for the list of possible configurations.
@@ -1331,10 +1331,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/grafana-loki/values.yaml

@@ -2596,7 +2596,7 @@ queryScheduler:
   ##
   initContainers: []
 
-  ## @section Query Frontend Traffic Exposure Parameters
+  ## @section Query Scheduler Traffic Exposure Parameters
   ##
 
   ## queryScheduler service parameters

bitnami/grafana-operator/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/grafana-operator
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/grafana-operator
 ```
 
 ## 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/grafana-operator
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/grafana-operator
 ```
 
 These commands deploy grafana-operator 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 grafana-operator on the Kubernetes cluster in the default
 To uninstall/delete the `my-release` helm release:
 
 ```console
-$ helm uninstall my-release
+helm uninstall my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -72,7 +72,6 @@ For more information, refer to the [documentation on the differences between the
 | `global.imageRegistry`    | Global Docker image registry                    | `""`  |
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                               | Value           |
@@ -86,7 +85,6 @@ For more information, refer to the [documentation on the differences between the
 | `commonAnnotations` | Common Annotations which are applied to every ressource deployed                                          | `{}`            |
 | `clusterDomain`     | Kubernetes cluster domain name                                                                            | `cluster.local` |
 
-
 ### Grafana Operator parameters
 
 | Name                                                         | Description                                                                                                                               | Value                      |
@@ -188,7 +186,6 @@ For more information, refer to the [documentation on the differences between the
 | `operator.startupProbe.failureThreshold`                     | Failure threshold for startupProbe                                                                                                        | `3`                        |
 | `operator.startupProbe.successThreshold`                     | Success threshold for startupProbe                                                                                                        | `1`                        |
 
-
 ### Grafana parameters
 
 | Name                                                        | Description                                                                                                | Value                    |
@@ -272,7 +269,6 @@ For more information, refer to the [documentation on the differences between the
 | `grafana.extraVolumeMounts`                                 | Optionally specify extra list of additional volumeMounts for the grafana container(s)                      | `[]`                     |
 | `grafana.sidecars`                                          | Add additional sidecar containers to the grafana pod(s)                                                    | `[]`                     |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -286,7 +282,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/grafana-operator
+helm install my-release -f values.yaml my-repo/grafana-operator
 ```
 
 ## Configuration and installation details
@@ -316,7 +312,7 @@ Find more information about how to deal with common errors related to Bitnami's
 ## Upgrading
 
 ```console
-$ helm upgrade my-release my-repo/grafana-operator
+helm upgrade my-release my-repo/grafana-operator
 ```
 
 ### To 2.0.0
@@ -372,10 +368,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/grafana-tempo/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ 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
 ```
 
 ## Introduction
@@ -36,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ 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.
@@ -49,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.
@@ -64,7 +64,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value           |
@@ -80,7 +79,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployments/statefulsets                      | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployments/statefulsets                         | `["infinity"]`  |
 
-
 ### Common Grafana Tempo Parameters
 
 | Name                                   | Description                                                                                                   | Value                         |
@@ -112,7 +110,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `tempo.gossipRing.service.ports.http`  | Gossip Ring HTTP headless service port                                                                        | `7946`                        |
 | `tempo.gossipRing.service.annotations` | Additional custom annotations for Gossip Ring headless service                                                | `{}`                          |
 
-
 ### Compactor Deployment Parameters
 
 | Name                                              | Description                                                                                         | Value           |
@@ -174,7 +171,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `compactor.sidecars`                              | Add additional sidecar containers to the Compactor pod(s)                                           | `[]`            |
 | `compactor.initContainers`                        | Add additional init containers to the Compactor pod(s)                                              | `[]`            |
 
-
 ### Compactor Traffic Exposure Parameters
 
 | Name                                         | Description                                                      | Value       |
@@ -191,7 +187,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `compactor.service.annotations`              | Additional custom annotations for Compactor service              | `{}`        |
 | `compactor.service.extraPorts`               | Extra ports to expose in the Compactor service                   | `[]`        |
 
-
 ### Distributor Deployment Parameters
 
 | Name                                                | Description                                                                                           | Value           |
@@ -252,7 +247,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `distributor.sidecars`                              | Add additional sidecar containers to the Distributor pod(s)                                           | `[]`            |
 | `distributor.initContainers`                        | Add additional init containers to the Distributor pod(s)                                              | `[]`            |
 
-
 ### Distributor Traffic Exposure Parameters
 
 | Name                                           | Description                                                      | Value       |
@@ -271,7 +265,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `distributor.service.annotations`              | Additional custom annotations for Distributor service            | `{}`        |
 | `distributor.service.extraPorts`               | Extra ports to expose in the Distributor service                 | `[]`        |
 
-
 ### Metrics Generator Deployment Parameters
 
 | Name                                                     | Description                                                                                                | Value           |
@@ -334,7 +327,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metricsGenerator.sidecars`                              | Add additional sidecar containers to the metricsGenerator pod(s)                                           | `[]`            |
 | `metricsGenerator.initContainers`                        | Add additional init containers to the metricsGenerator pod(s)                                              | `[]`            |
 
-
 ### Metrics Generator Traffic Exposure Parameters
 
 | Name                                                | Description                                                      | Value       |
@@ -352,7 +344,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metricsGenerator.service.annotations`              | Additional custom annotations for metricsGenerator service       | `{}`        |
 | `metricsGenerator.service.extraPorts`               | Extra ports to expose in the metricsGenerator service            | `[]`        |
 
-
 ### Ingester Deployment Parameters
 
 | Name                                             | Description                                                                                        | Value           |
@@ -413,7 +404,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingester.sidecars`                              | Add additional sidecar containers to the Ingester pod(s)                                           | `[]`            |
 | `ingester.initContainers`                        | Add additional init containers to the Ingester pod(s)                                              | `[]`            |
 
-
 ### Ingester Persistence Parameters
 
 | Name                                 | Description                                                             | Value               |
@@ -427,7 +417,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingester.persistence.annotations`   | Additional PVC annotations                                              | `{}`                |
 | `ingester.persistence.selector`      | Selector to match an existing Persistent Volume for Ingester's data PVC | `{}`                |
 
-
 ### Ingester Traffic Exposure Parameters
 
 | Name                                        | Description                                                      | Value       |
@@ -446,7 +435,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingester.service.annotations`              | Additional custom annotations for Ingester service               | `{}`        |
 | `ingester.service.extraPorts`               | Extra ports to expose in the Ingester service                    | `[]`        |
 
-
 ### Querier Deployment Parameters
 
 | Name                                            | Description                                                                                       | Value           |
@@ -507,7 +495,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `querier.sidecars`                              | Add additional sidecar containers to the Querier pod(s)                                           | `[]`            |
 | `querier.initContainers`                        | Add additional init containers to the Querier pod(s)                                              | `[]`            |
 
-
 ### Querier Traffic Exposure Parameters
 
 | Name                                       | Description                                                      | Value       |
@@ -526,7 +513,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `querier.service.annotations`              | Additional custom annotations for Querier service                | `{}`        |
 | `querier.service.extraPorts`               | Extra ports to expose in the Querier service                     | `[]`        |
 
-
 ### Query Frontend Deployment Parameters
 
 | Name                                                        | Description                                                                                                         | Value                         |
@@ -630,7 +616,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `queryFrontend.query.resources.requests`                    | The requested resources for the query sidecar containers                                                            | `{}`                          |
 | `queryFrontend.query.extraVolumeMounts`                     | Optionally specify extra list of additional volumeMounts for the queryFrontend container(s)                         | `[]`                          |
 
-
 ### Query Frontend Traffic Exposure Parameters
 
 | Name                                             | Description                                                      | Value       |
@@ -649,7 +634,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `queryFrontend.service.annotations`              | Additional custom annotations for queryFrontend service          | `{}`        |
 | `queryFrontend.service.extraPorts`               | Extra ports to expose in the queryFrontend service               | `[]`        |
 
-
 ### Vulture Deployment Parameters
 
 | Name                                            | Description                                                                                                     | Value                           |
@@ -718,7 +702,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `vulture.sidecars`                              | Add additional sidecar containers to the Vulture pod(s)                                                         | `[]`                            |
 | `vulture.initContainers`                        | Add additional init containers to the Vulture pod(s)                                                            | `[]`                            |
 
-
 ### Vulture Traffic Exposure Parameters
 
 | Name                                       | Description                                                      | Value       |
@@ -735,7 +718,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `vulture.service.annotations`              | Additional custom annotations for Vulture service                | `{}`        |
 | `vulture.service.extraPorts`               | Extra ports to expose in the Vulture service                     | `[]`        |
 
-
 ### Init Container Parameters
 
 | Name                                                   | Description                                                                                                   | Value                   |
@@ -751,7 +733,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.requests`                 | The requested resources for the init container                                                                | `{}`                    |
 | `volumePermissions.containerSecurityContext.runAsUser` | Set init container's Security Context runAsUser                                                               | `0`                     |
 
-
 ### Other Parameters
 
 | Name                                          | Description                                                            | Value   |
@@ -761,7 +742,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.automountServiceAccountToken` | Allows auto mount of ServiceAccountToken on the serviceAccount created | `true`  |
 | `serviceAccount.annotations`                  | Additional custom annotations for the ServiceAccount                   | `{}`    |
 
-
 ### Metrics Parameters
 
 | Name                                       | Description                                                                           | Value   |
@@ -778,7 +758,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.serviceMonitor.honorLabels`       | Specify honorLabels parameter to add the scrape endpoint                              | `false` |
 | `metrics.serviceMonitor.jobLabel`          | The name of the label on the target service to use as the job name in prometheus.     | `""`    |
 
-
 ### External Memcached Parameters
 
 | Name                     | Description                                   | Value   |
@@ -786,7 +765,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalMemcached.host` | Host of a running external memcached instance | `""`    |
 | `externalMemcached.port` | Port of a running external memcached instance | `11211` |
 
-
 ### Memcached Sub-chart Parameters
 
 | Name                                | Description                     | Value   |
@@ -797,8 +775,7 @@ The command removes all the Kubernetes components associated with the chart and
 | `memcached.auth.password`           | Memcached admin password        | `""`    |
 | `memcached.service.ports.memcached` | Memcached service port          | `11211` |
 
-
-See https://github.com/bitnami-labs/readme-generator-for-helm to create the table
+See <https://github.com/bitnami-labs/readme-generator-for-helm> to create the table
 
 The above parameters map to the env variables defined in [bitnami/grafana-tempo](https://github.com/bitnami/containers/tree/main/bitnami/grafana-tempo). For more information please refer to the [bitnami/grafana-tempo](https://github.com/bitnami/containers/tree/main/bitnami/grafana-tempo) image documentation.
 
@@ -815,7 +792,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)
@@ -827,6 +804,7 @@ $ helm install my-release -f values.yaml my-repo/grafana-tempo
 It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
 
 Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
+
 ### Tempo configuration
 
 The tempo configuration file `tempo.yaml` is shared across the different components: `distributor`, `compactor`, `ingester`, `querier` and `queryFrontend`. This is set in the `tempo.configuration` value. Check the official [Tempo Grafana documentation](https://grafana.com/docs/tempo/latest/configuration/) for the list of possible configurations.
@@ -918,10 +896,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/grafana/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/grafana
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/grafana
 ```
 
 ## 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/grafana
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/grafana
 ```
 
 These commands deploy grafana 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 grafana 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. Use the option `--purge` to delete all persistent volumes too.
@@ -57,7 +57,7 @@ In the Bitnami catalog we offer both the bitnami/grafana and bitnami/grafana-ope
 
 The *bitnami/grafana* chart deploys a single Grafana installation (with grafana-image-renderer) using a Kubernetes Deployment object (together with Services, PVCs, ConfigMaps, etc.). The figure below shows the deployed objects in the cluster after executing *helm install*:
 
-```
+```text
                     +--------------+             +-----+
                     |              |             |     |
  Service & Ingress  |    Grafana   +<------------+ PVC |
@@ -78,7 +78,7 @@ Its lifecycle is managed using Helm and, at the Grafana container level, the fol
 
 The *bitnami/grafana-operator* chart deploys a Grafana Operator installation using a Kubernetes Deployment.  The figure below shows the Grafana operator deployment after executing *helm install*:
 
-```
+```text
 +--------------------+
 |                    |      +---------------+
 |  Grafana Operator  |      |               |
@@ -95,7 +95,7 @@ The *bitnami/grafana-operator* chart deploys a Grafana Operator installation usi
 The operator will extend the Kubernetes API with the following objects: *Grafana*, *GrafanaDashboards* and *GrafanaDataSources*. From that moment, the user will be able to deploy objects of these kinds and the previously deployed Operator will take care of deploying all the required Deployments, ConfigMaps and Services for running a Grafana instance. Its lifecycle is managed using *kubectl* on the Grafana, GrafanaDashboards and GrafanaDataSource objects. The following figure shows the deployed objects after
  deploying a *Grafana* object using *kubectl*:
 
-```
+```text
 +--------------------+
 |                    |      +---------------+
 |  Grafana Operator  |      |               |
@@ -144,7 +144,6 @@ This solution allows to easily deploy multiple Grafana instances compared to the
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                             | Value           |
@@ -157,7 +156,6 @@ This solution allows to easily deploy multiple Grafana instances compared to the
 | `commonLabels`      | Labels to add to all deployed objects                                                   | `{}`            |
 | `commonAnnotations` | Annotations to add to all deployed objects                                              | `{}`            |
 
-
 ### Grafana parameters
 
 | Name                               | Description                                                                                                                                          | Value                             |
@@ -213,7 +211,6 @@ This solution allows to easily deploy multiple Grafana instances compared to the
 | `datasources.secretDefinition`     | The contents of a secret defining a custom datasource file. Only used if datasources.secretName is empty or not defined.                             | `{}`                              |
 | `notifiers.configMapName`          | Name of a ConfigMap containing Grafana notifiers configuration                                                                                       | `""`                              |
 
-
 ### Grafana Deployment parameters
 
 | Name                                         | Description                                                                                             | Value           |
@@ -283,7 +280,6 @@ This solution allows to easily deploy multiple Grafana instances compared to the
 | `grafana.command`                            | Override default container command (useful when using custom images)                                    | `[]`            |
 | `grafana.args`                               | Override default container args (useful when using custom images)                                       | `[]`            |
 
-
 ### Persistence parameters
 
 | Name                        | Description                                                                                               | Value           |
@@ -296,7 +292,6 @@ This solution allows to easily deploy multiple Grafana instances compared to the
 | `persistence.existingClaim` | If you want to reuse an existing claim, you can pass the name of the PVC using the existingClaim variable | `""`            |
 | `persistence.size`          | Size for the PV                                                                                           | `10Gi`          |
 
-
 ### RBAC parameters
 
 | Name                                          | Description                                                                                                           | Value   |
@@ -306,7 +301,6 @@ This solution allows to easily deploy multiple Grafana instances compared to the
 | `serviceAccount.annotations`                  | Annotations to add to the ServiceAccount Metadata                                                                     | `{}`    |
 | `serviceAccount.automountServiceAccountToken` | Automount service account token for the application controller service account                                        | `false` |
 
-
 ### Traffic exposure parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -338,7 +332,6 @@ This solution allows to easily deploy multiple Grafana instances compared to the
 | `ingress.ingressClassName`         | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Metrics parameters
 
 | Name                                       | Description                                                                                                                               | Value   |
@@ -360,7 +353,6 @@ This solution allows to easily deploy multiple Grafana instances compared to the
 | `metrics.prometheusRule.additionalLabels`  | Additional labels that can be used so PrometheusRule will be discovered by Prometheus                                                     | `{}`    |
 | `metrics.prometheusRule.rules`             | PrometheusRule rules to configure                                                                                                         | `[]`    |
 
-
 ### Grafana Image Renderer parameters
 
 | Name                                                     | Description                                                                                                                               | Value                            |
@@ -435,7 +427,6 @@ This solution allows to easily deploy multiple Grafana instances compared to the
 | `imageRenderer.args`                                     | Override default container args (useful when using custom images)                                                                         | `[]`                             |
 | `imageRenderer.lifecycleHooks`                           | for the Grafana Image Renderer container(s) to automate configuration before or after startup                                             | `{}`                             |
 
-
 ### Volume permissions init Container Parameters
 
 | Name                                                   | Description                                                                                                   | Value                   |
@@ -451,7 +442,6 @@ This solution allows to easily deploy multiple Grafana instances compared to the
 | `volumePermissions.resources.requests`                 | The requested resources for the init container                                                                | `{}`                    |
 | `volumePermissions.containerSecurityContext.runAsUser` | Set init container's Security Context runAsUser                                                               | `0`                     |
 
-
 ### Diagnostic Mode Parameters
 
 | Name                     | Description                                                                             | Value          |
@@ -460,7 +450,6 @@ This solution allows to easily deploy multiple Grafana instances compared to the
 | `diagnosticMode.command` | Command to override all containers in the deployment                                    | `["sleep"]`    |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                       | `["infinity"]` |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -475,7 +464,7 @@ The above command sets the Grafana admin user to `admin-user`.
 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/grafana
+helm install my-release -f values.yaml my-repo/grafana
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -506,6 +495,7 @@ And now you need to pass the ConfigMap name, to the corresponding parameters: `c
 
 To provide dashboards on deployment time, Grafana needs a dashboards provider and the dashboards themselves.
 A default provider is created if enabled, or you can mount your own provider using a ConfigMap, but have in mind that the path to the dashboard folder must be `/opt/bitnami/grafana/dashboards`.
+
   1. To create a dashboard, it is needed to have a datasource for it. The datasources must be created mounting a secret with all the datasource files in it. In this case, it is not a ConfigMap because the datasource could contain sensitive information.
   2. To load the dashboards themselves you need to create a ConfigMap for each one containing the `json` file that defines the dashboard and set the array with the ConfigMap names into the `dashboardsConfigMaps` parameter.
 Note the difference between the datasources and the dashboards creation. For the datasources we can use just one secret with all of the files, while for the dashboards we need one ConfigMap per file.
@@ -513,14 +503,13 @@ Note the difference between the datasources and the dashboards creation. For the
 For example, create the dashboard ConfigMap(s) and datasource Secret as described below:
 
 ```console
-$ kubectl create secret generic datasource-secret --from-file=datasource-secret.yaml
-$ kubectl create configmap my-dashboard-1 --from-file=my-dashboard-1.json
-$ kubectl create configmap my-dashboard-2 --from-file=my-dashboard-2.json
+kubectl create secret generic datasource-secret --from-file=datasource-secret.yaml
+kubectl create configmap my-dashboard-1 --from-file=my-dashboard-1.json
+kubectl create configmap my-dashboard-2 --from-file=my-dashboard-2.json
 ```
 
 > Note: the commands above assume you had previously exported your dashboards in the JSON files: *my-dashboard-1.json* and *my-dashboard-2.json*
-
-> Note: the commands above assume you had previously created a datasource config file *datasource-secret.yaml*. Find an example at https://grafana.com/docs/grafana/latest/administration/provisioning/#example-datasource-config-file
+> Note: the commands above assume you had previously created a datasource config file *datasource-secret.yaml*. Find an example at <https://grafana.com/docs/grafana/latest/administration/provisioning/#example-datasource-config-file>
 
 Once you have them, use the following parameters to deploy Grafana with 2 custom dashboards:
 
@@ -627,7 +616,7 @@ Find more information about how to deal with common errors related to Bitnami's
 
 ### To 8.0.0
 
-This major release only bumps the Grafana version to 9.x. No major issues are expected during the upgrade. See the upstream changelog https://grafana.com/docs/grafana/latest/release-notes/release-notes-9-0-0/ for more info about the changes included in this new major version of the application
+This major release only bumps the Grafana version to 9.x. No major issues are expected during the upgrade. See the upstream changelog <https://grafana.com/docs/grafana/latest/release-notes/release-notes-9-0-0/> for more info about the changes included in this new major version of the application
 
 ### To 7.0.0
 
@@ -636,8 +625,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
@@ -648,28 +637,28 @@ This version also introduces `bitnami/common`, a [library chart](https://helm.sh
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 3.0.0
 
 Deployment label selector is immutable after it gets created, so you cannot "upgrade".
 
-In https://github.com/bitnami/charts/pull/2773 the deployment label selectors of the resources were updated to add the component name. Resulting in compatibility breakage.
+In <https://github.com/bitnami/charts/pull/2773> the deployment label selectors of the resources were updated to add the component name. Resulting in compatibility breakage.
 
 In order to "upgrade" from a previous version, you will need to [uninstall](#uninstalling-the-chart) the existing chart manually.
 
@@ -683,10 +672,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/haproxy/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/haproxy
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/haproxy
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ 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.
@@ -48,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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value           |
@@ -79,7 +78,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                    | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                       | `["infinity"]`  |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -109,7 +107,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.ingressClassName`         | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### HAProxy Parameters
 
 | Name                                    | Description                                                                                             | Value                |
@@ -186,7 +183,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `sidecars`                              | Add additional sidecar containers to the haproxy pod(s)                                                 | `[]`                 |
 | `initContainers`                        | Add additional init containers to the haproxy pod(s)                                                    | `[]`                 |
 
-
 ### Other Parameters
 
 | Name                                          | Description                                                                                                         | Value  |
@@ -198,7 +194,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.create`                       | Specifies whether a ServiceAccount should be created                                                                | `true` |
 | `serviceAccount.name`                         | The name of the ServiceAccount to use.                                                                              | `""`   |
 
-
 The above parameters map to the env variables defined in [bitnami/haproxy](https://github.com/bitnami/containers/tree/main/bitnami/haproxy). For more information please refer to the [bitnami/haproxy](https://github.com/bitnami/containers/tree/main/bitnami/haproxy) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -216,7 +211,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)
@@ -233,8 +228,8 @@ Bitnami will release a new chart updating its containers if a new version of the
 
 By default, HAProxy is deployed with a sample, non-functional, configuration. You will need to edit the following values to adapt it to your use case:
 
-* Set the configuration to be injected in the `haproxy.cfg` file by changing the `configuration` parameter. Alternatively, you can provide an existing ConfigMap with `haproxy.cfg` by using the `existingConfigmap` parameter.
-* Based on your HAProxy configuration, edit the `containerPorts` and `service.ports` parameters. In the `containerPorts` parameter, set all the ports that the HAProxy configuration uses, and in the `service.ports` parameter, set the ports to be externally exposed.
+- Set the configuration to be injected in the `haproxy.cfg` file by changing the `configuration` parameter. Alternatively, you can provide an existing ConfigMap with `haproxy.cfg` by using the `existingConfigmap` parameter.
+- Based on your HAProxy configuration, edit the `containerPorts` and `service.ports` parameters. In the `containerPorts` parameter, set all the ports that the HAProxy configuration uses, and in the `service.ports` parameter, set the ports to be externally exposed.
 
 Refer to the [chart documentation for a more detailed configuration example](https://docs.bitnami.com/kubernetes/infrastructure/haproxy/get-started/configure-proxy).
 
@@ -274,10 +269,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/harbor/README.md

@@ -6,13 +6,11 @@ Harbor is an open source trusted cloud-native registry to store, sign, and scan
 
 [Overview of Harbor](https://goharbor.io/)
 
-
-
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/harbor
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/harbor
 ```
 
 ## Introduction
@@ -45,8 +43,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/harbor
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/harbor
 ```
 
 ## Uninstalling the Chart
@@ -54,7 +52,7 @@ $ helm install my-release my-repo/harbor
 To uninstall/delete the `my-release` deployment:
 
 ```console
-$ helm delete --purge my-release
+helm delete --purge my-release
 ```
 
 Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manually delete the PVCs.
@@ -69,7 +67,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common Parameters
 
 | Name                     | Description                                                                                  | Value           |
@@ -85,7 +82,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `diagnosticMode.command` | Command to override all containers in the the deployment(s)/statefulset(s)                   | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the the deployment(s)/statefulset(s)                      | `["infinity"]`  |
 
-
 ### Harbor common parameters
 
 | Name                         | Description                                                                                                                                          | Value                                  |
@@ -102,7 +98,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `ipFamily.ipv6.enabled`      | Enable listening on IPv6 ([::]) for NGINX-based components (NGINX,portal)                                                                            | `true`                                 |
 | `ipFamily.ipv4.enabled`      | Enable listening on IPv4 for NGINX-based components (NGINX,portal)                                                                                   | `true`                                 |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -150,7 +145,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `ingress.notary.secrets`           | Custom TLS certificates as secrets                                                                                               | `[]`                     |
 | `ingress.notary.extraRules`        | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Persistence Parameters
 
 | Name                                                                  | Description                                                                                                                                                                                                                                                                                                                                          | Value                                    |
@@ -249,7 +243,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `persistence.imageChartStorage.oss.rootdirectory`                     | OSS storage type setting: Directory                                                                                                                                                                                                                                                                                                                  | `""`                                     |
 | `persistence.imageChartStorage.oss.secretkey`                         | OSS storage type setting: Secret key                                                                                                                                                                                                                                                                                                                 | `""`                                     |
 
-
 ### Tracing parameters
 
 | Name                       | Description                                                                                                                                                              | Value           |
@@ -273,7 +266,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `tracing.otel.timeout`     | The timeout for data transfer                                                                                                                                            | `10s`           |
 | `tracing.otel.insecure`    | Ignore cert verification for otel backend                                                                                                                                | `true`          |
 
-
 ### Volume Permissions parameters
 
 | Name                                                   | Description                                                                                                                       | Value                   |
@@ -290,7 +282,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `volumePermissions.containerSecurityContext.enabled`   | Enable init container Security Context                                                                                            | `true`                  |
 | `volumePermissions.containerSecurityContext.runAsUser` | User ID for the init container                                                                                                    | `0`                     |
 
-
 ### NGINX Parameters
 
 | Name                                          | Description                                                                                                              | Value                  |
@@ -364,7 +355,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `nginx.extraVolumeMounts`                     | Optionally specify extra list of additional volumeMounts for the NGINX pods                                              | `[]`                   |
 | `nginx.extraVolumes`                          | Optionally specify extra list of additional volumes for the NGINX pods                                                   | `[]`                   |
 
-
 ### Harbor Portal Parameters
 
 | Name                                           | Description                                                                                                              | Value                   |
@@ -437,7 +427,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `portal.service.ports.http`                    | Harbor Portal HTTP service port                                                                                          | `80`                    |
 | `portal.service.ports.https`                   | Harbor Portal HTTPS service port                                                                                         | `443`                   |
 
-
 ### Harbor Core Parameters
 
 | Name                                         | Description                                                                                                                                                                                                                                                                              | Value                 |
@@ -522,7 +511,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `core.service.ports.https`                   | Harbor Core HTTPS service port                                                                                                                                                                                                                                                           | `443`                 |
 | `core.service.ports.metrics`                 | Harbor Core metrics service port                                                                                                                                                                                                                                                         | `8001`                |
 
-
 ### Harbor Jobservice Parameters
 
 | Name                                               | Description                                                                                                                                                  | Value                          |
@@ -602,12 +590,11 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `jobservice.service.ports.https`                   | Harbor Jobservice HTTPS service port                                                                                                                         | `443`                          |
 | `jobservice.service.ports.metrics`                 | Harbor Jobservice HTTPS service port                                                                                                                         | `8001`                         |
 
-
 ### Harbor Registry Parameters
 
 | Name                                                        | Description                                                                                                                                                                                                                                                               | Value                                                                               |
 | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
-| `registry.secret`                                           | Secret is used to secure the upload state from client and registry storage backend. See: https://github.com/docker/distribution/blob/master/docs/configuration.md                                                                                                         | `""`                                                                                |
+| `registry.secret`                                           | Secret is used to secure the upload state from client and registry storage backend. See: <https://github.com/docker/distribution/blob/master/docs/configuration.md>                                                                                                         | `""`                                                                                |
 | `registry.existingSecret`                                   | Existing secret for registry                                                                                                                                                                                                                                              | `""`                                                                                |
 | `registry.relativeurls`                                     | Make the registry return relative URLs in Location headers. The client is responsible for resolving the correct URL.                                                                                                                                                      | `false`                                                                             |
 | `registry.credentials.username`                             | The username for accessing the registry instance, which is hosted by htpasswd auth mode.  More details see [official docs](https://github.com/docker/distribution/blob/master/docs/configuration.md#htpasswd)                                                             | `harbor_registry_user`                                                              |
@@ -735,7 +722,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `registry.controller.service.ports.http`                    | Harbor Registryctl HTTP service port                                                                                                                                                                                                                                      | `8080`                                                                              |
 | `registry.controller.service.ports.https`                   | Harbor Registryctl HTTPS service port                                                                                                                                                                                                                                     | `8443`                                                                              |
 
-
 ### ChartMuseum Parameters
 
 | Name                                                | Description                                                                                                              | Value                  |
@@ -826,7 +812,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `chartmuseum.service.ports.http`                    | Chartmuseum HTTP service port                                                                                            | `80`                   |
 | `chartmuseum.service.ports.https`                   | Chartmuseum HTTPS service port                                                                                           | `443`                  |
 
-
 ### Notary Parameters
 
 | Name                                                  | Description                                                                                                                                                                                                                                                                                                                                    | Value                          |
@@ -962,7 +947,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `notary.service.ports.server`                         | Harbor Notary server service port                                                                                                                                                                                                                                                                                                              | `4443`                         |
 | `notary.service.ports.signer`                         | Harbor Notary signer service port                                                                                                                                                                                                                                                                                                              | `7899`                         |
 
-
 ### Harbor Adapter Trivy Parameters
 
 | Name                                          | Description                                                                                                              | Value                                  |
@@ -1044,7 +1028,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `trivy.service.ports.http`                    | Trivy HTTP service port                                                                                                  | `8080`                                 |
 | `trivy.service.ports.https`                   | Trivy HTTPS service port                                                                                                 | `8443`                                 |
 
-
 ### Harbor Exporter Parameters
 
 | Name                                             | Description                                                                                                                                     | Value                     |
@@ -1115,7 +1098,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `exporter.automountServiceAccountToken`          | Automount service account token                                                                                                                 | `false`                   |
 | `exporter.service.ports.metrics`                 | Exporter HTTP service port                                                                                                                      | `8001`                    |
 
-
 ### PostgreSQL Parameters
 
 | Name                                       | Description                                                                                                | Value                          |
@@ -1145,7 +1127,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `externalDatabase.notarySignerUsername`    | External database username for notary signer                                                               | `""`                           |
 | `externalDatabase.notarySignerPassword`    | External database password for notary signer                                                               | `""`                           |
 
-
 ### Redis&reg; parameters
 
 | Name                                      | Description                                                            | Value        |
@@ -1170,7 +1151,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `externalRedis.sentinel.masterSet`        | Name of sentinel masterSet if sentinel is used                         | `mymaster`   |
 | `externalRedis.sentinel.hosts`            | Sentinel hosts and ports in the format                                 | `""`         |
 
-
 ### Harbor metrics parameters
 
 | Name                                       | Description                                                                                       | Value      |
@@ -1188,7 +1168,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `metrics.serviceMonitor.honorLabels`       | Specify honorLabels parameter to add the scrape endpoint                                          | `false`    |
 | `metrics.serviceMonitor.jobLabel`          | The name of the label on the target service to use as the job name in prometheus.                 | `""`       |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -1204,7 +1183,7 @@ The above command sets the Harbor administrator account password to `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/harbor
+helm install my-release -f values.yaml my-repo/harbor
 ```
 
 ## Configuration and installation details
@@ -1339,10 +1318,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/influxdb/README.md

@@ -11,8 +11,8 @@ InfluxDB(TM) is a trademark owned by InfluxData, which is not affiliated with, a
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/influxdb
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/influxdb
 ```
 
 ## 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/influxdb
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/influxdb
 ```
 
 These commands deploy influxdb 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 influxdb on the Kubernetes cluster in the default configur
 To uninstall/delete the `my-release` statefulset:
 
 ```console
-$ helm delete my-release
+helm delete my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release. Use the option `--purge` to delete all history too.
@@ -61,7 +61,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global storage class for dynamic provisioning   | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                           | Value           |
@@ -77,7 +76,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                                  | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                                     | `["infinity"]`  |
 
-
 ### InfluxDB™ parameters
 
 | Name                                             | Description                                                                                                                                                                                                                                                          | Value                 |
@@ -180,7 +178,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `influxdb.service.sessionAffinity`               | Session Affinity for Kubernetes service, can be "None" or "ClientIP"                                                                                                                                                                                                 | `None`                |
 | `influxdb.service.sessionAffinityConfig`         | Additional settings for the sessionAffinity                                                                                                                                                                                                                          | `{}`                  |
 
-
 ### InfluxDB Collectd™ parameters
 
 | Name                                        | Description                                                                               | Value       |
@@ -198,7 +195,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `collectd.service.sessionAffinity`          | Session Affinity for Kubernetes service, can be "None" or "ClientIP"                      | `None`      |
 | `collectd.service.sessionAffinityConfig`    | Additional settings for the sessionAffinity                                               | `{}`        |
 
-
 ### Exposing parameters
 
 | Name                       | Description                                                                                                                      | Value                    |
@@ -217,7 +213,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.ingressClassName` | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `ingress.extraRules`       | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Metrics parameters
 
 | Name                                          | Description                                                                                                                                 | Value               |
@@ -257,7 +252,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `psp.create`                                  | Whether to create a PodSecurityPolicy. WARNING: PodSecurityPolicy is deprecated in Kubernetes v1.21 or later, unavailable in v1.25 or later | `false`             |
 | `rbac.create`                                 | Create Role and RoleBinding (required for PSP to work)                                                                                      | `false`             |
 
-
 ### Volume permissions parameters
 
 | Name                                          | Description                                                                                                                       | Value                   |
@@ -271,7 +265,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.image.pullSecrets`         | Specify docker-registry secret names as an array                                                                                  | `[]`                    |
 | `volumePermissions.securityContext.runAsUser` | User ID for the init container (when facing issues in OpenShift or uid unknown, try value "auto")                                 | `0`                     |
 
-
 ### InfluxDB™ backup parameters
 
 | Name                                              | Description                                                                                                      | Value                      |
@@ -328,7 +321,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `backup.uploadProviders.aws.image.pullPolicy`     | AWS CLI image pull policy                                                                                        | `IfNotPresent`             |
 | `backup.uploadProviders.aws.image.pullSecrets`    | Specify docker-registry secret names as an array                                                                 | `[]`                       |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -343,7 +335,7 @@ The above command sets the InfluxDB™ admin user to `admin-user`.
 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/influxdb
+helm install my-release -f values.yaml my-repo/influxdb
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -444,7 +436,7 @@ Find more information about how to deal with common errors related to Bitnami's
 
 ## Upgrade
 
-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:
+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:
 
 ```console
 $ helm upgrade my-release my-repo/influxdb \
@@ -465,8 +457,8 @@ This major release completely removes support for InfluxDB Relay™ because
 To update from the previous major, please follow this steps:
 
 ```
-$ kubectl delete deployments.apps influxdb
-$ helm upgrade influxdb my-repo/influxdb
+kubectl delete deployments.apps influxdb
+helm upgrade influxdb my-repo/influxdb
 ```
 
 ### To 4.0.0
@@ -494,10 +486,10 @@ Affected values:
 This version adds support to InfluxDB™ +2.0, since this version the chart is only verified to work with InfluxDB™ +2.0 bitnami images.
 However, you can use images for versions ~1.x.x taking into account the chart may need some modification to run with them.
 
-#### Installing InfluxDB™ v1 in chart v2.
+#### Installing InfluxDB™ v1 in chart v2
 
 ```
-$ helm install my-repo/influxdb --set image.tag=1.8.3-debian-10-r88
+helm install my-repo/influxdb --set image.tag=1.8.3-debian-10-r88
 ```
 
 As a consecuece some breaking changes have been included in this version.
@@ -516,20 +508,20 @@ Since this release could mean lot of concepts changes, we strongly recommend to
 
 We actually recommend to backup all the data form a previous helm release, install new release using latest version of the chart and images and then restore data following their guides.
 
-#### Upgrading the chart form 1.x.x to 2.x.x using InfluxDB™ v1 images.
+#### Upgrading the chart form 1.x.x to 2.x.x using InfluxDB™ v1 images
 
 > NOTE: Please, create a backup of your database before running any of those actions.
 
 Having an already existing chart release called `influxdb` and deployed like
 
 ```console
-$ helm install influxdb my-repo/influxdb
+helm install influxdb my-repo/influxdb
 ```
 
 ##### Export secrets and required values to update
 
 ```console
-$ export INFLUXDB_ADMIN_PASSWORD=$(kubectl get secret --namespace default influxdb -o jsonpath="{.data.admin-user-password}" | base64 -d)
+export INFLUXDB_ADMIN_PASSWORD=$(kubectl get secret --namespace default influxdb -o jsonpath="{.data.admin-user-password}" | base64 -d)
 ```
 
 ##### Upgrade the chart release
@@ -549,22 +541,22 @@ This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - The different fields present in the _Chart.yaml_ file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ## License
 
@@ -574,9 +566,9 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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
+See the License for the specific language governing permissions and

bitnami/jaeger/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/jaeger
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/jaeger
 ```
 
 ## 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/jaeger
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/jaeger
 ```
 
 These commands deploy jaeger 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 jaeger on the Kubernetes cluster in the default configurat
 To uninstall/delete the `my-release` statefulset:
 
 ```console
-$ helm delete my-release
+helm delete my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release. Use the option `--purge` to delete all history too.
@@ -61,7 +61,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value          |
@@ -75,7 +74,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                    | `["sleep"]`    |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                       | `["infinity"]` |
 
-
 ### Jaeger parameters
 
 | Name                | Description                                                                                            | Value                 |
@@ -88,7 +86,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `image.pullSecrets` | Jaeger image pull secrets                                                                              | `[]`                  |
 | `image.debug`       | Enable image debug mode                                                                                | `false`               |
 
-
 ### Query deployment parameters
 
 | Name                                                | Description                                                                               | Value           |
@@ -168,7 +165,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `query.initContainers`                              | Add additional init containers to the jaeger pods                                         | `[]`            |
 | `query.sidecars`                                    | Add additional sidecar containers to the jaeger pods                                      | `[]`            |
 
-
 ### Collector deployment parameters
 
 | Name                                                    | Description                                                                                | Value           |
@@ -254,7 +250,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `collector.initContainers`                              | Add additional init containers to the jaeger pods                                          | `[]`            |
 | `collector.sidecars`                                    | Add additional sidecar containers to the jaeger pods                                       | `[]`            |
 
-
 ### agent deployment parameters
 
 | Name                                                | Description                                                                                                    | Value           |
@@ -355,7 +350,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `migration.resources.requests`                      | The requested resources for Jaeger containers                                                                  | `{}`            |
 | `migration.extraVolumes`                            | Optionally specify extra list of additional volumes for jaeger container                                       | `[]`            |
 
-
 ### Set the image to use for the migration job
 
 | Name                                         | Description                                                                                               | Value                 |
@@ -376,7 +370,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.cluster.datacenter`        | Name for cassandra's jaeger datacenter                                                                    | `dc1`                 |
 | `externalDatabase.keyspace`                  | Name for cassandra's jaeger keyspace                                                                      | `bitnami_jaeger`      |
 
-
 ### Cassandra storage sub-chart
 
 | Name                           | Description                                             | Value            |
@@ -388,7 +381,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `cassandra.dbUser.password`    | Password for `dbUser.user`. Randomly generated if empty | `""`             |
 | `cassandra.service.ports.cql`  | Cassandra cql port                                      | `9042`           |
 
-
 > **Tip**: You can use the default [values.yaml](values.yaml)
 
 ## Configuration and installation details
@@ -464,10 +456,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/jasperreports/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/jasperreports
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/jasperreports
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/jasperreports
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/jasperreports
 ```
 
 The command deploys JasperReports on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys JasperReports 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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                          | Value           |
@@ -76,7 +75,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `clusterDomain`     | Default Kubernetes cluster domain                                    | `cluster.local` |
 | `extraDeploy`       | Array of extra objects to deploy with the release                    | `[]`            |
 
-
 ### JasperReports parameters
 
 | Name                    | Description                                                                                                   | Value                   |
@@ -104,7 +102,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsSecret`    | Name of existing Secret containing extra env vars                                                             | `""`                    |
 | `updateStrategy.type`   | StrategyType                                                                                                  | `RollingUpdate`         |
 
-
 ### Jasperreports deployment parameters
 
 | Name                                    | Description                                                                               | Value                      |
@@ -167,7 +164,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `persistence.existingClaim`             | An Existing PVC name for Jasperreports volume                                             | `""`                       |
 | `persistence.annotations`               | Persistent Volume Claim annotations                                                       | `{}`                       |
 
-
 ### Exposure parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -197,7 +193,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.ingressClassName`         | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Database parameters
 
 | Name                                        | Description                                                               | Value                   |
@@ -222,7 +217,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.database`                 | Name of the existing database                                             | `bitnami_jasperreports` |
 | `externalDatabase.type`                     | Type of the existing database, allowed values: mariadb, mysql, postgresql | `mariadb`               |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                          | Description                                                                                                                       | Value   |
@@ -240,7 +234,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.denyConnectionsToExternal`         | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                                    | `false` |
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                                        | `{}`    |
 
-
 The above parameters map to the env variables defined in [bitnami/jasperreports](https://github.com/bitnami/containers/tree/main/bitnami/jasperreports). For more information please refer to the [bitnami/jasperreports](https://github.com/bitnami/containers/tree/main/bitnami/jasperreports) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -258,7 +251,7 @@ The above command sets the JasperReports administrator account username and pass
 Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/jasperreports
+helm install my-release -f values.yaml my-repo/jasperreports
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -369,11 +362,11 @@ Consequences:
 - Backwards compatibility is not guaranteed. However, you can easily workaround this issue by removing JasperReports deployment before upgrading (the following example assumes that the release name is `jasperreports`):
 
 ```console
-$ export JASPER_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)
-$ kubectl delete deployments.apps jasperreports
-$ helm upgrade jasperreports my-repo/jasperreports --set jasperreportsPassword=$JASPER_PASSWORD,mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD,mariadb.auth.password=$MARIADB_PASSWORD
+export JASPER_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)
+kubectl delete deployments.apps jasperreports
+helm upgrade jasperreports my-repo/jasperreports --set jasperreportsPassword=$JASPER_PASSWORD,mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD,mariadb.auth.password=$MARIADB_PASSWORD
 ```
 
 ### To 9.0.0
@@ -385,30 +378,30 @@ In this major there were two main changes introduced:
 
 Please read the update notes carefully.
 
-**1. Adaptation to Helm v2 EOL**
+#### 1. Adaptation to Helm v2 EOL
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+##### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+##### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+##### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
-**2. Updated MariaDB dependency version**
+#### 2. Updated MariaDB dependency version
 
 In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-800) for more information.
 
@@ -419,30 +412,30 @@ 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:
 
 ```console
-  $ kubectl delete deployments.apps jasperreports
+  kubectl delete deployments.apps jasperreports
 
-  $ kubectl delete statefulsets.apps jasperreports-mariadb --cascade=false
+  kubectl delete statefulsets.apps jasperreports-mariadb --cascade=false
 ```
 
 Now the upgrade works:
 
 ```console
-$ helm upgrade jasperreports my-repo/jasperreports --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set jasperreportsPassword=$JASPERREPORTS_PASSWORD --set allowEmptyPasswords=false
+helm upgrade jasperreports my-repo/jasperreports --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set jasperreportsPassword=$JASPERREPORTS_PASSWORD --set allowEmptyPasswords=false
 ```
 
 You will have to delete the existing MariaDB pod and the new statefulset is going to create a new one
 
   ```console
-  $ kubectl delete pod jasperreports-mariadb-0
+  kubectl delete pod jasperreports-mariadb-0
   ```
 
 Finally, you should see the lines below in MariaDB container logs:
@@ -463,7 +456,7 @@ JasperReports 7.5.0 includes some new configuration options that are required to
 
 Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
 
-In https://github.com/helm/charts/pull/17298 the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
+In <https://github.com/helm/charts/pull/17298> the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
 
 This major version signifies this change.
 
@@ -473,8 +466,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 jasperreports:
 
 ```console
-$ kubectl patch deployment jasperreports-jasperreports --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl delete statefulset jasperreports-mariadb --cascade=false
+kubectl patch deployment jasperreports-jasperreports --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl delete statefulset jasperreports-mariadb --cascade=false
 ```
 
 ## Community supported solution
@@ -493,10 +486,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/jenkins/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## 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.
@@ -61,7 +61,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value           |
@@ -77,7 +76,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                    | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                       | `["infinity"]`  |
 
-
 ### Jenkins Image parameters
 
 | Name                | Description                                                                                             | Value                  |
@@ -90,7 +88,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `image.pullSecrets` | Jenkins image pull secrets                                                                              | `[]`                   |
 | `image.debug`       | Enable image debug mode                                                                                 | `false`                |
 
-
 ### Jenkins Configuration parameters
 
 | Name                    | Description                                                            | Value                   |
@@ -107,7 +104,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsCM`        | Name of existing ConfigMap containing extra env vars                   | `""`                    |
 | `extraEnvVarsSecret`    | Name of existing Secret containing extra env vars                      | `""`                    |
 
-
 ### Jenkins deployment parameters
 
 | Name                                    | Description                                                                               | Value           |
@@ -164,7 +160,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `customLivenessProbe`                   | Custom livenessProbe that overrides the default one                                       | `{}`            |
 | `customReadinessProbe`                  | Custom readinessProbe that overrides the default one                                      | `{}`            |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -197,7 +192,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.ingressClassName`         | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Persistence Parameters
 
 | Name                                          | Description                                                                                                   | Value                   |
@@ -220,7 +214,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.requests`        | The requested resources for the init container                                                                | `{}`                    |
 | `volumePermissions.securityContext.runAsUser` | Set init container's Security Context runAsUser                                                               | `0`                     |
 
-
 The above parameters map to the env variables defined in [bitnami/jenkins](https://github.com/bitnami/containers/tree/main/bitnami/jenkins). For more information please refer to the [bitnami/jenkins](https://github.com/bitnami/containers/tree/main/bitnami/jenkins) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -239,7 +232,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)
@@ -315,6 +308,7 @@ This major release is no longer contains the metrics section because the contain
 This major release renames several values in this chart and adds missing features, in order to be inline with the rest of assets in the Bitnami charts repository.
 
 Affected values:
+
 - `service.port` renamed as `service.ports.http`.
 - `service.httpsPort` renamed as `service.ports.https`.
 - `serviceMonitor.additionalLabels` renamed as `serviceMonitor.labels`.
@@ -329,15 +323,15 @@ Upgrading from version `7.x.x` should be possible following the workaround below
 - Remove Jenkins deployment:
 
 ```console
-$ export JENKINS_PASSWORD=$(kubectl get secret --namespace default jenkins -o jsonpath="{.data.jenkins-password}" | base64 -d)
-$ kubectl delete deployments.apps jenkins
+export JENKINS_PASSWORD=$(kubectl get secret --namespace default jenkins -o jsonpath="{.data.jenkins-password}" | base64 -d)
+kubectl delete deployments.apps jenkins
 ```
 
 - Upgrade your release and delete data that should not be persisted anymore:
 
 ```console
-$ helm upgrade jenkins my-repo/jenkins --set jenkinsPassword=$JENKINS_PASSWORD --set jenkinsHome=/bitnami/jenkins/jenkins_home
-$ kubectl exec -it $(kubectl get pod -l app.kubernetes.io/instance=jenkins,app.kubernetes.io/name=jenkins -o jsonpath="{.items[0].metadata.name}") -- find /bitnami/jenkins -mindepth 1 -maxdepth 1 -not -name jenkins_home -exec rm -rf {} \;
+helm upgrade jenkins my-repo/jenkins --set jenkinsPassword=$JENKINS_PASSWORD --set jenkinsHome=/bitnami/jenkins/jenkins_home
+kubectl exec -it $(kubectl get pod -l app.kubernetes.io/instance=jenkins,app.kubernetes.io/name=jenkins -o jsonpath="{.items[0].metadata.name}") -- find /bitnami/jenkins -mindepth 1 -maxdepth 1 -not -name jenkins_home -exec rm -rf {} \;
 ```
 
 ### To 7.0.0
@@ -349,9 +343,9 @@ Consequences:
 - Backwards compatibility is not guaranteed. However, you can easily workaround this issue by removing Jenkins deployment before upgrading (the following example assumes that the release name is `jenkins`):
 
 ```console
-$ export JENKINS_PASSWORD=$(kubectl get secret --namespace default jenkins -o jsonpath="{.data.jenkins-password}" | base64 -d)
-$ kubectl delete deployments.apps jenkins
-$ helm upgrade jenkins my-repo/jenkins --set jenkinsPassword=$JENKINS_PASSWORD
+export JENKINS_PASSWORD=$(kubectl get secret --namespace default jenkins -o jsonpath="{.data.jenkins-password}" | base64 -d)
+kubectl delete deployments.apps jenkins
+helm upgrade jenkins my-repo/jenkins --set jenkinsPassword=$JENKINS_PASSWORD
 ```
 
 ### To 6.1.0
@@ -390,7 +384,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
@@ -401,10 +395,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/joomla/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/joomla
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/joomla
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/joomla
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/joomla
 ```
 
 The command deploys Joomla! on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys Joomla! 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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                                | Value |
@@ -76,7 +75,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `commonLabels`      | Common labels to add to all Harbor resources (sub-charts are not considered). Evaluated as a template      | `{}`  |
 | `extraDeploy`       | Array of extra objects to deploy with the release (evaluated as a template).                               | `[]`  |
 
-
 ### Joomla! parameters
 
 | Name                                    | Description                                                                                                          | Value                |
@@ -162,7 +160,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `podAnnotations`                        | Pod annotations                                                                                                      | `{}`                 |
 | `podLabels`                             | Add additional labels to the pod (evaluated as a template)                                                           | `{}`                 |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -194,7 +191,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.ingressClassName`         | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Database parameters
 
 | Name                                        | Description                                                                                                                                                                       | Value            |
@@ -218,7 +214,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.password`                 | Password for the above username                                                                                                                                                   | `""`             |
 | `externalDatabase.database`                 | Name of the existing database                                                                                                                                                     | `bitnami_joomla` |
 
-
 ### Metrics parameters
 
 | Name                        | Description                                                                                                     | Value                     |
@@ -233,7 +228,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.resources`         | Exporter resource requests/limit                                                                                | `{}`                      |
 | `metrics.podAnnotations`    | Additional annotations for Metrics exporter pod                                                                 | `{}`                      |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                          | Description                                                                                                                | Value   |
@@ -254,7 +248,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.denyConnectionsToExternal`         | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                             | `false` |
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                                 | `{}`    |
 
-
 The above parameters map to the env variables defined in [bitnami/joomla](https://github.com/bitnami/containers/tree/main/bitnami/joomla). For more information please refer to the [bitnami/joomla](https://github.com/bitnami/containers/tree/main/bitnami/joomla) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -272,7 +265,7 @@ The above command sets the Joomla! administrator account username and password t
 Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/joomla
+helm install my-release -f values.yaml my-repo/joomla
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -386,30 +379,30 @@ In this major there were two main changes introduced:
 
 Please read the update notes carefully.
 
-**1. Adaptation to Helm v2 EOL**
+#### 1. Adaptation to Helm v2 EOL
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+##### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+##### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+##### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
-**2. Updated MariaDB dependency version**
+#### 2. Updated MariaDB dependency version
 
 In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-800) for more information.
 
@@ -420,22 +413,22 @@ 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:
 
 ```console
-$ helm upgrade joomla my-repo/joomla --set joomlaPassword=$JOOMLA_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 8.1.9
+helm upgrade joomla my-repo/joomla --set joomlaPassword=$JOOMLA_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 8.1.9
 ```
 
 Finally, upgrade you release to 9.0.0 reusing the existing PVC, and enabling back MariaDB:
 
 ```console
-$ helm upgrade joomla my-repo/joomla --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set joomlaPassword=$JOOMLA_PASSWORD
+helm upgrade joomla my-repo/joomla --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set joomlaPassword=$JOOMLA_PASSWORD
 ```
 
 You should see the lines below in MariaDB container logs:
@@ -465,7 +458,7 @@ This upgrade also adapts the chart to the latest Bitnami good practices. Check t
 
 Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
 
-In https://github.com/helm/charts/pull/17299 the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
+In <https://github.com/helm/charts/pull/17299> the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
 
 This major version signifies this change.
 
@@ -475,8 +468,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 opencart:
 
 ```console
-$ kubectl patch deployment joomla-joomla --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl delete statefulset joomla-mariadb --cascade=false
+kubectl patch deployment joomla-joomla --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl delete statefulset joomla-mariadb --cascade=false
 ```
 
 ## Community supported solution
@@ -495,10 +488,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/jupyterhub/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/jupyterhub
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/jupyterhub
 ```
 
 ## Introduction
@@ -36,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/jupyterhub
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/jupyterhub
 ```
 
 These commands deploy JupyterHub on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -49,7 +49,7 @@ These commands deploy JupyterHub on the Kubernetes cluster in the default config
 To uninstall/delete the `my-release` helm release:
 
 ```console
-$ helm uninstall my-release
+helm uninstall my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -64,7 +64,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value           |
@@ -80,7 +79,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the the deployment(s)/daemonset(s)                | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the the deployment(s)/daemonset(s)                   | `["infinity"]`  |
 
-
 ### Hub deployment parameters
 
 | Name                                        | Description                                                                                                              | Value                |
@@ -157,7 +155,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `hub.pdb.minAvailable`                      | Set minimum available hub instances                                                                                      | `""`                 |
 | `hub.pdb.maxUnavailable`                    | Set maximum available hub instances                                                                                      | `""`                 |
 
-
 ### Hub RBAC parameters
 
 | Name                                              | Description                                                            | Value  |
@@ -169,7 +166,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `hub.rbac.create`                                 | Specifies whether RBAC resources should be created                     | `true` |
 | `hub.rbac.rules`                                  | Custom RBAC rules to set                                               | `[]`   |
 
-
 ### Hub Traffic Exposure Parameters
 
 | Name                                      | Description                                                      | Value       |
@@ -190,7 +186,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `hub.service.annotations`                 | Additional custom annotations for Hub service                    | `{}`        |
 | `hub.service.extraPorts`                  | Extra port to expose on Hub service                              | `[]`        |
 
-
 ### Hub Metrics parameters
 
 | Name                                           | Description                                                                                 | Value          |
@@ -208,7 +203,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `hub.metrics.serviceMonitor.honorLabels`       | Specify honorLabels parameter to add the scrape endpoint                                    | `false`        |
 | `hub.metrics.serviceMonitor.jobLabel`          | The name of the label on the target service to use as the job name in prometheus.           | `""`           |
 
-
 ### Proxy deployment parameters
 
 | Name                                          | Description                                                                                                              | Value                             |
@@ -283,7 +277,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `proxy.pdb.minAvailable`                      | Set minimum available proxy instances                                                                                    | `""`                              |
 | `proxy.pdb.maxUnavailable`                    | Set maximum available proxy instances                                                                                    | `""`                              |
 
-
 ### Proxy Traffic Exposure Parameters
 
 | Name                                             | Description                                                                                                                      | Value                    |
@@ -340,7 +333,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `proxy.ingress.secrets`                          | Custom TLS certificates as secrets                                                                                               | `[]`                     |
 | `proxy.ingress.extraRules`                       | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Proxy Metrics parameters
 
 | Name                                             | Description                                                                                 | Value      |
@@ -357,7 +349,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `proxy.metrics.serviceMonitor.honorLabels`       | Specify honorLabels parameter to add the scrape endpoint                                    | `false`    |
 | `proxy.metrics.serviceMonitor.jobLabel`          | The name of the label on the target service to use as the job name in prometheus.           | `""`       |
 
-
 ### Image puller deployment parameters
 
 | Name                                                | Description                                                                                                              | Value           |
@@ -401,7 +392,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `imagePuller.initContainers`                        | Add additional init containers to the ImagePuller pods                                                                   | `[]`            |
 | `imagePuller.sidecars`                              | Add additional sidecar containers to the ImagePuller pod                                                                 | `[]`            |
 
-
 ### Singleuser deployment parameters
 
 | Name                                            | Description                                                                                                 | Value                                |
@@ -434,7 +424,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `singleuser.initContainers`                     | Add additional init containers to the Single User pods                                                      | `[]`                                 |
 | `singleuser.sidecars`                           | Add additional sidecar containers to the Single User pod                                                    | `[]`                                 |
 
-
 ### Single User RBAC parameters
 
 | Name                                                     | Description                                                            | Value  |
@@ -444,7 +433,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `singleuser.serviceAccount.automountServiceAccountToken` | Allows auto mount of ServiceAccountToken on the serviceAccount created | `true` |
 | `singleuser.serviceAccount.annotations`                  | Additional custom annotations for the ServiceAccount                   | `{}`   |
 
-
 ### Single User Persistence parameters
 
 | Name                                  | Description                                                | Value               |
@@ -454,7 +442,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `singleuser.persistence.accessModes`  | Persistent Volumes access modes                            | `["ReadWriteOnce"]` |
 | `singleuser.persistence.size`         | Persistent Volumes size                                    | `10Gi`              |
 
-
 ### Traffic exposure parameters
 
 | Name                                                | Description                                              | Value   |
@@ -465,7 +452,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `singleuser.networkPolicy.extraIngress`             | Add extra ingress rules to the NetworkPolicy             | `""`    |
 | `singleuser.networkPolicy.extraEgress`              | Add extra egress rules to the NetworkPolicy              | `""`    |
 
-
 ### Auxiliary image parameters
 
 | Name                         | Description                                                                                               | Value                   |
@@ -477,7 +463,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `auxiliaryImage.pullPolicy`  | Auxiliary image pull policy                                                                               | `IfNotPresent`          |
 | `auxiliaryImage.pullSecrets` | Auxiliary image pull secrets                                                                              | `[]`                    |
 
-
 ### JupyterHub database parameters
 
 | Name                                         | Description                                                             | Value                |
@@ -497,7 +482,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.existingSecret`            | Name of an existing secret resource containing the database credentials | `""`                 |
 | `externalDatabase.existingSecretPasswordKey` | Name of an existing secret key containing the database credentials      | `""`                 |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -511,7 +495,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/jupyterhub
+helm install my-release -f values.yaml my-repo/jupyterhub
 ```
 
 ## Configuration and installation details
@@ -559,10 +543,10 @@ Learn more about [configuring and using Ingress in the chart documentation](http
 
 This chart facilitates the creation of TLS secrets for use with the Ingress controller (although this is not mandatory). There are four common use cases:
 
-* Helm generates/manages certificate secrets based on the parameters.
-* User generates/manages certificates separately.
-* Helm creates self-signed certificates and generates/manages certificate secrets.
-* An additional tool (like [cert-manager](https://github.com/jetstack/cert-manager/)) manages the secrets for the application.
+- Helm generates/manages certificate secrets based on the parameters.
+- User generates/manages certificates separately.
+- Helm creates self-signed certificates and generates/manages certificate secrets.
+- An additional tool (like [cert-manager](https://github.com/jetstack/cert-manager/)) manages the secrets for the application.
 
 Refer to the [chart documentation for more information on working with TLS](https://docs.bitnami.com/kubernetes/infrastructure/jupyterhub/administration/enable-tls-ingress/).
 
@@ -596,10 +580,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/kafka/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## 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.
@@ -60,7 +60,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value           |
@@ -76,7 +75,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the statefulset                                   | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the statefulset                                      | `["infinity"]`  |
 
-
 ### Kafka parameters
 
 | Name                                              | Description                                                                                                                                                                         | Value                               |
@@ -161,7 +159,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsCM`                                  | ConfigMap with extra environment variables                                                                                                                                          | `""`                                |
 | `extraEnvVarsSecret`                              | Secret with extra environment variables                                                                                                                                             | `""`                                |
 
-
 ### Statefulset parameters
 
 | Name                                                | Description                                                                                                                                                                                   | Value           |
@@ -230,7 +227,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `pdb.minAvailable`                                  | Maximum number/percentage of unavailable Kafka replicas                                                                                                                                       | `""`            |
 | `pdb.maxUnavailable`                                | Maximum number/percentage of unavailable Kafka replicas                                                                                                                                       | `1`             |
 
-
 ### Traffic Exposure parameters
 
 | Name                                              | Description                                                                                                              | Value                 |
@@ -257,7 +253,7 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalAccess.autoDiscovery.image.registry`     | Init container auto-discovery image registry                                                                             | `docker.io`           |
 | `externalAccess.autoDiscovery.image.repository`   | Init container auto-discovery image repository                                                                           | `bitnami/kubectl`     |
 | `externalAccess.autoDiscovery.image.tag`          | Init container auto-discovery image tag (immutable tags are recommended)                                                 | `1.25.6-debian-11-r1` |
-| `externalAccess.autoDiscovery.image.digest`       | Petete image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag                   | `""`                  |
+| `externalAccess.autoDiscovery.image.digest`       | Kubectl image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag                  | `""`                  |
 | `externalAccess.autoDiscovery.image.pullPolicy`   | Init container auto-discovery image pull policy                                                                          | `IfNotPresent`        |
 | `externalAccess.autoDiscovery.image.pullSecrets`  | Init container auto-discovery image pull secrets                                                                         | `[]`                  |
 | `externalAccess.autoDiscovery.resources.limits`   | The resources limits for the auto-discovery init container                                                               | `{}`                  |
@@ -282,7 +278,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.externalAccess.from`               | customize the from section for External Access on tcp-external port                                                      | `[]`                  |
 | `networkPolicy.egressRules.customRules`           | Custom network policy rule                                                                                               | `{}`                  |
 
-
 ### Persistence parameters
 
 | Name                           | Description                                                                                                                            | Value                     |
@@ -305,7 +300,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `logPersistence.selector`      | Selector to match an existing Persistent Volume for Kafka log data PVC. If set, the PVC can't have a PV dynamically provisioned for it | `{}`                      |
 | `logPersistence.mountPath`     | Mount path of the Kafka logs volume                                                                                                    | `/opt/bitnami/kafka/logs` |
 
-
 ### Volume Permissions parameters
 
 | Name                                                   | Description                                                                                                                       | Value                   |
@@ -321,7 +315,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.requests`                 | Init container volume-permissions resource requests                                                                               | `{}`                    |
 | `volumePermissions.containerSecurityContext.runAsUser` | User ID for the init container                                                                                                    | `0`                     |
 
-
 ### Other Parameters
 
 | Name                                          | Description                                                                                    | Value   |
@@ -332,7 +325,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.annotations`                  | Additional custom annotations for the ServiceAccount                                           | `{}`    |
 | `rbac.create`                                 | Whether to create & use RBAC resources or not                                                  | `false` |
 
-
 ### Metrics parameters
 
 | Name                                                        | Description                                                                                                                      | Value                                                                                   |
@@ -421,7 +413,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRule.labels`                             | Additional labels that can be used so PrometheusRule will be discovered by Prometheus                                            | `{}`                                                                                    |
 | `metrics.prometheusRule.groups`                             | Prometheus Rule Groups for Kafka                                                                                                 | `[]`                                                                                    |
 
-
 ### Kafka provisioning parameters
 
 | Name                                                       | Description                                                                                                                   | Value                 |
@@ -474,7 +465,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `provisioning.initContainers`                              | Add additional Add init containers to the Kafka provisioning pod(s)                                                           | `[]`                  |
 | `provisioning.waitForKafka`                                | If true use an init container to wait until kafka is ready before starting provisioning                                       | `true`                |
 
-
 ### ZooKeeper chart parameters
 
 | Name                                    | Description                                                                                                                                                             | Value               |
@@ -492,7 +482,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `zookeeper.persistence.size`            | Persistent Volume size                                                                                                                                                  | `8Gi`               |
 | `externalZookeeper.servers`             | List of external zookeeper servers to use. Typically used in combination with 'zookeeperChrootPath'.                                                                    | `[]`                |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -506,7 +495,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 +552,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.
@@ -574,6 +563,7 @@ If, for some reason (like using Cert-Manager) you can not use the default JKS se
 - `auth.tls.jksTruststoreSecret` to define additional secret, where the `kafka.truststore.jks` is being kept. The truststore password **must** be the same as in `auth.tls.password`
 - `auth.tls.jksTruststore` to overwrite the default value of the truststore key (`kafka.truststore.jks`).
 - `auth.tls.jksKeystoreSAN` if you want to use a SAN certificate for your brokers. Setting this parameter would mean that the chart expects a existing key in the `auth.tls.jksTruststoreSecret` with the `auth.tls.jksKeystoreSAN` value and use this as a keystore for **all** brokers
+
 > **Note**: If you are using cert-manager, particularly when an ACME issuer is used, the `ca.crt` field is not put in the `Secret` that cert-manager creates. To handle this, the `auth.tls.pemChainIncluded` property can be set to `true` and the initContainer created by this Chart will attempt to extract the intermediate certs from the `tls.crt` field of the secret (which is a PEM chain)
 
 > **Note**: The truststore/keystore from above **must** be protected with the same password as in `auth.tls.password`
@@ -920,24 +910,24 @@ This version also introduces `bitnami/common`, a [library chart](https://helm.sh
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 11.8.0
 
@@ -997,7 +987,7 @@ Backwards compatibility is not guaranteed you adapt your values.yaml to the new
 + metrics.jmx.existingConfigmap
 ```
 
-Ports names were prefixed with the protocol to comply with Istio (see https://istio.io/docs/ops/deployment/requirements/).
+Ports names were prefixed with the protocol to comply with Istio (see <https://istio.io/docs/ops/deployment/requirements/>).
 
 ### To 8.0.0
 
@@ -1009,8 +999,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 +1009,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 +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 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
@@ -1041,10 +1031,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/kafka/values.yaml

@@ -755,7 +755,7 @@ externalAccess:
     ## @param externalAccess.autoDiscovery.image.registry Init container auto-discovery image registry
     ## @param externalAccess.autoDiscovery.image.repository Init container auto-discovery image repository
     ## @param externalAccess.autoDiscovery.image.tag Init container auto-discovery image tag (immutable tags are recommended)
-    ## @param externalAccess.autoDiscovery.image.digest Petete image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag
+    ## @param externalAccess.autoDiscovery.image.digest Kubectl image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag
     ## @param externalAccess.autoDiscovery.image.pullPolicy Init container auto-discovery image pull policy
     ## @param externalAccess.autoDiscovery.image.pullSecrets Init container auto-discovery image pull secrets
     ##

bitnami/keycloak/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## 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
@@ -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/keycloak
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/keycloak
 ```
 
 These commands deploy a Keycloak application on the Kubernetes cluster in the default configuration.
@@ -46,7 +46,7 @@ These commands deploy a Keycloak application on the Kubernetes cluster in the de
 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.
@@ -61,7 +61,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value           |
@@ -78,7 +77,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the the statefulset                               | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the the statefulset                                  | `["infinity"]`  |
 
-
 ### Keycloak parameters
 
 | Name                             | Description                                                                                                                  | Value                         |
@@ -122,7 +120,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsCM`                 | Name of existing ConfigMap containing extra env vars                                                                         | `""`                          |
 | `extraEnvVarsSecret`             | Name of existing Secret containing extra env vars                                                                            | `""`                          |
 
-
 ### Keycloak statefulset parameters
 
 | Name                                    | Description                                                                                                              | Value           |
@@ -183,7 +180,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `initContainers`                        | Add additional init containers to the Keycloak pods                                                                      | `[]`            |
 | `sidecars`                              | Add additional sidecar containers to the Keycloak pods                                                                   | `[]`            |
 
-
 ### Exposure parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -221,7 +217,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.allowExternal`      | Don't require client label for connections                                                                                       | `true`                   |
 | `networkPolicy.additionalRules`    | Additional NetworkPolicy rules                                                                                                   | `{}`                     |
 
-
 ### RBAC parameter
 
 | Name                                          | Description                                               | Value   |
@@ -234,7 +229,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `rbac.create`                                 | Whether to create and use RBAC resources or not           | `false` |
 | `rbac.rules`                                  | Custom RBAC rules                                         | `[]`    |
 
-
 ### Other parameters
 
 | Name                       | Description                                                    | Value   |
@@ -248,7 +242,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `autoscaling.targetCPU`    | Target CPU utilization percentage                              | `""`    |
 | `autoscaling.targetMemory` | Target Memory utilization percentage                           | `""`    |
 
-
 ### Metrics parameters
 
 | Name                                       | Description                                                                                                               | Value   |
@@ -274,7 +267,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRule.labels`            | Additional labels that can be used so PrometheusRule will be discovered by Prometheus                                     | `{}`    |
 | `metrics.prometheusRule.groups`            | Groups, containing the alert rules.                                                                                       | `[]`    |
 
-
 ### keycloak-config-cli parameters
 
 | Name                                                      | Description                                                                                                                   | Value                         |
@@ -311,7 +303,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `keycloakConfigCli.configuration`                         | keycloak-config-cli realms configuration                                                                                      | `{}`                          |
 | `keycloakConfigCli.existingConfigmap`                     | ConfigMap with keycloak-config-cli configuration. This will override `keycloakConfigCli.config`                               | `""`                          |
 
-
 ### Database parameters
 
 | Name                                         | Description                                                                                                       | Value              |
@@ -331,7 +322,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.existingSecret`            | Name of an existing secret resource containing the database credentials                                           | `""`               |
 | `externalDatabase.existingSecretPasswordKey` | Name of an existing secret key containing the database credentials                                                | `""`               |
 
-
 ### Keycloak Cache parameters
 
 | Name              | Description                                                                | Value        |
@@ -340,7 +330,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `cache.stackName` | Set infinispan cache stack to use                                          | `kubernetes` |
 | `cache.stackFile` | Set infinispan cache stack filename to use                                 | `""`         |
 
-
 ### Keycloak Logging parameters
 
 | Name             | Description                                                                    | Value     |
@@ -348,11 +337,10 @@ The command removes all the Kubernetes components associated with the chart and
 | `logging.output` | Alternates between the default log output format or json format                | `default` |
 | `logging.level`  | Allowed values as documented: FATAL, ERROR, WARN, INFO, DEBUG, TRACE, ALL, OFF | `INFO`    |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
-$ helm install my-release --set auth.adminPassword=secretpassword my-repo/keycloak
+helm install my-release --set auth.adminPassword=secretpassword my-repo/keycloak
 ```
 
 The above command sets the Keycloak administrator password to `secretpassword`.
@@ -362,7 +350,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/keycloak
+helm install my-release -f values.yaml my-repo/keycloak
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -455,9 +443,9 @@ If your ingress controller has the SSL Termination, you should set `proxy` to `e
 
 This chart provides several ways to manage passwords:
 
-* Values passed to the chart
-* An existing secret with all the passwords (via the `existingSecret` parameter)
-* Multiple existing secrets with all the passwords (via the `existingSecretPerPassword` parameter)
+- Values passed to the chart
+- An existing secret with all the passwords (via the `existingSecret` parameter)
+- Multiple existing secrets with all the passwords (via the `existingSecretPerPassword` parameter)
 
 Refer to the [chart documentation on managing passwords](https://docs.bitnami.com/kubernetes/apps/keycloak/configuration/manage-passwords/) for examples of each method.
 
@@ -483,10 +471,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/kiam/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## 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.
@@ -35,8 +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 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
 ```
 
 These commands deploy a kiam application on the Kubernetes cluster in the default configuration.
@@ -48,7 +48,7 @@ These commands deploy a kiam application 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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value          |
@@ -78,7 +77,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the the deployment(s)/statefulset(s)              | `["sleep"]`    |
 | `diagnosticMode.args`    | Args to override all containers in the the deployment(s)/statefulset(s)                 | `["infinity"]` |
 
-
 ### kiam image parameters
 
 | Name                | Description                                                                                          | Value                 |
@@ -90,7 +88,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `image.pullPolicy`  | kiam image pull policy                                                                               | `IfNotPresent`        |
 | `image.pullSecrets` | Specify docker-registry secret names as an array                                                     | `[]`                  |
 
-
 ### kiam server parameters
 
 | Name                                             | Description                                                                                                                                 | Value            |
@@ -170,7 +167,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `server.initContainers`                          | Add additional init containers to the kiam pods                                                                                             | `[]`             |
 | `server.sidecars`                                | Add additional sidecar containers to the kiam pods                                                                                          | `[]`             |
 
-
 ### kiam server exposure parameters
 
 | Name                                      | Description                                                                  | Value       |
@@ -187,7 +183,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `server.service.sessionAffinity`          | Session Affinity for Kubernetes service, can be "None" or "ClientIP"         | `None`      |
 | `server.service.sessionAffinityConfig`    | Additional settings for the sessionAffinity                                  | `{}`        |
 
-
 ### kiam server Service Account parameters
 
 | Name                                                 | Description                                                                                                         | Value  |
@@ -197,7 +192,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `server.serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account                                                      | `true` |
 | `server.serviceAccount.annotations`                  | Annotations for service account. Evaluated as a template. Only used if `create` is `true`.                          | `{}`   |
 
-
 ### kiam server metrics parameters
 
 | Name                                              | Description                                                                       | Value   |
@@ -217,7 +211,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `server.metrics.serviceMonitor.labels`            | Extra labels for the ServiceMonitor                                               | `{}`    |
 | `server.metrics.serviceMonitor.honorLabels`       | honorLabels chooses the metric's labels on collisions with target labels          | `false` |
 
-
 ### kiam agent parameters
 
 | Name                                              | Description                                                                                                                                 | Value                     |
@@ -300,7 +293,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `agent.initContainers`                            | Add additional init containers to the kiam pods                                                                                             | `[]`                      |
 | `agent.sidecars`                                  | Add additional sidecar containers to the kiam pods                                                                                          | `[]`                      |
 
-
 ### kiam agent exposure parameters
 
 | Name                                     | Description                                                                  | Value       |
@@ -316,7 +308,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `agent.service.sessionAffinity`          | Session Affinity for Kubernetes service, can be "None" or "ClientIP"         | `None`      |
 | `agent.service.sessionAffinityConfig`    | Additional settings for the sessionAffinity                                  | `{}`        |
 
-
 ### kiam agent Service Account parameters
 
 | Name                                                | Description                                                                                                         | Value  |
@@ -326,7 +317,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `agent.serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account                                                      | `true` |
 | `agent.serviceAccount.annotations`                  | Annotations for service account. Evaluated as a template. Only used if `create` is `true`.                          | `{}`   |
 
-
 ### kiam agent metrics parameters
 
 | Name                                             | Description                                                                       | Value   |
@@ -346,18 +336,16 @@ The command removes all the Kubernetes components associated with the chart and
 | `agent.metrics.serviceMonitor.labels`            | Extra labels for the ServiceMonitor                                               | `{}`    |
 | `agent.metrics.serviceMonitor.honorLabels`       | honorLabels chooses the metric's labels on collisions with target labels          | `false` |
 
-
 ### RBAC parameters
 
 | Name          | Description                                     | Value  |
 | ------------- | ----------------------------------------------- | ------ |
 | `rbac.create` | Whether to create and use RBAC resources or not | `true` |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
-$ helm install my-release --set server.resourceType=deployment my-repo/kiam
+helm install my-release --set server.resourceType=deployment my-repo/kiam
 ```
 
 The above command sets the server nodes to be deployed as Deployment objects.
@@ -365,7 +353,7 @@ 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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/kiam
+helm install my-release -f values.yaml my-repo/kiam
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -465,10 +453,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/kibana/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/kibana --set elasticsearch.hosts[0]=<Hostname of your ES instance> --set elasticsearch.port=<port of your ES instance>
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/kibana --set elasticsearch.hosts[0]=<Hostname of your ES instance> --set elasticsearch.port=<port of your ES instance>
 ```
 
 ## Introduction
@@ -48,7 +48,7 @@ This chart requires an Elasticsearch instance to work. You can use an already ex
 To uninstall/delete the `my-release` statefulset:
 
 ```console
-$ helm delete my-release
+helm delete my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release. Use the option `--purge` to delete all history too.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                               | Value           |
@@ -79,7 +78,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the the deployment(s)/statefulset(s)                                | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the the deployment(s)/statefulset(s)                                   | `["infinity"]`  |
 
-
 ### Kibana parameters
 
 | Name                                          | Description                                                                                                                                               | Value                    |
@@ -216,7 +214,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.serviceMonitor.labels`               | Extra labels for the ServiceMonitor                                                                                                                       | `{}`                     |
 | `metrics.serviceMonitor.honorLabels`          | honorLabels chooses the metric's labels on collisions with target labels                                                                                  | `false`                  |
 
-
 ### Kibana server TLS configuration
 
 | Name                   | Description                                                                    | Value   |
@@ -229,7 +226,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `tls.keystorePassword` | Password to access the PKCS12 keystore when it is password-protected.          | `""`    |
 | `tls.passwordsSecret`  | Name of a existing secret containing the Keystore or PEM key password          | `""`    |
 
-
 ### Elasticsearch parameters
 
 | Name                                                      | Description                                                                                                              | Value   |
@@ -248,7 +244,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `elasticsearch.security.tls.truststorePassword`           | Password to access the PKCS12 trustore in case it is password-protected.                                                 | `""`    |
 | `elasticsearch.security.tls.passwordsSecret`              | Name of a existing secret containing the Truststore password                                                             | `""`    |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -263,7 +258,7 @@ The above command sets the Kibana admin user to `admin-user`.
 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/kibana
+helm install my-release -f values.yaml my-repo/kibana
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -348,7 +343,7 @@ This chart requires an Elasticsearch instance to work. For production, the optio
 
 For testing purposes, use a sidecar Elasticsearch container setting the following parameters during the Kibana chart installation:
 
-```
+```text
 elasticsearch.hosts[0]=localhost
 elasticsearch.port=9200
 sidecars[0].name=elasticsearch
@@ -466,10 +461,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## 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
@@ -60,7 +60,6 @@ $ helm delete my-release
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                               | Value           |
@@ -76,7 +75,6 @@ $ helm delete my-release
 | `diagnosticMode.command` | Command to override all containers in the daemonset/deployment                                            | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the daemonset/deployment                                               | `["infinity"]`  |
 
-
 ### Kong common parameters
 
 | Name                | Description                                                                                          | Value                 |
@@ -90,7 +88,6 @@ $ helm delete my-release
 | `image.debug`       | Enable image debug mode                                                                              | `false`               |
 | `database`          | Select which database backend Kong will use. Can be 'postgresql', 'cassandra' or 'off'               | `postgresql`          |
 
-
 ### Kong deployment / daemonset parameters
 
 | Name                                    | Description                                                                                                                        | Value           |
@@ -130,7 +127,6 @@ $ helm delete my-release
 | `pdb.minAvailable`                      | Minimum available Kong replicas (expressed in percentage)                                                                          | `""`            |
 | `pdb.maxUnavailable`                    | Maximum unavailable Kong replicas (expressed in percentage)                                                                        | `50%`           |
 
-
 ### Kong Container Parameters
 
 | Name                                      | Description                                                                                                                | Value   |
@@ -174,7 +170,6 @@ $ helm delete my-release
 | `kong.customStartupProbe`                 | Override default startup probe (kong container)                                                                            | `{}`    |
 | `kong.lifecycleHooks`                     | Lifecycle hooks (kong container)                                                                                           | `{}`    |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -213,7 +208,6 @@ $ helm delete my-release
 | `ingress.secrets`                  | If you're providing your own certificates, please use this to add the certificates as secrets                                    | `[]`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Kong Ingress Controller Container Parameters
 
 | Name                                                            | Description                                                                                                                                   | Value                             |
@@ -265,7 +259,6 @@ $ helm delete my-release
 | `ingressController.rbac.create`                                 | Create the necessary RBAC resources for the Ingress Controller to work                                                                        | `true`                            |
 | `ingressController.rbac.rules`                                  | Custom RBAC rules                                                                                                                             | `[]`                              |
 
-
 ### Kong Migration job Parameters
 
 | Name                           | Description                                                                                                                | Value |
@@ -283,7 +276,6 @@ $ helm delete my-release
 | `migration.podLabels`          | Additional pod labels                                                                                                      | `{}`  |
 | `migration.podAnnotations`     | Additional pod annotations                                                                                                 | `{}`  |
 
-
 ### PostgreSQL Parameters
 
 | Name                                            | Description                                                                                                | Value                 |
@@ -308,7 +300,6 @@ $ helm delete my-release
 | `postgresql.external.existingSecret`            | Name of an existing secret resource containing the database credentials                                    | `""`                  |
 | `postgresql.external.existingSecretPasswordKey` | Name of an existing secret key containing the database credentials                                         | `""`                  |
 
-
 ### Cassandra Parameters
 
 | Name                                           | Description                                                              | Value   |
@@ -326,7 +317,6 @@ $ helm delete my-release
 | `cassandra.external.existingSecret`            | Name of an existing secret resource containing the Cassandra credentials | `""`    |
 | `cassandra.external.existingSecretPasswordKey` | Name of an existing secret key containing the Cassandra credentials      | `""`    |
 
-
 ### Metrics Parameters
 
 | Name                                       | Description                                                                           | Value   |
@@ -350,7 +340,6 @@ $ helm delete my-release
 | `metrics.serviceMonitor.serviceAccount`    | Service account used by Prometheus Operator                                           | `""`    |
 | `metrics.serviceMonitor.rbac.create`       | Create the necessary RBAC resources so Prometheus Operator can reach Kong's namespace | `true`  |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -363,7 +352,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)
@@ -383,7 +372,7 @@ 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
@@ -428,6 +417,7 @@ As is said in step 4 of [kong official docker installation](https://docs.konghq.
 
 1. Set `database` value with any value other than "postgresql" or "cassandra". For example `database: "off"`
 2. Use `kong.extraEnvVars` value to set the `KONG_DATABASE` environment variable:
+
 ```yaml
 kong.extraEnvVars:
 - name: KONG_DATABASE
@@ -558,15 +548,15 @@ Kong Ingress Controller version was bumped to new major version, `1.x.x`. The as
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
-- Move dependency information from the *requirements.yaml* to the *Chart.yaml*
-- After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
-- The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
+- Move dependency information from the _requirements.yaml_ to the _Chart.yaml_
+- After running `helm dependency update`, a _Chart.lock_ file is generated containing the same structure used in the previous _requirements.lock_
+- The different fields present in the _Chart.yaml_ file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 - This chart depends on the **PostgreSQL 10** instead of **PostgreSQL 9**. Apart from the same changes that are described in this section, there are also other major changes due to the master/slave nomenclature was replaced by primary/readReplica. [Here](https://github.com/bitnami/charts/pull/4385) you can find more information about the changes introduced.
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
@@ -577,8 +567,8 @@ Kong Ingress Controller version was bumped to new major version, `1.x.x`. The as
 ##### Export secrets and required values to update
 
 ```console
-$ export POSTGRESQL_PASSWORD=$(kubectl get secret --namespace default kong-postgresql -o jsonpath="{.data.password}" | base64 -d)
-$ export POSTGRESQL_PVC=$(kubectl get pvc -l app.kubernetes.io/instance=kong,app.kubernetes.io/name=postgresql,role=master -o jsonpath="{.items[0].metadata.name}")
+export POSTGRESQL_PASSWORD=$(kubectl get secret --namespace default kong-postgresql -o jsonpath="{.data.password}" | base64 -d)
+export POSTGRESQL_PVC=$(kubectl get pvc -l app.kubernetes.io/instance=kong,app.kubernetes.io/name=postgresql,role=master -o jsonpath="{.items[0].metadata.name}")
 ```
 
 ##### Delete statefulsets
@@ -586,7 +576,7 @@ $ export POSTGRESQL_PVC=$(kubectl get pvc -l app.kubernetes.io/instance=kong,app
 Delete PostgreSQL statefulset. Notice the option `--cascade=false`:
 
 ```
-$ kubectl delete statefulsets.apps kong-postgresql --cascade=false
+kubectl delete statefulsets.apps kong-postgresql --cascade=false
 ```
 
 ##### Upgrade the chart release
@@ -600,8 +590,9 @@ $ helm upgrade kong my-repo/kong \
 ##### Force new statefulset to create a new pod for postgresql
 
 ```console
-$ kubectl delete pod kong-postgresql-0
+kubectl delete pod kong-postgresql-0
 ```
+
 Finally, you should see the lines below in MariaDB container logs:
 
 ```console
@@ -611,11 +602,11 @@ postgresql 08:05:12.59 INFO  ==> Deploying PostgreSQL with persisted data...
 ...
 ```
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 4.0.0
 
@@ -627,9 +618,9 @@ PostgreSQL and Cassandra dependencies versions were bumped to new major versions
 
 In order to properly migrate your data to this new version:
 
-* If you were using PostgreSQL as your database, please refer to the [PostgreSQL Upgrade Notes](https://github.com/bitnami/charts/tree/main/bitnami/postgresql#900).
+- If you were using PostgreSQL as your database, please refer to the [PostgreSQL Upgrade Notes](https://github.com/bitnami/charts/tree/main/bitnami/postgresql#900).
 
-* If you were using Cassandra as your database, please refer to the [Cassandra Upgrade Notes](https://github.com/bitnami/charts/tree/main/bitnami/cassandra#to-600).
+- If you were using Cassandra as your database, please refer to the [Cassandra Upgrade Notes](https://github.com/bitnami/charts/tree/main/bitnami/cassandra#to-600).
 
 ## License
 
@@ -639,10 +630,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/kube-prometheus
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/kube-prometheus
 ```
 
 ## Introduction
@@ -41,8 +41,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/kube-prometheus
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/kube-prometheus
 ```
 
 The command deploys kube-prometheus on the Kubernetes cluster in the default configuration. The [configuration](#configuration-and-installation-details) section lists the parameters that can be configured during installation.
@@ -54,7 +54,7 @@ The command deploys kube-prometheus on the Kubernetes cluster in the default con
 To uninstall/delete the `my-release` release:
 
 ```console
-$ helm delete my-release
+helm delete my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release. Use the flag `--purge` to delete all history too.
@@ -69,7 +69,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                                | Value           |
@@ -83,7 +82,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraDeploy`       | Array of extra objects to deploy with the release                                                          | `[]`            |
 | `clusterDomain`     | Kubernetes cluster domain name                                                                             | `cluster.local` |
 
-
 ### Prometheus Operator Parameters
 
 | Name                                                                                  | Description                                                                                                            | Value                         |
@@ -199,7 +197,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `operator.prometheusConfigReloader.readinessProbe.successThreshold`                   | Minimum consecutive successes for the probe                                                                            | `1`                           |
 | `operator.namespaces`                                                                 | Optional comma-separated list of namespaces to watch (default=all).                                                    | `""`                          |
 
-
 ### Prometheus Parameters
 
 | Name                                                                  | Description                                                                                                                      | Value                     |
@@ -403,7 +400,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `prometheus.thanos.ingress.extraRules`                                | The list of additional rules to be added to this ingress record. Evaluated as a template                                         | `[]`                      |
 | `prometheus.portName`                                                 | Port name used for the pods and governing service. This defaults to web                                                          | `web`                     |
 
-
 ### Alertmanager Parameters
 
 | Name                                                             | Description                                                                                                                                                                                                                                                                                                | Value                    |
@@ -518,7 +514,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `alertmanager.configSelector`                                    | Namespaces to be selected for AlertmanagerConfig discovery. If nil, only check own namespace. This defaults to {}                                                                                                                                                                                          | `{}`                     |
 | `alertmanager.configuration`                                     | EXPERIMENTAL: alertmanagerConfiguration specifies the global Alertmanager configuration. If defined, it takes precedence over the `configSecret` field. This field may change in future releases. The specified global alertmanager config will not force add a namespace label in routes and inhibitRules | `{}`                     |
 
-
 ### Exporters
 
 | Name                                               | Description                                                                                            | Value                        |
@@ -543,7 +538,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `kubelet.serviceMonitor.labels`                    | Extra labels for the ServiceMonitor                                                                    | `{}`                         |
 | `kubelet.serviceMonitor.annotations`               | Extra annotations for the ServiceMonitor                                                               | `{}`                         |
 
-
 ### Blackbox Exporter Deployment Parameters
 
 | Name                                                           | Description                                                                                                       | Value                       |
@@ -618,7 +612,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `blackboxExporter.sidecars`                                    | Add additional sidecar containers to the Blackbox Exporter pod(s)                                                 | `[]`                        |
 | `blackboxExporter.initContainers`                              | Add additional init containers to the Blackbox Exporter pod(s)                                                    | `[]`                        |
 
-
 ### Blackbox Exporter Traffic Exposure Parameters
 
 | Name                                                      | Description                                                                                                                     | Value         |
@@ -689,7 +682,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `kubeProxy.serviceMonitor.labels`                         | Extra labels for the ServiceMonitor                                                                                             | `{}`          |
 | `kubeProxy.serviceMonitor.annotations`                    | Extra annotations for the ServiceMonitor                                                                                        | `{}`          |
 
-
 ### RBAC parameters
 
 | Name              | Description                                                                                                                                                        | Value  |
@@ -697,7 +689,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `rbac.create`     | Whether to create and use RBAC resources or not                                                                                                                    | `true` |
 | `rbac.pspEnabled` | Whether to create a PodSecurityPolicy and bound it with RBAC. WARNING: PodSecurityPolicy is deprecated in Kubernetes v1.21 or later, unavailable in v1.25 or later | `true` |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -712,7 +703,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/kube-prometheus
+helm install my-release -f values.yaml my-repo/kube-prometheus
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -760,7 +751,7 @@ Find more information about how to deal with common errors related to Bitnami's
 ## Upgrading
 
 ```console
-$ helm upgrade my-release my-repo/kube-prometheus
+helm upgrade my-release my-repo/kube-prometheus
 ```
 
 ### To 8.0.0
@@ -882,8 +873,8 @@ 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:
 
 ```console
-$ kubectl delete svc my-relase-kube-prometheus-prometheus-thanos
-$ helm upgrade my-release --set prometheus.thanos.create=true my-repo/kube-prometheus
+kubectl delete svc my-relase-kube-prometheus-prometheus-thanos
+helm upgrade my-release --set prometheus.thanos.create=true my-repo/kube-prometheus
 ```
 
 ### To 2.0.0
@@ -908,10 +899,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/kube-state-metrics
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/kube-state-metrics
 ```
 
 ## Introduction
@@ -31,8 +31,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/kube-state-metrics
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/kube-state-metrics
 ```
 
 The command deploys kube-state-metrics on the Kubernetes cluster in the default configuration. The [configuration](#configuration-and-installation-details) section lists the parameters that can be configured during installation.
@@ -42,7 +42,7 @@ The command deploys kube-state-metrics on the Kubernetes cluster in the default
 To uninstall/delete the `my-release` release:
 
 ```console
-$ helm delete my-release
+helm delete my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -57,7 +57,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                                   | Value          |
@@ -73,7 +72,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the the deployment(s)/statefulset(s)                                    | `["sleep"]`    |
 | `diagnosticMode.args`    | Args to override all containers in the the deployment(s)/statefulset(s)                                       | `["infinity"]` |
 
-
 ### kube-state-metrics parameters
 
 | Name                                            | Description                                                                                                                                                        | Value                        |
@@ -200,17 +198,16 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceMonitor.metricRelabelings`              | ServiceMonitor metricRelabelings                                                                                                                                   | `[]`                         |
 | `serviceMonitor.labels`                         | Extra labels for the ServiceMonitor                                                                                                                                | `{}`                         |
 
-
 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`.
 
 ```console
-$ helm install my-release --set replicas=2 my-repo/kube-state-metrics
+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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/kube-state-metrics
+helm install my-release -f values.yaml my-repo/kube-state-metrics
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -242,7 +239,7 @@ Find more information about how to deal with common errors related to Bitnami's
 ## Upgrading
 
 ```console
-$ helm upgrade my-release my-repo/kube-state-metrics
+helm upgrade my-release my-repo/kube-state-metrics
 ```
 
 ### To 3.0.0
@@ -250,6 +247,7 @@ $ helm upgrade my-release my-repo/kube-state-metrics
 This major release renames several values in this chart and adds missing features, in order to be aligned with the rest of the assets in the Bitnami charts repository.
 
 Affected values:
+
 - `service.port` was renamed as `service.ports.metrics`.
 - `service.nodePort` was renamed as `service.nodePorts.metrics`.
 - `securityContext` was split in `podSecurityContext` and `containerSecurityContext`.
@@ -259,8 +257,8 @@ Affected values:
 
 This version updates kube-state-metrics to its new major, 2.0.0. There have been some value's name changes to acommodate to the naming used in 2.0.0:
 
-  - `.Values.namespace` -> `.Values.namespaces`
-  - `.Values.collectors` -> `.Values.kubeResources`
+- `.Values.namespace` -> `.Values.namespaces`
+- `.Values.collectors` -> `.Values.kubeResources`
 
 For more information, please refer to [kube-state-metrics 2 release notes](https://kubernetes.io/blog/2021/04/13/kube-state-metrics-v-2-0/).
 
@@ -282,10 +280,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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

@@ -6,13 +6,11 @@ Kubeapps is a web-based UI for launching and managing applications on Kubernetes
 
 [Overview of Kubeapps](https://github.com/vmware-tanzu/kubeapps)
 
-
-
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/kubeapps --namespace kubeapps --create-namespace
+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.
@@ -46,8 +44,8 @@ It also packages the [Bitnami PostgreSQL chart](https://github.com/bitnami/chart
 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/kubeapps --namespace kubeapps --create-namespace
+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.
@@ -66,7 +64,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value          |
@@ -82,7 +79,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
 | `diagnosticMode.command` | Command to override all containers in the deployment                                    | `["sleep"]`    |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                       | `["infinity"]` |
 
-
 ### Traffic Exposure Parameters
 
 | Name                       | Description                                                                                                                      | Value                    |
@@ -102,7 +98,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
 | `ingress.ingressClassName` | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `ingress.extraRules`       | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Kubeapps packaging options
 
 | Name                       | Description                                                | Value   |
@@ -111,7 +106,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
 | `packaging.carvel.enabled` | Enable support for the Carvel (kapp-controller) packaging. | `false` |
 | `packaging.flux.enabled`   | Enable support for Flux (v2) packaging.                    | `false` |
 
-
 ### Frontend parameters
 
 | Name                                             | Description                                                                                           | Value                  |
@@ -195,7 +189,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
 | `frontend.service.sessionAffinity`               | Session Affinity for Kubernetes service, can be "None" or "ClientIP"                                  | `None`                 |
 | `frontend.service.sessionAffinityConfig`         | Additional settings for the sessionAffinity                                                           | `{}`                   |
 
-
 ### Dashboard parameters
 
 | Name                                              | Description                                                                                               | Value                        |
@@ -276,7 +269,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
 | `dashboard.service.ports.http`                    | Dashboard service HTTP port                                                                               | `8080`                       |
 | `dashboard.service.annotations`                   | Additional custom annotations for Dashboard service                                                       | `{}`                         |
 
-
 ### AppRepository Controller parameters
 
 | Name                                                        | Description                                                                                                                                                                                              | Value                                       |
@@ -344,7 +336,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
 | `apprepository.serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account                                                                                                                                           | `true`                                      |
 | `apprepository.serviceAccount.annotations`                  | Annotations for service account. Evaluated as a template. Only used if `create` is `true`.                                                                                                               | `{}`                                        |
 
-
 ### Auth Proxy parameters
 
 | Name                                              | Description                                                                                                                         | Value                  |
@@ -385,7 +376,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
 | `authProxy.resources.requests.cpu`                | The requested CPU for the OAuth2 Proxy container                                                                                    | `25m`                  |
 | `authProxy.resources.requests.memory`             | The requested memory for the OAuth2 Proxy container                                                                                 | `32Mi`                 |
 
-
 ### Pinniped Proxy parameters
 
 | Name                                                  | Description                                                                                                    | Value                             |
@@ -421,7 +411,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
 | `pinnipedProxy.service.ports.pinnipedProxy`           | Pinniped Proxy service port                                                                                    | `3333`                            |
 | `pinnipedProxy.service.annotations`                   | Additional custom annotations for Pinniped Proxy service                                                       | `{}`                              |
 
-
 ### Other Parameters
 
 | Name          | Description                                               | Value  |
@@ -429,7 +418,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
 | `clusters`    | List of clusters that Kubeapps can target for deployments | `[]`   |
 | `rbac.create` | Specifies whether RBAC resources should be created        | `true` |
 
-
 ### Feature flags
 
 | Name                                    | Description                                                                                                | Value   |
@@ -439,7 +427,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
 | `featureFlags.operators`                | Enable support for Operators in Kubeapps                                                                   | `false` |
 | `featureFlags.schemaEditor.enabled`     | Enable a visual editor for customizing the package schemas                                                 | `false` |
 
-
 ### Database Parameters
 
 | Name                                     | Description                                                                  | Value        |
@@ -456,7 +443,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
 | `postgresql.resources.requests.cpu`      | The requested CPU for the PostgreSQL container                               | `250m`       |
 | `postgresql.resources.requests.memory`   | The requested memory for the PostgreSQL container                            | `256Mi`      |
 
-
 ### kubeappsapis parameters
 
 | Name                                                                                            | Description                                                                                                                                                                | Value                              |
@@ -549,7 +535,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
 | `kubeappsapis.serviceAccount.automountServiceAccountToken`                                      | Automount service account token for the server service account                                                                                                             | `true`                             |
 | `kubeappsapis.serviceAccount.annotations`                                                       | Annotations for service account. Evaluated as a template. Only used if `create` is `true`.                                                                                 | `{}`                               |
 
-
 ### Redis® chart configuration
 
 | Name                                | Description                                                      | Value                                                    |
@@ -566,7 +551,6 @@ Once you have installed Kubeapps follow the [Getting Started Guide](https://gith
 | `redis.replica.disableCommands`     | Array with commands to deactivate on Redis®                  | `[]`                                                     |
 | `redis.replica.persistence.enabled` | Enable Redis® replica data persistence using PVC             | `false`                                                  |
 
-
 ```console
 $ helm install kubeapps --namespace kubeapps \
   --set ingress.enabled=true \
@@ -578,7 +562,7 @@ 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,
 
 ```console
-$ helm install kubeapps --namespace kubeapps -f custom-values.yaml my-repo/kubeapps
+helm install kubeapps --namespace kubeapps -f custom-values.yaml my-repo/kubeapps
 ```
 
 ## Configuration and installation details
@@ -602,7 +586,7 @@ 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:
 
 ```console
-$ kubectl get services --namespace kubeapps --watch
+kubectl get services --namespace kubeapps --watch
 ```
 
 #### Ingress
@@ -662,14 +646,14 @@ 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:
 
 ```console
-$ helm repo update
+helm repo update
 ```
 
 Now upgrade Kubeapps:
 
 ```console
-$ export RELEASE_NAME=kubeapps
-$ helm upgrade $RELEASE_NAME my-repo/kubeapps
+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.
@@ -696,7 +680,7 @@ 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
 
 ```console
-$ kubectl delete namespace kubeapps
+kubectl delete namespace kubeapps
 ```
 
 ## FAQ
@@ -877,13 +861,13 @@ 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:
 
 ```console
-$ kubectl api-versions
+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`:
 
 ```console
-$ helm install --name kubeapps --namespace kubeapps my-repo/kubeapps --set rbac.create=false
+helm install --name kubeapps --namespace kubeapps my-repo/kubeapps --set rbac.create=false
 ```
 
 ### Error while upgrading the Chart
@@ -898,13 +882,13 @@ It is possible that when upgrading Kubeapps an error appears. That can be caused
 1. (Optional) Backup your personal repositories (if you have any):
 
 ```console
-$ kubectl get apprepository -A -o yaml > <repo name>.yaml
+kubectl get apprepository -A -o yaml > <repo name>.yaml
 ```
 
 2. Delete Kubeapps:
 
 ```console
-$ helm del --purge kubeapps
+helm del --purge kubeapps
 ```
 
 3. (Optional) Delete the App Repositories CRD:
@@ -912,7 +896,7 @@ $ helm del --purge kubeapps
 > **Warning**: Do not run this step if you have more than one Kubeapps installation in your cluster.
 
 ```console
-$ kubectl delete crd apprepositories.kubeapps.com
+kubectl delete crd apprepositories.kubeapps.com
 ```
 
 4. (Optional) Clean the Kubeapps namespace:
@@ -920,20 +904,20 @@ $ kubectl delete crd apprepositories.kubeapps.com
 > **Warning**: Do not run this step if you have workloads other than Kubeapps in the `kubeapps` namespace.
 
 ```console
-$ kubectl delete namespace kubeapps
+kubectl delete namespace kubeapps
 ```
 
 5. Install the latest version of Kubeapps (using any custom modifications you need):
 
 ```console
-$ helm repo update
-$ helm install --name kubeapps --namespace kubeapps my-repo/kubeapps
+helm repo update
+helm install --name kubeapps --namespace kubeapps my-repo/kubeapps
 ```
 
 6. (Optional) Restore any repositories you backed up in the first step:
 
 ```console
-$ kubectl apply -f <repo name>.yaml
+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).
@@ -962,7 +946,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.
@@ -978,7 +962,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.
@@ -988,14 +972,14 @@ 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)
 
 [On November 13, 2020, Helm 2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm 3 and to be consistent with the Helm project itself regarding the Helm 2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the _requirements.yaml_ to the _Chart.yaml_
@@ -1003,7 +987,7 @@ $ helm upgrade kubeapps my-repo/kubeapps -n kubeapps --set postgresql.postgresql
 - The different fields present in the _Chart.yaml_ file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 - In the case of PostgreSQL subchart, apart from the same changes that are described in this section, there are also other major changes due to the _master/slave_ nomenclature was replaced by _primary/readReplica_. [Here](https://github.com/bitnami/charts/pull/4385) you can find more information about the changes introduced.
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version using Helm 2, this scenario is not supported as this version does not support Helm 2 anymore
 - If you installed the previous version with Helm 2 and wants to upgrade to this version with Helm 3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm 2 to 3
@@ -1012,10 +996,10 @@ $ helm upgrade kubeapps my-repo/kubeapps -n kubeapps --set postgresql.postgresql
 > 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**
+#### Useful links
 
 - <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
 - <https://helm.sh/docs/topics/v2_v3_migration/>
@@ -1034,7 +1018,7 @@ 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.
 
 ```console
-$ kubectl delete statefulset -n kubeapps kubeapps-postgresql-master kubeapps-postgresql-slave
+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.
@@ -1047,10 +1031,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/kubernetes-event-exporter
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/kubernetes-event-exporter
 ```
 
 ## Introduction
@@ -31,8 +31,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/kubernetes-event-exporter
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/kubernetes-event-exporter
 ```
 
 These commands deploy Kubernetes Event Exporter on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -44,7 +44,7 @@ These commands deploy Kubernetes Event Exporter on the Kubernetes cluster in the
 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.
@@ -58,7 +58,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imageRegistry`    | Global Docker image registry                    | `""`  |
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                              | Value          |
@@ -73,7 +72,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                                        | `["infinity"]` |
 | `extraDeploy`            | Array of extra objects to deploy with the release (evaluated as a template)                              | `[]`           |
 
-
 ### Kubernetes Event Exporter parameters
 
 | Name                                              | Description                                                                                                               | Value                               |
@@ -155,7 +153,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRule.labels`                   | Additional labels that can be used so PrometheusRule will be discovered by Prometheus                                     | `{}`                                |
 | `metrics.prometheusRule.groups`                   | Groups, containing the alert rules.                                                                                       | `[]`                                |
 
-
 ## Configuration and installation details
 
 ### [Rolling vs Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
@@ -186,10 +183,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/logstash/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/logstash
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/logstash
 ```
 
 ## Introduction
@@ -31,8 +31,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/logstash
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/logstash
 ```
 
 These commands deploy logstash on the Kubernetes cluster in the default configuration. The [configuration](#configuration-and-installation-details) section lists the parameters that can be configured during installation.
@@ -44,7 +44,7 @@ These commands deploy logstash on the Kubernetes cluster in the default configur
 To uninstall/delete the `my-release` statefulset:
 
 ```console
-$ helm delete my-release
+helm delete my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release. Use the option `--purge` to delete all history too.
@@ -59,7 +59,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                              | Value           |
@@ -75,7 +74,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                     | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                        | `["infinity"]`  |
 
-
 ### Logstash parameters
 
 | Name                                          | Description                                                                                                                       | Value                    |
@@ -201,7 +199,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `pdb.minAvailable`                            | Minimum number / percentage of pods that should remain scheduled                                                                  | `1`                      |
 | `pdb.maxUnavailable`                          | Maximum number / percentage of pods that may be made unavailable                                                                  | `""`                     |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -214,7 +211,7 @@ The above command disables the Logstash Monitoring API.
 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/logstash
+helm install my-release -f values.yaml my-repo/logstash
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -334,10 +331,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/magento/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/magento
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/magento
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/magento
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/magento
 ```
 
 The command deploys Magento on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys Magento 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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value          |
@@ -79,7 +78,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                    | `["sleep"]`    |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                       | `["infinity"]` |
 
-
 ### Magento parameters
 
 | Name                                    | Description                                                                                                          | Value                    |
@@ -165,7 +163,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `podAnnotations`                        | Pod annotations                                                                                                      | `{}`                     |
 | `podLabels`                             | Add additional labels to the pod (evaluated as a template)                                                           | `{}`                     |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                          | Description                                                                                                                         | Value   |
@@ -186,7 +183,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.denyConnectionsToExternal`         | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                                      | `false` |
 | `networkPolicy.egressRules.customRules`                       | magento Custom network policy rule                                                                                                  | `{}`    |
 
-
 ### Database parameters
 
 | Name                                        | Description                                                                                             | Value                   |
@@ -214,7 +210,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.database`                 | Name of the existing database                                                                           | `bitnami_magento`       |
 | `externalDatabase.existingSecret`           | Name of an existing secret resource containing the DB password                                          | `""`                    |
 
-
 ### Elasticsearch parameters
 
 | Name                                      | Description                                                                                                   | Value                   |
@@ -232,7 +227,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalElasticsearch.host`              | Host of the external elasticsearch server                                                                     | `""`                    |
 | `externalElasticsearch.port`              | Port of the external elasticsearch server                                                                     | `""`                    |
 
-
 ### Persistence parameters
 
 | Name                        | Description                                                                                             | Value               |
@@ -248,7 +242,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `persistence.selector`      | Selector to match an existing Persistent Volume for WordPress data PVC                                  | `{}`                |
 | `persistence.dataSource`    | Custom PVC data source                                                                                  | `{}`                |
 
-
 ### Volume Permissions parameters
 
 | Name                                   | Description                                                                                                                                               | Value                   |
@@ -263,7 +256,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.limits`   | The resources limits for the init container                                                                                                               | `{}`                    |
 | `volumePermissions.resources.requests` | The requested resourcesc for the init container                                                                                                           | `{}`                    |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -296,7 +288,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.secrets`                  | If you're providing your own certificates, please use this to add the certificates as secrets                                    | `[]`                     |
 | `ingress.ingressClassName`         | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 
-
 ### Metrics parameters
 
 | Name                          | Description                                                                                                     | Value                     |
@@ -314,7 +305,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.service.port`        | Service Metrics port                                                                                            | `9117`                    |
 | `metrics.service.annotations` | Annotations for the Prometheus exporter service                                                                 | `{}`                      |
 
-
 ### Certificate injection parameters
 
 | Name                                                 | Description                                                                                                       | Value                                    |
@@ -338,7 +328,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `certificates.image.pullPolicy`                      | Container sidecar image pull policy                                                                               | `IfNotPresent`                           |
 | `certificates.image.pullSecrets`                     | Container sidecar image pull secrets                                                                              | `[]`                                     |
 
-
 ### Other Parameters
 
 | Name                       | Description                          | Value   |
@@ -349,7 +338,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `autoscaling.targetCPU`    | Target CPU utilization percentage    | `""`    |
 | `autoscaling.targetMemory` | Target Memory utilization percentage | `""`    |
 
-
 The above parameters map to the env variables defined in [bitnami/magento](https://github.com/bitnami/containers/tree/main/bitnami/magento). For more information please refer to the [bitnami/magento](https://github.com/bitnami/containers/tree/main/bitnami/magento) image documentation.
 
 > **Note**:
@@ -381,7 +369,7 @@ The above command sets the Magento 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/magento
+helm install my-release -f values.yaml my-repo/magento
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -464,7 +452,9 @@ If you are going to manage TLS secrets outside of Helm, please know that you can
 
 The [Bitnami Magento](https://github.com/bitnami/containers/tree/main/bitnami/magento) image stores the Magento data and configurations at the `/bitnami/magento` and `/bitnami/apache` paths of the container.
 
- Persistent Volume Claims are used to keep the data across deployments. There is a [known issue](https://github.com/kubernetes/kubernetes/issues/39178) in Kubernetes Clusters with EBS in different availability zones. Ensure your cluster is configured properly to create Volumes in the same availability zone where the nodes are running. Kuberentes 1.12 solved this issue with the [Volume Binding Mode](https://kubernetes.io/docs/concepts/storage/storage-classes/#volume-binding-mode).
+Persistent Volume Claims are used to keep the data across deployments. There is a [known issue](https://github.com/kubernetes/kubernetes/issues/39178) in Kubernetes Clusters with EBS in different availability zones. Ensure your cluster is configured properly to create Volumes in the same availability zone where the nodes are running. Kuberentes 1.12 solved this issue with the [Volume Binding Mode](https://kubernetes.io/docs/concepts/storage/storage-classes/#volume-binding-mode).
+
+See the [Parameters](#parameters) section to configure the PVC or to disable persistence.
 
 ### Adding extra environment variables
 
@@ -542,13 +532,6 @@ This chart allows you to set your custom affinity using the `affinity` parameter
 
 As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
 
-## Persistence
-
-The [Bitnami Magento](https://github.com/bitnami/containers/tree/main/bitnami/magento) image stores the Magento data and configurations at the `/bitnami/magento` path of the container.
-
-Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube.
-See the [Parameters](#parameters) section to configure the PVC or to disable persistence.
-
 ### Existing PersistentVolumeClaim
 
 1. Create the PersistentVolume
@@ -556,7 +539,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
 1. Install the chart
 
     ```console
-    $ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/magento
+    helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/magento
     ```
 
 ### Host path
@@ -572,7 +555,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
 1. Install the chart
 
     ```console
-    $ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/magento
+    helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/magento
     ```
 
     This will mount the `magento-data` volume into the `hostPath` directory. The site data will be persisted if the mount path contains valid data, else the site data will be initialized at first launch.
@@ -590,8 +573,9 @@ certificates:
 ```
 
 > Tip! You can create a secret containing your CA certificates using the following command:
+
 ```console
-$ kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
+kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
 ```
 
 ## Troubleshooting
@@ -622,7 +606,7 @@ In this major there were three main changes introduced:
 - Migration to non-root
 - Elasticsearch sub-chart 14.0.0 update
 
-**1. Chart standarizations**
+#### 1. Chart standarizations
 
 This upgrade adapts the chart to the latest Bitnami good practices. Check the Parameters section for more information. In summary:
 
@@ -630,14 +614,14 @@ This upgrade adapts the chart to the latest Bitnami good practices. Check the Pa
 - Some parameters were renamed or disappeared in favor of new ones in this major version. For example, `persistence.magento.*` parameters were deprecated in favor of `persistence.*`.
 - This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
 
-**2. Migration of the Magento image to non-root**
+#### 2. Migration of the Magento image to non-root
 
 The [Bitnami Magento](https://github.com/bitnami/containers/tree/main/bitnami/magento) image was migrated to a "non-root" user approach. Previously the container ran as the `root` user and the Apache daemon was started as the `daemon` user. From now on, both the container and the Apache daemon run as user `1001`. Consequences:
 
 - The HTTP/HTTPS ports exposed by the container are now `8080/8443` instead of `80/443`.
 - Backwards compatibility is not guaranteed. Uninstall & install the chart again to obtain the latest version.
 
-**3. Elasticsearch sub-chart 14.0.0 update**
+#### 3. Elasticsearch sub-chart 14.0.0 update
 
 This version of the Elasticsearch sub-chart standardizes the way of defining Ingress rules in the Kibana sub-chart.
 
@@ -697,12 +681,12 @@ Consequences:
 - Backwards compatibility is not guaranteed. However, you can easily workaround this issue by removing Magento deployment before upgrading (the following example assumes that the release name is `magento`):
 
 ```console
-$ export APP_HOST=$(kubectl get svc --namespace default magento --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
-$ export APP_PASSWORD=$(kubectl get secret --namespace default magento -o jsonpath="{.data.magento-password}" | base64 -d)
-$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default magento-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
-$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default magento-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
-$ kubectl delete deployments.apps magento
-$ helm upgrade magento my-repo/magento --set magentoHost=$APP_HOST,magentoPassword=$APP_PASSWORD,mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD,mariadb.auth.password=$MARIADB_PASSWORD
+export APP_HOST=$(kubectl get svc --namespace default magento --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
+export APP_PASSWORD=$(kubectl get secret --namespace default magento -o jsonpath="{.data.magento-password}" | base64 -d)
+export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default magento-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
+export MARIADB_PASSWORD=$(kubectl get secret --namespace default magento-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
+kubectl delete deployments.apps magento
+helm upgrade magento my-repo/magento --set magentoHost=$APP_HOST,magentoPassword=$APP_PASSWORD,mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD,mariadb.auth.password=$MARIADB_PASSWORD
 ```
 
 ### To 15.0.0
@@ -714,30 +698,30 @@ In this major there were two main changes introduced:
 
 Please read the update notes carefully.
 
-**1. Adaptation to Helm v2 EOL**
+#### 1. Adaptation to Helm v2 EOL
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+##### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
-- Move dependency information from the *requirements.yaml* to the *Chart.yaml*
-- After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
-- The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
+- Move dependency information from the _requirements.yaml_ to the _Chart.yaml_
+- After running `helm dependency update`, a _Chart.lock_ file is generated containing the same structure used in the previous _requirements.lock_
+- The different fields present in the _Chart.yaml_ file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+##### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+##### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
-**2. Updated MariaDB dependency version**
+#### 2. Updated MariaDB dependency version
 
 In this major the MariaDB and Elasticsearch dependency versions were also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-800) for more information. Although it is using the latest `bitnami/mariadb` chart, given Magento `2.4` [current limitations](https://devdocs.magento.com/guides/v2.4/install-gde/system-requirements.html#database), the container image of MariaDB has been bumped to `10.4.x` instead of using the latest `10.5.x`.
 
@@ -748,30 +732,30 @@ To upgrade to `15.0.0`, it should be done reusing the PVCs used to hold data fro
 Obtain the credentials and the names of the PVCs used to hold the MariaDB data on your current release:
 
 ```console
-$ export MAGENTO_HOST=$(kubectl get svc --namespace default magento --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
-$ export MAGENTO_PASSWORD=$(kubectl get secret --namespace default magento -o jsonpath="{.data.magento-password}" | base64 -d)
-$ export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default magento-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
-$ export MARIADB_PASSWORD=$(kubectl get secret --namespace default magento-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
-$ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=magento -o jsonpath="{.items[0].metadata.name}")
+export MAGENTO_HOST=$(kubectl get svc --namespace default magento --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
+export MAGENTO_PASSWORD=$(kubectl get secret --namespace default magento -o jsonpath="{.data.magento-password}" | base64 -d)
+export MARIADB_ROOT_PASSWORD=$(kubectl get secret --namespace default magento-mariadb -o jsonpath="{.data.mariadb-root-password}" | base64 -d)
+export MARIADB_PASSWORD=$(kubectl get secret --namespace default magento-mariadb -o jsonpath="{.data.mariadb-password}" | base64 -d)
+export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=magento -o jsonpath="{.items[0].metadata.name}")
 ```
 
 Delete the Magento deployment and delete the MariaDB statefulset. Notice the option `--cascade=false` in the latter.
 
 ```console
-$ kubectl delete deployments.apps magento
-$ kubectl delete statefulsets.apps magento-mariadb --cascade=false
+kubectl delete deployments.apps magento
+kubectl delete statefulsets.apps magento-mariadb --cascade=false
 ```
 
 Now the upgrade works:
 
 ```console
-$ helm upgrade magento my-repo/magento --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set magentoPassword=$MAGENTO_PASSWORD --set magentoHost=$MAGENTO_HOST
+helm upgrade magento my-repo/magento --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set magentoPassword=$MAGENTO_PASSWORD --set magentoHost=$MAGENTO_HOST
 ```
 
 You will have to delete the existing MariaDB pod and the new statefulset is going to create a new one
 
 ```console
-$ kubectl delete pod magento-mariadb-0z
+kubectl delete pod magento-mariadb-0z
 ```
 
 Finally, you should see the lines below in MariaDB container logs:
@@ -798,9 +782,9 @@ Manual intervention is needed if configuring Elasticsearch 6 as Magento search e
 
 [Follow the Magento documentation](https://devdocs.magento.com/guides/v2.3/config-guide/elasticsearch/configure-magento.html) in order to configure Elasticsearch, setting **Search Engine** to **Elasticsearch 6.0+**. If using the Elasticsearch server included in this chart, `hostname` and `port` can be obtained with the following commands:
 
-```
-$ kubectl get svc -l app=elasticsearch,component=client,release=RELEASE_NAME -o jsonpath="{.items[0].metadata.name}"
-$ kubectl get svc -l app=elasticsearch,component=client,release=RELEASE_NAME -o jsonpath="{.items[0].spec.ports[0].port}"
+```console
+kubectl get svc -l app=elasticsearch,component=client,release=RELEASE_NAME -o jsonpath="{.items[0].metadata.name}"
+kubectl get svc -l app=elasticsearch,component=client,release=RELEASE_NAME -o jsonpath="{.items[0].spec.ports[0].port}"
 ```
 
 Where `RELEASE_NAME` is the name of the release. Use `helm list` to find it.
@@ -811,8 +795,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 magento:
 
 ```console
-$ kubectl patch deployment magento-magento --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl delete statefulset magento-mariadb --cascade=false
+kubectl patch deployment magento-magento --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl delete statefulset magento-mariadb --cascade=false
 ```
 
 ## Community supported solution
@@ -831,10 +815,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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-galera/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/mariadb-galera
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mariadb-galera
 ```
 
 ## 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/mariadb-galera
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mariadb-galera
 ```
 
 The command deploys MariaDB Galera on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -45,13 +45,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`:
 
 ```console
-$ kubectl scale sts my-release-mariadb-galera --replicas=0
+kubectl scale sts my-release-mariadb-galera --replicas=0
 ```
 
 To uninstall/delete the `my-release` release:
 
 ```console
-$ helm delete --purge my-release
+helm delete --purge my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -66,7 +66,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                               | Value           |
@@ -84,7 +83,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                                      | `[]`            |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                                         | `[]`            |
 
-
 ### MariaDB Galera parameters
 
 | Name                                          | Description                                                                                                                                                                                   | Value                     |
@@ -257,7 +255,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRules.additionalLabels`    | Additional labels to add to the PrometheusRule so it is picked up by the operator                                                                                                             | `{}`                      |
 | `metrics.prometheusRules.rules`               | PrometheusRule rules to configure                                                                                                                                                             | `{}`                      |
 
-
 The above parameters map to the env variables defined in [bitnami/mariadb-galera](https://github.com/bitnami/containers/tree/main/bitnami/mariadb-galera). For more information please refer to the [bitnami/mariadb-galera](https://github.com/bitnami/containers/tree/main/bitnami/mariadb-galera) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -276,7 +273,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/mariadb-galera
+helm install my-release -f values.yaml my-repo/mariadb-galera
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -362,7 +359,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:
@@ -405,6 +402,7 @@ initdbScripts:
 
 The feature allows for specifying a template string for a initContainer in the pod. Usecases include situations when you need some pre-run setup. For example, in IKS (IBM Cloud Kubernetes Service), non-root users do not have write permission on the volume mount path for NFS-powered file storage. So, you could use a initcontainer to `chown` the mount. See a example below, where we add an initContainer on the pod that reports to an external resource that the db is going to starting.
 `values.yaml`
+
 ```yaml
 extraInitContainers:
 - name: initcontainer
@@ -418,6 +416,7 @@ extraInitContainers:
 
 The feature allows for specifying additional containers in the pod. Usecases include situations when you need to run some sidecar containers. For example, you can observe if mysql in pod is running and report to some service discovery software like eureka. Example:
 `values.yaml`
+
 ```yaml
 extraContainers:
 - name: '{{ .Chart.Name }}-eureka-sidecar'
@@ -622,22 +621,22 @@ This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
-- The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
+- The different fields present in the _Chart.yaml_ file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 2.0.0
 
@@ -674,10 +673,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/mariadb
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mariadb
 ```
 
 ## 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/mariadb
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mariadb
 ```
 
 The command deploys MariaDB on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -47,7 +47,7 @@ The command deploys MariaDB 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.
@@ -62,7 +62,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global storage class for dynamic provisioning   | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value           |
@@ -80,7 +79,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                    | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                       | `["infinity"]`  |
 
-
 ### MariaDB common parameters
 
 | Name                       | Description                                                                                                                                                                                                                                                                   | Value                  |
@@ -106,7 +104,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `initdbScripts`            | Dictionary of initdb scripts                                                                                                                                                                                                                                                  | `{}`                   |
 | `initdbScriptsConfigMap`   | ConfigMap with the initdb scripts (Note: Overrides `initdbScripts`)                                                                                                                                                                                                           | `""`                   |
 
-
 ### MariaDB Primary parameters
 
 | Name                                                        | Description                                                                                                       | Value               |
@@ -199,7 +196,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `primary.pdb.maxUnavailable`                                | Maximum number/percentage of MariaDB primary pods that can be unavailable after the eviction                      | `""`                |
 | `primary.revisionHistoryLimit`                              | Maximum number of revisions that will be maintained in the StatefulSet                                            | `10`                |
 
-
 ### MariaDB Secondary parameters
 
 | Name                                                          | Description                                                                                                           | Value               |
@@ -292,7 +288,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `secondary.pdb.maxUnavailable`                                | Maximum number/percentage of MariaDB secondary pods that may be made unavailable                                      | `""`                |
 | `secondary.revisionHistoryLimit`                              | Maximum number of revisions that will be maintained in the StatefulSet                                                | `10`                |
 
-
 ### RBAC parameters
 
 | Name                                          | Description                                                    | Value   |
@@ -303,7 +298,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account | `false` |
 | `rbac.create`                                 | Whether to create and use RBAC resources or not                | `false` |
 
-
 ### Volume Permissions parameters
 
 | Name                                   | Description                                                                                                                       | Value                   |
@@ -318,7 +312,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.limits`   | Init container volume-permissions resource limits                                                                                 | `{}`                    |
 | `volumePermissions.resources.requests` | Init container volume-permissions resource requests                                                                               | `{}`                    |
 
-
 ### Metrics parameters
 
 | Name                                                        | Description                                                                                                                               | Value                     |
@@ -365,7 +358,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRule.additionalLabels`                   | Additional labels that can be used so PrometheusRule will be discovered by Prometheus                                                     | `{}`                      |
 | `metrics.prometheusRule.rules`                              | Prometheus Rule definitions                                                                                                               | `[]`                      |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                                   | Description                                                                                                                            | Value   |
@@ -385,7 +377,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.denyConnectionsToExternal`                  | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                                         | `false` |
 | `networkPolicy.egressRules.customRules`                                | Custom network policy rule                                                                                                             | `{}`    |
 
-
 The above parameters map to the env variables defined in [bitnami/mariadb](https://github.com/bitnami/containers/tree/main/bitnami/mariadb). For more information please refer to the [bitnami/mariadb](https://github.com/bitnami/containers/tree/main/bitnami/mariadb) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -403,7 +394,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/mariadb
+helm install my-release -f values.yaml my-repo/mariadb
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -463,7 +454,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:
 
 ```console
-$ helm upgrade my-release my-repo/mariadb --set auth.rootPassword=[ROOT_PASSWORD]
+helm upgrade my-release my-repo/mariadb --set auth.rootPassword=[ROOT_PASSWORD]
 ```
 
 | Note: you need to substitute the placeholder _[ROOT_PASSWORD]_ with the value obtained in the installation notes.
@@ -520,7 +511,7 @@ Backwards compatibility is not guaranteed. To upgrade to `8.0.0`, install a new
 - 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`:
 
 ```console
-$ helm install mariadb my-repo/mariadb --set auth.rootPassword=[ROOT_PASSWORD] --set primary.persistence.existingClaim=[EXISTING_PVC]
+helm install mariadb my-repo/mariadb --set auth.rootPassword=[ROOT_PASSWORD] --set primary.persistence.existingClaim=[EXISTING_PVC]
 ```
 
 | Note: you need to substitute the placeholder _[EXISTING_PVC]_ with the name of the PVC used on your previous release, and _[ROOT_PASSWORD]_ with the root password used in your previous release.
@@ -529,7 +520,7 @@ $ helm install mariadb my-repo/mariadb --set auth.rootPassword=[ROOT_PASSWORD] -
 
 Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
 
-In https://github.com/helm/charts/pull/17308 the `apiVersion` of the statefulset resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
+In <https://github.com/helm/charts/pull/17308> the `apiVersion` of the statefulset resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
 
 This major version bump signifies this change.
 
@@ -546,7 +537,7 @@ Backwards compatibility is not guaranteed unless you modify the labels used on t
 Use the workaround below to upgrade from versions previous to 5.0.0. The following example assumes that the release name is mariadb:
 
 ```console
-$ kubectl delete statefulset opencart-mariadb --cascade=false
+kubectl delete statefulset opencart-mariadb --cascade=false
 ```
 
 ## License
@@ -557,10 +548,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/mastodon/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/mastodon
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mastodon
 ```
 
 ## Introduction
@@ -36,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ 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.
@@ -49,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.
@@ -64,7 +64,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                                                                         | Value                 |
@@ -88,7 +87,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `image.pullSecrets`      | Mastodon image pull secrets                                                                                                                         | `[]`                  |
 | `image.debug`            | Enable Mastodon image debug mode                                                                                                                    | `false`               |
 
-
 ### Mastodon common parameters
 
 | Name                           | Description                                                                    | Value               |
@@ -107,8 +105,7 @@ The command removes all the Kubernetes components associated with the chart and
 | `enableSearches`               | Enable the search engine (uses Elasticsearch under the hood)                   | `true`              |
 | `enableS3`                     | Enable the S3 storage engine                                                   | `true`              |
 | `webDomain`                    | Web domain for Mastodon                                                        | `""`                |
-| `s3AliasHost`                  | S3 alias host for Mastodon (will use http://webDomain/bucket if not set)       | `""`                |
-
+| `s3AliasHost`                  | S3 alias host for Mastodon (will use <http://webDomain/bucket> if not set)       | `""`                |
 
 ### Mastodon Web Parameters
 
@@ -175,7 +172,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `web.sidecars`                                          | Add additional sidecar containers to the Mastodon web pod(s)                                                             | `[]`             |
 | `web.initContainers`                                    | Add additional init containers to the Mastodon web pod(s)                                                                | `[]`             |
 
-
 ### Mastodon Web Traffic Exposure Parameters
 
 | Name                                   | Description                                                                             | Value       |
@@ -192,7 +188,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `web.service.sessionAffinity`          | Control where web requests go, to the same pod or round-robin                           | `None`      |
 | `web.service.sessionAffinityConfig`    | Additional settings for the sessionAffinity                                             | `{}`        |
 
-
 ### Mastodon Sidekiq Parameters
 
 | Name                                                        | Description                                                                                                              | Value            |
@@ -257,7 +252,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `sidekiq.sidecars`                                          | Add additional sidecar containers to the Mastodon sidekiq pod(s)                                                         | `[]`             |
 | `sidekiq.initContainers`                                    | Add additional init containers to the Mastodon sidekiq pod(s)                                                            | `[]`             |
 
-
 ### Mastodon Streaming Parameters
 
 | Name                                                          | Description                                                                                                              | Value            |
@@ -323,7 +317,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `streaming.sidecars`                                          | Add additional sidecar containers to the Mastodon streaming pod(s)                                                       | `[]`             |
 | `streaming.initContainers`                                    | Add additional init containers to the Mastodon streaming pod(s)                                                          | `[]`             |
 
-
 ### Mastodon Streaming Traffic Exposure Parameters
 
 | Name                                         | Description                                                                                   | Value       |
@@ -340,7 +333,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `streaming.service.sessionAffinity`          | Control where streaming requests go, to the same pod or round-robin                           | `None`      |
 | `streaming.service.sessionAffinityConfig`    | Additional settings for the sessionAffinity                                                   | `{}`        |
 
-
 ### Mastodon Migration job Parameters
 
 | Name                                                        | Description                                                                                                                    | Value            |
@@ -371,7 +363,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `initJob.podLabels`                                         | Additional pod labels                                                                                                          | `{}`             |
 | `initJob.podAnnotations`                                    | Additional pod annotations                                                                                                     | `{}`             |
 
-
 ### Persistence Parameters (only when S3 is disabled)
 
 | Name                        | Description                                                                                             | Value               |
@@ -387,7 +378,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `persistence.selector`      | Selector to match an existing Persistent Volume for WordPress data PVC                                  | `{}`                |
 | `persistence.dataSource`    | Custom PVC data source                                                                                  | `{}`                |
 
-
 ### Init Container Parameters
 
 | Name                                                   | Description                                                                                     | Value                   |
@@ -402,7 +392,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.requests`                 | The requested resources for the init container                                                  | `{}`                    |
 | `volumePermissions.containerSecurityContext.runAsUser` | Set init container's Security Context runAsUser                                                 | `0`                     |
 
-
 ### Other Parameters
 
 | Name                                          | Description                                                             | Value         |
@@ -419,7 +408,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.existingSecret`             | Name of an existing secret resource containing the database credentials | `""`          |
 | `externalDatabase.existingSecretPasswordKey`  | Name of an existing secret key containing the database credentials      | `db-password` |
 
-
 ### External Redis parameters
 
 | Name                                      | Description                                                          | Value  |
@@ -430,7 +418,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalRedis.existingSecret`            | Name of an existing secret resource containing the Redis credentials | `""`   |
 | `externalRedis.existingSecretPasswordKey` | Name of an existing secret key containing the Redis credentials      | `""`   |
 
-
 ### External S3 parameters
 
 | Name                                      | Description                                                        | Value           |
@@ -446,7 +433,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalS3.bucket`                       | External S3 bucket                                                 | `mastodon`      |
 | `externalS3.region`                       | External S3 region                                                 | `us-east-1`     |
 
-
 ### External elasticsearch configuration
 
 | Name                                              | Description                                                                  | Value                    |
@@ -457,7 +443,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalElasticsearch.existingSecret`            | Name of an existing secret resource containing the elasticsearch credentials | `""`                     |
 | `externalElasticsearch.existingSecretPasswordKey` | Name of an existing secret key containing the elasticsearch credentials      | `elasticsearch-password` |
 
-
 ### Redis sub-chart parameters
 
 | Name                               | Description                                    | Value        |
@@ -470,7 +455,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `redis.auth.password`              | Redis password                                 | `""`         |
 | `redis.auth.existingSecret`        | Name of a secret containing the Redis password | `""`         |
 
-
 ### PostgreSQL chart configuration
 
 | Name                                          | Description                                               | Value              |
@@ -483,7 +467,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `postgresql.architecture`                     | PostgreSQL architecture (`standalone` or `replication`)   | `standalone`       |
 | `postgresql.primary.service.ports.postgresql` | PostgreSQL service port                                   | `5432`             |
 
-
 ### MinIO&reg; chart parameters
 
 | Name                               | Description                                                                                                                       | Value                                                  |
@@ -501,7 +484,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `minio.service.loadBalancerIP`     | MinIO&reg; service LoadBalancer IP                                                                                                | `""`                                                   |
 | `minio.service.ports.api`          | MinIO&reg; service port                                                                                                           | `80`                                                   |
 
-
 ### Elasticsearch chart configuration
 
 | Name                                        | Description                                                                 | Value   |
@@ -517,7 +499,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `elasticsearch.ingest.replicaCount`         | Desired number of Elasticsearch ingest nodes                                | `1`     |
 | `elasticsearch.service.ports.restAPI`       | Elasticsearch REST API port                                                 | `9200`  |
 
-
 ### Apache chart configuration
 
 | Name                            | Description                                                     | Value                      |
@@ -534,8 +515,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `apache.ingress.enabled`        | Enable ingress                                                  | `false`                    |
 | `apache.ingress.hostname`       | Ingress hostname                                                | `mastodon.local`           |
 
-
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -552,7 +531,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)
@@ -666,10 +645,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/matomo/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/matomo
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/matomo
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/matomo
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/matomo
 ```
 
 The command deploys Matomo on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys Matomo on the Kubernetes cluster in the default configuratio
 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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                                | Value |
@@ -76,7 +75,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `commonLabels`      | Common labels to add to all Matomo resources (sub-charts are not considered). Evaluated as a template      | `{}`  |
 | `extraDeploy`       | Array of extra objects to deploy with the release (evaluated as a template).                               | `[]`  |
 
-
 ### Matomo parameters
 
 | Name                                    | Description                                                                                                           | Value                 |
@@ -172,7 +170,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `podAnnotations`                        | Pod annotations                                                                                                       | `{}`                  |
 | `podLabels`                             | Add additional labels to the pod (evaluated as a template)                                                            | `{}`                  |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -204,7 +201,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.secrets`                  | If you're providing your own certificates, please use this to add the certificates as secrets                                    | `[]`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Database parameters
 
 | Name                                        | Description                                                                              | Value               |
@@ -228,7 +224,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.database`                 | Name of the existing database                                                            | `bitnami_matomo`    |
 | `externalDatabase.existingSecret`           | Name of a secret containing the database credentials                                     | `""`                |
 
-
 ### Volume Permissions parameters
 
 | Name                                   | Description                                                                                                                                               | Value                   |
@@ -243,7 +238,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.limits`   | The resources limits for the container                                                                                                                    | `{}`                    |
 | `volumePermissions.resources.requests` | The requested resources for the container                                                                                                                 | `{}`                    |
 
-
 ### Metrics parameters
 
 | Name                        | Description                                                                                                     | Value                     |
@@ -258,7 +252,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.resources`         | Metrics exporter resource requests and limits                                                                   | `{}`                      |
 | `metrics.podAnnotations`    | Additional annotations for Metrics exporter pod                                                                 | `{}`                      |
 
-
 ### Certificate injection parameters
 
 | Name                                                 | Description                                                                                                       | Value                                    |
@@ -282,7 +275,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `certificates.image.pullPolicy`                      | Container sidecar image pull policy                                                                               | `IfNotPresent`                           |
 | `certificates.image.pullSecrets`                     | Container sidecar image pull secrets                                                                              | `[]`                                     |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                          | Description                                                                                                                | Value   |
@@ -303,7 +295,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.denyConnectionsToExternal`         | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                             | `false` |
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                                 | `{}`    |
 
-
 The above parameters map to the env variables defined in [bitnami/matomo](https://github.com/bitnami/containers/tree/main/bitnami/matomo). For more information please refer to the [bitnami/matomo](https://github.com/bitnami/containers/tree/main/bitnami/matomo) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -321,7 +312,7 @@ The above command sets the Matomo administrator account username and password to
 Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/matomo
+helm install my-release -f values.yaml my-repo/matomo
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -372,7 +363,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
 1. Install the chart
 
 ```console
-$ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/matomo
+helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/matomo
 ```
 
 ### Host path
@@ -388,7 +379,7 @@ $ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/matom
 1. Install the chart
 
     ```console
-    $ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/matomo
+    helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/matomo
     ```
 
     This will mount the `matomo-data` volume into the `hostPath` directory. The site data will be persisted if the mount path contains valid data, else the site data will be initialized at first launch.
@@ -406,10 +397,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/mediawiki/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/mediawiki
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mediawiki
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/mediawiki
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mediawiki
 ```
 
 The command deploys MediaWiki on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys MediaWiki 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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                  | Value           |
@@ -76,7 +75,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `clusterDomain`     | Default Kubernetes cluster domain                                                            | `cluster.local` |
 | `extraDeploy`       | Array of extra objects to deploy with the release                                            | `[]`            |
 
-
 ### Mediawiki parameters
 
 | Name                 | Description                                                                                                                                        | Value                  |
@@ -108,7 +106,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsCM`     | Name of existing ConfigMap containing extra env vars                                                                                               | `""`                   |
 | `extraEnvVarsSecret` | Name of existing Secret containing extra env vars                                                                                                  | `""`                   |
 
-
 ### Mediawiki deployment parameters
 
 | Name                                    | Description                                                                               | Value                                             |
@@ -175,7 +172,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `persistence.size`                      | PVC Storage Request for MediaWiki volume                                                  | `8Gi`                                             |
 | `persistence.annotations`               | Persistent Volume Claim annotations                                                       | `{}`                                              |
 
-
 ### Traffic Exposure parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -207,7 +203,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.ingressClassName`         | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Database parameters
 
 | Name                                        | Description                                                                           | Value               |
@@ -231,7 +226,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.password`                 | Password for the above username                                                       | `""`                |
 | `externalDatabase.database`                 | Name of the existing database                                                         | `bitnami_mediawiki` |
 
-
 ### Metrics parameters
 
 | Name                                       | Description                                                                                                     | Value                     |
@@ -256,7 +250,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.serviceMonitor.labels`            | Extra labels for the ServiceMonitor                                                                             | `{}`                      |
 | `metrics.serviceMonitor.honorLabels`       | honorLabels chooses the metric's labels on collisions with target labels                                        | `false`                   |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                          | Description                                                                                                                   | Value   |
@@ -277,7 +270,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.denyConnectionsToExternal`         | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                                | `false` |
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                                    | `{}`    |
 
-
 The above parameters map to the env variables defined in [bitnami/mediawiki](https://github.com/bitnami/containers/tree/main/bitnami/mediawiki). For more information please refer to the [bitnami/mediawiki](https://github.com/bitnami/containers/tree/main/bitnami/mediawiki) image documentation.
 
 > **Note**:
@@ -299,7 +291,7 @@ The above command sets the MediaWiki administrator account username and password
 Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/mediawiki
+helm install my-release -f values.yaml my-repo/mediawiki
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -400,12 +392,12 @@ Consequences:
 - Backwards compatibility is not guaranteed. However, you can easily workaround this issue by removing Mediawki deployment before upgrading (the following example assumes that the release name is `mediawiki`):
 
 ```console
-$ export APP_HOST=$(kubectl get svc --namespace default mediawiki --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
-$ export APP_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)
-$ kubectl delete deployments.apps mediawiki
-$ helm upgrade mediawiki my-repo/mediawiki --set mediawikiHost=$APP_HOST,mediawikiPassword=$APP_PASSWORD,mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD,mariadb.auth.password=$MARIADB_PASSWORD
+export APP_HOST=$(kubectl get svc --namespace default mediawiki --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
+export APP_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)
+kubectl delete deployments.apps mediawiki
+helm upgrade mediawiki my-repo/mediawiki --set mediawikiHost=$APP_HOST,mediawikiPassword=$APP_PASSWORD,mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD,mariadb.auth.password=$MARIADB_PASSWORD
 ```
 
 ### To 11.0.0
@@ -417,30 +409,30 @@ In this major there were two main changes introduced:
 
 Please read the update notes carefully.
 
-**1. Adaptation to Helm v2 EOL**
+#### 1. Adaptation to Helm v2 EOL
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+##### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+##### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+##### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
-**2. Updated MariaDB dependency version**
+#### 2. Updated MariaDB dependency version
 
 In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-800) for more information.
 
@@ -451,31 +443,31 @@ 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:
 
 ```console
-  $ kubectl delete deployments.apps mediawiki
+  kubectl delete deployments.apps mediawiki
 
-  $ kubectl delete statefulsets.apps mediawiki-mariadb --cascade=false
+  kubectl delete statefulsets.apps mediawiki-mariadb --cascade=false
 ```
 
 Now the upgrade works:
 
 ```console
-$ helm upgrade mediawiki my-repo/mediawiki --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set mediawikiPassword=$MEDIAWIKI_PASSWORD --set mediawikiHost=$MEDIAWIKI_HOST
+helm upgrade mediawiki my-repo/mediawiki --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set mediawikiPassword=$MEDIAWIKI_PASSWORD --set mediawikiHost=$MEDIAWIKI_HOST
 ```
 
 You will have to delete the existing MariaDB pod and the new statefulset is going to create a new one
 
   ```console
-  $ kubectl delete pod mediawiki-mariadb-0
+  kubectl delete pod mediawiki-mariadb-0
   ```
 
 Finally, you should see the lines below in MariaDB container logs:
@@ -503,7 +495,7 @@ To upgrade to `10.0.0`, backup MediaWiki data and the previous MariaDB databases
 
 Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
 
-In https://github.com/helm/charts/pull/17300 the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
+In <https://github.com/helm/charts/pull/17300> the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
 
 This major version signifies this change.
 
@@ -513,8 +505,8 @@ Backwards compatibility is not guaranteed unless you modify the labels used on t
 Use the workaround below to upgrade from versions previous to 4.0.0. The following example assumes that the release name is mediawiki:
 
 ```console
-$ kubectl patch deployment mediawiki-mediawiki --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl delete statefulset mediawiki-mariadb --cascade=false
+kubectl patch deployment mediawiki-mediawiki --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl delete statefulset mediawiki-mariadb --cascade=false
 ```
 
 ## Community supported solution
@@ -533,10 +525,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/memcached/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/memcached
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/memcached
 ```
 
 ## Introduction
@@ -31,8 +31,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/memcached
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/memcached
 ```
 
 These commands deploy Memcached on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -44,7 +44,7 @@ These commands deploy Memcached on the Kubernetes cluster in the default configu
 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.
@@ -59,7 +59,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                  | Value           |
@@ -75,7 +74,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment/statefulset                             | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment/statefulset                                | `["infinity"]`  |
 
-
 ### Memcached parameters
 
 | Name                          | Description                                                                                               | Value                  |
@@ -98,7 +96,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsCM`              | Name of existing ConfigMap containing extra env vars for Memcached nodes                                  | `""`                   |
 | `extraEnvVarsSecret`          | Name of existing Secret containing extra env vars for Memcached nodes                                     | `""`                   |
 
-
 ### Deployment/Statefulset parameters
 
 | Name                                    | Description                                                                                                                                                                                       | Value           |
@@ -166,7 +163,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `pdb.minAvailable`                      | Minimum available Memcached replicas                                                                                                                                                              | `""`            |
 | `pdb.maxUnavailable`                    | Maximum unavailable Memcached replicas                                                                                                                                                            | `1`             |
 
-
 ### Traffic Exposure parameters
 
 | Name                               | Description                                                                             | Value       |
@@ -183,7 +179,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `service.annotations`              | Additional custom annotations for Memcached service                                     | `{}`        |
 | `service.extraPorts`               | Extra ports to expose in the Memcached service (normally used with the `sidecar` value) | `[]`        |
 
-
 ### Other Parameters
 
 | Name                                          | Description                                                            | Value   |
@@ -193,7 +188,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.automountServiceAccountToken` | Allows auto mount of ServiceAccountToken on the serviceAccount created | `true`  |
 | `serviceAccount.annotations`                  | Additional custom annotations for the ServiceAccount                   | `{}`    |
 
-
 ### Persistence parameters
 
 | Name                       | Description                                                              | Value               |
@@ -205,7 +199,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `persistence.annotations`  | Annotations for the PVC                                                  | `{}`                |
 | `persistence.selector`     | Selector to match an existing Persistent Volume for Memcached's data PVC | `{}`                |
 
-
 ### Volume Permissions parameters
 
 | Name                                                   | Description                                                                                                                       | Value                        |
@@ -270,13 +263,12 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.serviceMonitor.honorLabels`                   | Specify honorLabels parameter to add the scrape endpoint                                                                          | `false`                      |
 | `metrics.serviceMonitor.jobLabel`                      | The name of the label on the target service to use as the job name in prometheus.                                                 | `""`                         |
 
-
 The above parameters map to the environment variables defined in the [bitnami/memcached](https://github.com/bitnami/containers/tree/main/bitnami/memcached) container image. For more information please refer to the [bitnami/memcached](https://github.com/bitnami/containers/tree/main/bitnami/memcached) container image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
-$ helm install my-release --set auth.username=user,auth.password=password my-repo/memcached
+helm install my-release --set auth.username=user,auth.password=password my-repo/memcached
 ```
 
 The above command sets the Memcached admin account username and password to `user` and `password` respectively.
@@ -286,7 +278,7 @@ The above command sets the Memcached admin account username and password to `use
 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/memcached
+helm install my-release -f values.yaml my-repo/memcached
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -357,8 +349,8 @@ Backwards compatibility is not guaranteed unless you modify the labels used on t
 Use the workaround below to upgrade from versions previous to 4.0.0. The following example assumes that the release name is memcached:
 
 ```console
-$ kubectl delete deployment  memcached --cascade=false
-$ helm upgrade memcached my-repo/memcached
+kubectl delete deployment  memcached --cascade=false
+helm upgrade memcached my-repo/memcached
 ```
 
 ### To 3.0.0
@@ -371,7 +363,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 memcached:
 
 ```console
-$ kubectl patch deployment memcached --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl patch deployment memcached --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
 ```
 
 ## License
@@ -382,10 +374,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/metallb/README.md

@@ -11,11 +11,12 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/metallb
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/metallb
 ```
 
 ## Introduction
+
 Bitnami charts for Helm are carefully engineered, actively maintained and are the quickest and easiest way to deploy containers on a Kubernetes cluster that are ready to handle production workloads.
 
 This chart bootstraps a [MetalLB Controller](https://metallb.universe.tf/community/) Controller Deployment and a [MetalLB Speaker](https://metallb.universe.tf/community/) Daemonset on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
@@ -33,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/metallb
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/metallb
 ```
 
 These commands deploy metallb 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 @@ These commands deploy metallb on the Kubernetes cluster in the default configura
 To uninstall/delete the `my-release` helm release:
 
 ```console
-$ helm uninstall my-release
+helm uninstall my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -60,7 +61,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imageRegistry`    | Global Docker image registry                    | `""`  |
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value          |
@@ -75,7 +75,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the the deployment(s)/statefulset(s)              | `["sleep"]`    |
 | `diagnosticMode.args`    | Args to override all containers in the the deployment(s)/statefulset(s)                 | `["infinity"]` |
 
-
 ### MetalLB parameters
 
 | Name                                    | Description                                                                                                                                 | Value   |
@@ -87,7 +86,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.ingressNSPodMatchLabels` | For other namespaces match by pod labels and namespace labels                                                                               | `{}`    |
 | `prometheusRule.enabled`                | Prometheus Operator alertmanager alerts are created                                                                                         | `false` |
 
-
 ### Controller parameters
 
 | Name                                                           | Description                                                                                                                                 | Value                        |
@@ -164,7 +162,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `controller.customLivenessProbe`                               | Custom liveness probe for the Web component                                                                                                 | `{}`                         |
 | `controller.customReadinessProbe`                              | Custom readiness probe for the Web component                                                                                                | `{}`                         |
 
-
 ### Metallb controller Prometheus metrics export
 
 | Name                                                  | Description                                                                 | Value                    |
@@ -183,7 +180,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `controller.metrics.serviceMonitor.labels`            | Extra labels for the ServiceMonitor                                         | `{}`                     |
 | `controller.metrics.serviceMonitor.honorLabels`       | honorLabels chooses the metric's labels on collisions with target labels    | `false`                  |
 
-
 ### Speaker parameters
 
 | Name                                                        | Description                                                                                                                                 | Value                     |
@@ -260,7 +256,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `speaker.customLivenessProbe`                               | Custom liveness probe for the Web component                                                                                                 | `{}`                      |
 | `speaker.customReadinessProbe`                              | Custom readiness probe for the Web component                                                                                                | `{}`                      |
 
-
 ### Speaker Prometheus metrics export
 
 | Name                                               | Description                                                                 | Value                    |
@@ -279,7 +274,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `speaker.metrics.serviceMonitor.labels`            | Extra labels for the ServiceMonitor                                         | `{}`                     |
 | `speaker.metrics.serviceMonitor.honorLabels`       | honorLabels chooses the metric's labels on collisions with target labels    | `false`                  |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -287,6 +281,7 @@ $ helm install my-release \
   --set readinessProbe.successThreshold=5 \
     my-repo/metallb
 ```
+
 The above command sets the `readinessProbe.successThreshold` to `5`.
 
 ## Configuration and installation details
@@ -349,7 +344,7 @@ Affected values:
 
 ### To 2.0.0
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - The `.Values.prometheus` section was moved into the components `.Values.controller.prometheus` and `.Values.speaker.prometheus`
 - The `prometheus.prometheusRule` which is used to toggle the deployment of the metallb alerts is moved under the root of the `.Values.prometheusRule`
@@ -357,7 +352,7 @@ Affected values:
   - `Values.controller.rbac.create` and `Values.controller.psp.create`
   - `Values.speaker.rbac.create` and `Values.speaker.psp.create`
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - Check if you used the `prometheus` section in you deployment.
 - If you do so, place the configuration you made into the sections `controller.prometheus` and `speaker.prometheus`.
@@ -367,22 +362,22 @@ Affected values:
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ## Community supported solution
 
@@ -400,10 +395,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/metrics-server/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/metrics-server
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/metrics-server
 ```
 
 ## Introduction
@@ -31,8 +31,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/metrics-server
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/metrics-server
 ```
 
 These commands deploy Metrics Server on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -44,7 +44,7 @@ These commands deploy Metrics Server on the Kubernetes cluster in the default co
 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.
@@ -58,7 +58,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imageRegistry`    | Global Docker image registry                    | `""`  |
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                  | Value          |
@@ -74,7 +73,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the the deployment(s)/statefulset(s)                   | `["sleep"]`    |
 | `diagnosticMode.args`    | Args to override all containers in the the deployment(s)/statefulset(s)                      | `["infinity"]` |
 
-
 ### Metrics Server parameters
 
 | Name                                              | Description                                                                                                                                                              | Value                    |
@@ -169,7 +167,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraVolumes`                                    | Extra volumes                                                                                                                                                            | `[]`                     |
 | `extraVolumeMounts`                               | Mount extra volume(s)                                                                                                                                                    | `[]`                     |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -182,7 +179,7 @@ The above command enables RBAC authentication.
 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/metrics-server
+helm install my-release -f values.yaml my-repo/metrics-server
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -241,8 +238,8 @@ Backwards compatibility is not guaranteed unless you modify the labels used on t
 Use the workaround below to upgrade from versions previous to 4.0.0. The following example assumes that the release name is metrics-server:
 
 ```console
-$ kubectl delete deployment metrics-server --cascade=false
-$ helm upgrade metrics-server my-repo/metrics-server
+kubectl delete deployment metrics-server --cascade=false
+helm upgrade metrics-server my-repo/metrics-server
 ```
 
 ### To 2.0.0
@@ -251,7 +248,7 @@ 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 metrics-server:
 
 ```console
-$ kubectl patch deployment metrics-server --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl patch deployment metrics-server --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
 ```
 
 ## License
@@ -262,10 +259,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/minio/README.md

@@ -11,8 +11,8 @@ Disclaimer: All software products, projects and company names are trademark(TM)
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/minio
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/minio
 ```
 
 ## 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/minio
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/minio
 ```
 
 These commands deploy MinIO® 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 MinIO® 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.
@@ -60,7 +60,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                  | Value           |
@@ -73,7 +72,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `clusterDomain`     | Default Kubernetes cluster domain                                                            | `cluster.local` |
 | `extraDeploy`       | Array of extra objects to deploy with the release                                            | `[]`            |
 
-
 ### MinIO® parameters
 
 | Name                       | Description                                                                                                                                                                                               | Value                    |
@@ -108,7 +106,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `command`                  | Default container command (useful when using custom images). Use array form                                                                                                                               | `[]`                     |
 | `args`                     | Default container args (useful when using custom images). Use array form                                                                                                                                  | `[]`                     |
 
-
 ### MinIO® deployment/statefulset parameters
 
 | Name                                                 | Description                                                                                                                                                                                   | Value           |
@@ -191,7 +188,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `initContainers`                                     | Add additional init containers to the MinIO® pods                                                                                                                                         | `[]`            |
 | `sidecars`                                           | Add additional sidecar containers to the MinIO® pods                                                                                                                                      | `[]`            |
 
-
 ### Traffic exposure parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -241,7 +237,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.allowExternal`      | Don't require client label for connections                                                                                       | `true`                   |
 | `networkPolicy.extraFromClauses`   | Allows to add extra 'from' clauses to the NetworkPolicy                                                                          | `{}`                     |
 
-
 ### Persistence parameters
 
 | Name                        | Description                                                          | Value               |
@@ -254,7 +249,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `persistence.annotations`   | Annotations for the PVC                                              | `{}`                |
 | `persistence.existingClaim` | Name of an existing PVC to use (only in `standalone` mode)           | `""`                |
 
-
 ### Volume Permissions parameters
 
 | Name                                                   | Description                                                                                                                       | Value                   |
@@ -270,7 +264,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.requests`                 | Init container volume-permissions resource requests                                                                               | `{}`                    |
 | `volumePermissions.containerSecurityContext.runAsUser` | User ID for the init container                                                                                                    | `0`                     |
 
-
 ### RBAC parameters
 
 | Name                                          | Description                                                 | Value  |
@@ -280,7 +273,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.automountServiceAccountToken` | Enable/disable auto mounting of the service account token   | `true` |
 | `serviceAccount.annotations`                  | Custom annotations for MinIO® ServiceAccount            | `{}`   |
 
-
 ### Other parameters
 
 | Name                 | Description                                                                       | Value   |
@@ -289,7 +281,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `pdb.minAvailable`   | Minimum number/percentage of pods that must still be available after the eviction | `1`     |
 | `pdb.maxUnavailable` | Maximum number/percentage of pods that may be made unavailable after the eviction | `""`    |
 
-
 ### Metrics parameters
 
 | Name                                       | Description                                                                                                                   | Value                       |
@@ -312,7 +303,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRule.additionalLabels`  | Additional labels that can be used so PrometheusRule will be discovered by Prometheus                                         | `{}`                        |
 | `metrics.prometheusRule.rules`             | Prometheus Rule definitions                                                                                                   | `[]`                        |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -327,7 +317,7 @@ The above command sets the MinIO® Server root user and password to `minio-ad
 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/minio
+helm install my-release -f values.yaml my-repo/minio
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -374,7 +364,7 @@ MinIO® exports Prometheus metrics at `/minio/v2/metrics/cluster`. To allow P
 +   prometheus.io/port: "9000"
 ```
 
-> Find more information about MinIO® metrics at https://docs.min.io/docs/how-to-monitor-minio-using-prometheus.html
+> Find more information about MinIO&reg; metrics at <https://docs.min.io/docs/how-to-monitor-minio-using-prometheus.html>
 
 ## Persistence
 
@@ -477,6 +467,7 @@ This version updates MinIO&reg; authentication parameters so they're aligned wit
 ### To 8.0.0
 
 This version updates MinIO&reg; after some major changes, affecting its Web UI. MinIO&reg; has replaced its MinIO&reg; Browser with the MinIO&reg; Console, and Web UI has been moved to a separated port. As a result the following variables have been affected:
+
 - `service.port` has been slit into `service.ports.api` (default: 9000) and `service.ports.console` (default: 9001).
 - `containerPort` has been slit into `containerPorts.api` (default: 9000) and `containerPort.console` (default: 9001).
 - `service.nodePort`has been slit into `service.nodePorts.api` and `service.nodePorts.console`.
@@ -501,22 +492,22 @@ This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ## License
 
@@ -526,10 +517,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/mongodb-sharded/README.md

@@ -11,8 +11,8 @@ Disclaimer: The respective trademarks mentioned in the offering are owned by the
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/mongodb-sharded
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mongodb-sharded
 ```
 
 ## Introduction
@@ -37,8 +37,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/mongodb-sharded
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mongodb-sharded
 ```
 
 The command deploys MongoDB® on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -50,7 +50,7 @@ The command deploys MongoDB® 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.
@@ -65,7 +65,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global storage class for dynamic provisioning   | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value           |
@@ -82,7 +81,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                    | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                       | `["infinity"]`  |
 
-
 ### MongoDB(®) Sharded parameters
 
 | Name                                                 | Description                                                                                                                                               | Value                     |
@@ -98,7 +96,7 @@ The command removes all the Kubernetes components associated with the chart and
 | `auth.rootUser`                                      | MongoDB(®) root user                                                                                                                                  | `root`                    |
 | `auth.rootPassword`                                  | MongoDB(®) root password                                                                                                                              | `""`                      |
 | `auth.replicaSetKey`                                 | Key used for authentication in the replicaset (only when `architecture=replicaset`)                                                                       | `""`                      |
-| `auth.existingSecret`                                | Existing secret with MongoDB(®) credentials (keys: `mongodb-password`, `mongodb-root-password`, ` mongodb-replica-set-key`)                           | `""`                      |
+| `auth.existingSecret`                                | Existing secret with MongoDB(®) credentials (keys: `mongodb-password`, `mongodb-root-password`, `mongodb-replica-set-key`)                           | `""`                      |
 | `auth.usePasswordFile`                               | Mount credentials as files instead of using environment variables                                                                                         | `false`                   |
 | `shards`                                             | Number of shards to be created                                                                                                                            | `2`                       |
 | `common.mongodbEnableNumactl`                        | Enable launch MongoDB instance prefixed with "numactl --interleave=all"                                                                                   | `false`                   |
@@ -146,7 +144,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `service.sessionAffinity`                            | Session Affinity for Kubernetes service, can be "None" or "ClientIP"                                                                                      | `None`                    |
 | `service.sessionAffinityConfig`                      | Additional settings for the sessionAffinity                                                                                                               | `{}`                      |
 
-
 ### Config Server parameters
 
 | Name                                                        | Description                                                                                                                           | Value                                                  |
@@ -230,7 +227,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `configsvr.customReadinessProbe`                            | Custom readinessProbe that overrides the default one                                                                                  | `{}`                                                   |
 | `configsvr.customStartupProbe`                              | Custom startupProbe that overrides the default one                                                                                    | `{}`                                                   |
 
-
 ### Mongos parameters
 
 | Name                                                     | Description                                                                                                                  | Value           |
@@ -316,7 +312,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `mongos.customReadinessProbe`                            | Custom readinessProbe that overrides the default one                                                                         | `{}`            |
 | `mongos.customStartupProbe`                              | Custom startupProbe that overrides the default one                                                                           | `{}`            |
 
-
 ### Shard configuration: Data node parameters
 
 | Name                                                                | Description                                                                                                              | Value                                                  |
@@ -388,7 +383,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `shardsvr.dataNode.customReadinessProbe`                            | Custom readinessProbe that overrides the default one                                                                     | `{}`                                                   |
 | `shardsvr.dataNode.customStartupProbe`                              | Custom startupProbe that overrides the default one                                                                       | `{}`                                                   |
 
-
 ### Shard configuration: Persistence parameters
 
 | Name                                  | Description                                                                                                                           | Value               |
@@ -402,7 +396,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `shardsvr.persistence.annotations`    | Additional volume annotations                                                                                                         | `{}`                |
 | `shardsvr.persistence.resourcePolicy` | Setting it to "keep" to avoid removing PVCs during a helm delete operation. Leaving it empty will delete PVCs after the chart deleted | `""`                |
 
-
 ### Shard configuration: Arbiter parameters
 
 | Name                                                               | Description                                                                                                              | Value           |
@@ -471,7 +464,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `shardsvr.arbiter.customReadinessProbe`                            | Custom readinessProbe that overrides the default one                                                                     | `{}`            |
 | `shardsvr.arbiter.customStartupProbe`                              | Custom startupProbe that overrides the default one                                                                       | `{}`            |
 
-
 ### Metrics parameters
 
 | Name                                                      | Description                                                                                                           | Value                      |
@@ -519,7 +511,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.podMonitor.scrapeTimeout`                        | Specify the timeout after which the scrape is ended                                                                   | `""`                       |
 | `metrics.podMonitor.additionalLabels`                     | Additional labels that can be used so PodMonitors will be discovered by Prometheus                                    | `{}`                       |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -533,7 +524,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/mongodb-sharded
+helm install my-release -f values.yaml my-repo/mongodb-sharded
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -639,7 +630,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:
 
 ```console
-$ helm upgrade my-release my-repo/mongodb-sharded --set auth.rootPassword=[PASSWORD] (--set auth.replicaSetKey=[auth.replicaSetKey])
+helm upgrade my-release my-repo/mongodb-sharded --set auth.rootPassword=[PASSWORD] (--set auth.replicaSetKey=[auth.replicaSetKey])
 ```
 
 > Note: you need to substitute the placeholders [PASSWORD] and [auth.replicaSetKey] with the values obtained in the installation notes.
@@ -668,7 +659,7 @@ Affected values:
 ### To 4.0.0
 
 In this version, the mongodb-exporter bundled as part of this Helm chart was updated to a new version which, even it is not a major change, can contain breaking changes (from `0.11.X` to `0.30.X`).
-Please visit the release notes from the upstream project at https://github.com/percona/mongodb_exporter/releases
+Please visit the release notes from the upstream project at <https://github.com/percona/mongodb_exporter/releases>
 
 ### To 3.1.0
 
@@ -678,22 +669,22 @@ This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 2.0.0
 
@@ -709,10 +700,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/mongodb/README.md

@@ -11,8 +11,8 @@ Disclaimer: The respective trademarks mentioned in the offering are owned by the
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/mongodb
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mongodb
 ```
 
 ## 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/mongodb
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mongodb
 ```
 
 The command deploys MongoDB(®) 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 @@ The command deploys MongoDB(®) 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.
@@ -72,7 +72,6 @@ Refer to the [chart documentation for more information on each of these architec
 | `global.storageClass`      | Global StorageClass for Persistent Volume(s)                                                                           | `""`  |
 | `global.namespaceOverride` | Override the namespace for resource deployed by the chart, but can itself be overridden by the local namespaceOverride | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                               | Value           |
@@ -90,7 +89,6 @@ Refer to the [chart documentation for more information on each of these architec
 | `diagnosticMode.command` | Command to override all containers in the deployment                                                      | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                                         | `["infinity"]`  |
 
-
 ### MongoDB(®) parameters
 
 | Name                             | Description                                                                                                                                                  | Value                  |
@@ -115,7 +113,7 @@ Refer to the [chart documentation for more information on each of these architec
 | `auth.password`                  | DEPRECATED: use `auth.passwords` instead                                                                                                                     | `""`                   |
 | `auth.database`                  | DEPRECATED: use `auth.databases` instead                                                                                                                     | `""`                   |
 | `auth.replicaSetKey`             | Key used for authentication in the replicaset (only when `architecture=replicaset`)                                                                          | `""`                   |
-| `auth.existingSecret`            | Existing secret with MongoDB(®) credentials (keys: `mongodb-passwords`, `mongodb-root-password`, `mongodb-metrics-password`, ` mongodb-replica-set-key`) | `""`                   |
+| `auth.existingSecret`            | Existing secret with MongoDB(®) credentials (keys: `mongodb-passwords`, `mongodb-root-password`, `mongodb-metrics-password`, `mongodb-replica-set-key`) | `""`                   |
 | `tls.enabled`                    | Enable MongoDB(®) TLS support between nodes in the cluster as well as between mongo clients and nodes                                                    | `false`                |
 | `tls.autoGenerated`              | Generate a custom CA and self-signed certificates                                                                                                            | `true`                 |
 | `tls.existingSecret`             | Existing secret with TLS certificates (keys: `mongodb-ca-cert`, `mongodb-ca-key`)                                                                            | `""`                   |
@@ -146,7 +144,6 @@ Refer to the [chart documentation for more information on each of these architec
 | `enableJournal`                  | Switch to enable/disable MongoDB(®) Journaling                                                                                                           | `true`                 |
 | `configuration`                  | MongoDB(®) configuration file to be used for Primary and Secondary nodes                                                                                 | `""`                   |
 
-
 ### replicaSetConfigurationSettings settings applied during runtime (not via configuration file)
 
 | Name                                            | Description                                                                                         | Value   |
@@ -163,7 +160,6 @@ Refer to the [chart documentation for more information on each of these architec
 | `extraEnvVarsCM`                                | Name of existing ConfigMap containing extra env vars                                                | `""`    |
 | `extraEnvVarsSecret`                            | Name of existing Secret containing extra env vars (in case of sensitive data)                       | `""`    |
 
-
 ### MongoDB(®) statefulset parameters
 
 | Name                                    | Description                                                                                                     | Value           |
@@ -226,7 +222,6 @@ Refer to the [chart documentation for more information on each of these architec
 | `pdb.minAvailable`                      | Minimum number/percentage of MongoDB(®) pods that must still be available after the eviction                | `1`             |
 | `pdb.maxUnavailable`                    | Maximum number/percentage of MongoDB(®) pods that may be made unavailable after the eviction                | `""`            |
 
-
 ### Traffic exposure parameters
 
 | Name                                                     | Description                                                                                                                                     | Value                  |
@@ -284,7 +279,6 @@ Refer to the [chart documentation for more information on each of these architec
 | `externalAccess.hidden.service.sessionAffinity`          | Control where client requests go, to the same pod or round-robin                                                                                | `None`                 |
 | `externalAccess.hidden.service.sessionAffinityConfig`    | Additional settings for the sessionAffinity                                                                                                     | `{}`                   |
 
-
 ### Persistence parameters
 
 | Name                                          | Description                                                                                                                           | Value               |
@@ -303,7 +297,6 @@ Refer to the [chart documentation for more information on each of these architec
 | `persistence.volumeClaimTemplates.requests`   | Custom PVC requests attributes                                                                                                        | `{}`                |
 | `persistence.volumeClaimTemplates.dataSource` | Add dataSource to the VolumeClaimTemplate                                                                                             | `{}`                |
 
-
 ### RBAC parameters
 
 | Name                                          | Description                                                                                                                                 | Value   |
@@ -319,7 +312,6 @@ Refer to the [chart documentation for more information on each of these architec
 | `podSecurityPolicy.privileged`                | Allow privileged                                                                                                                            | `false` |
 | `podSecurityPolicy.spec`                      | Specify the full spec to use for Pod Security Policy                                                                                        | `{}`    |
 
-
 ### Volume Permissions parameters
 
 | Name                                          | Description                                                                                                                       | Value                   |
@@ -335,7 +327,6 @@ Refer to the [chart documentation for more information on each of these architec
 | `volumePermissions.resources.requests`        | Init container volume-permissions resource requests                                                                               | `{}`                    |
 | `volumePermissions.securityContext.runAsUser` | User ID for the volumePermissions container                                                                                       | `0`                     |
 
-
 ### Arbiter parameters
 
 | Name                                            | Description                                                                                       | Value           |
@@ -412,7 +403,6 @@ Refer to the [chart documentation for more information on each of these architec
 | `arbiter.service.extraPorts`                    | Extra ports to expose (normally used with the `sidecar` value)                                    | `[]`            |
 | `arbiter.service.annotations`                   | Provide any additional annotations that may be required                                           | `{}`            |
 
-
 ### Hidden Node parameters
 
 | Name                                                 | Description                                                                                          | Value               |
@@ -501,7 +491,6 @@ Refer to the [chart documentation for more information on each of these architec
 | `hidden.service.extraPorts`                          | Extra ports to expose (normally used with the `sidecar` value)                                       | `[]`                |
 | `hidden.service.annotations`                         | Provide any additional annotations that may be required                                              | `{}`                |
 
-
 ### Metrics parameters
 
 | Name                                         | Description                                                                                                           | Value                      |
@@ -561,7 +550,6 @@ Refer to the [chart documentation for more information on each of these architec
 | `metrics.prometheusRule.namespace`           | Namespace where prometheusRules resource should be created                                                            | `""`                       |
 | `metrics.prometheusRule.rules`               | Rules to be created, check values for an example                                                                      | `[]`                       |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -577,7 +565,7 @@ The above command sets the MongoDB(®) `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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/mongodb
+helm install my-release -f values.yaml my-repo/mongodb
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -594,8 +582,8 @@ Bitnami will release a new chart updating its containers if a new version of the
 
 The [Bitnami MongoDB(®) image](https://github.com/bitnami/containers/tree/main/bitnami/mongodb) supports the use of custom scripts to initialize a fresh instance. In order to execute the scripts, two options are available:
 
-* Specify them using the `initdbScripts` parameter as dict.
-* Define an external Kubernetes ConfigMap with all the initialization scripts by setting the `initdbScriptsConfigMap` parameter. Note that this will override the previous option.
+- Specify them using the `initdbScripts` parameter as dict.
+- Define an external Kubernetes ConfigMap with all the initialization scripts by setting the `initdbScriptsConfigMap` parameter. Note that this will override the previous option.
 
 The allowed script extensions are `.sh` and `.js`.
 
@@ -661,7 +649,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:
 
 ```console
-$ helm upgrade my-release my-repo/mongodb --set auth.rootPassword=[PASSWORD] (--set auth.replicaSetKey=[REPLICASETKEY])
+helm upgrade my-release my-repo/mongodb --set auth.rootPassword=[PASSWORD] (--set auth.replicaSetKey=[REPLICASETKEY])
 ```
 
 > Note: you need to substitute the placeholders [PASSWORD] and [REPLICASETKEY] with the values obtained in the installation notes.
@@ -687,7 +675,7 @@ Additionally also updates the MongoDB image dependency to it newest major, 5.0
 ### To 11.0.0
 
 In this version, the mongodb-exporter bundled as part of this Helm chart was updated to a new version which, even it is not a major change, can contain breaking changes (from `0.11.X` to `0.30.X`).
-Please visit the release notes from the upstream project at https://github.com/percona/mongodb_exporter/releases
+Please visit the release notes from the upstream project at <https://github.com/percona/mongodb_exporter/releases>
 
 ### To 10.0.0
 
@@ -742,7 +730,7 @@ When enabling replicaset configuration, backwards compatibility is not guarantee
 Use the workaround below to upgrade from versions previous to 5.0.0. The following example assumes that the release name is `my-release`:
 
 ```console
-$ kubectl delete statefulset my-release-mongodb-arbiter my-release-mongodb-primary my-release-mongodb-secondary --cascade=false
+kubectl delete statefulset my-release-mongodb-arbiter my-release-mongodb-primary my-release-mongodb-secondary --cascade=false
 ```
 
 ### Add extra deployment options
@@ -787,10 +775,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/moodle/README.md

@@ -11,8 +11,8 @@ Disclaimer: The respective trademarks mentioned in the offering are owned by the
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/moodle
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/moodle
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/moodle
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/moodle
 ```
 
 The command deploys Moodle™ on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys Moodle™ 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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                                | Value |
@@ -75,7 +74,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `commonLabels`      | Common labels to add to all Harbor resources (sub-charts are not considered). Evaluated as a template      | `{}`  |
 | `extraDeploy`       | Array with extra yaml to deploy with the chart. Evaluated as a template                                    | `[]`  |
 
-
 ### Moodle™ parameters
 
 | Name                                    | Description                                                                                                           | Value                |
@@ -168,7 +166,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `podAnnotations`                        | Pod annotations                                                                                                       | `{}`                 |
 | `podLabels`                             | Add additional labels to the pod (evaluated as a template)                                                            | `{}`                 |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -200,7 +197,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.ingressClassName`         | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Database parameters
 
 | Name                                        | Description                                                                              | Value               |
@@ -225,7 +221,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.database`                 | Name of the existing database                                                            | `bitnami_moodle`    |
 | `externalDatabase.existingSecret`           | Name of an existing secret resource containing the DB password                           | `""`                |
 
-
 ### Volume Permissions parameters
 
 | Name                                   | Description                                                                                                                                               | Value                   |
@@ -240,7 +235,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.limits`   | The resources limits for the container                                                                                                                    | `{}`                    |
 | `volumePermissions.resources.requests` | The requested resources for the container                                                                                                                 | `{}`                    |
 
-
 ### Metrics parameters
 
 | Name                                       | Description                                                                                                     | Value                     |
@@ -264,7 +258,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.resources`                        | Exporter resource requests/limit                                                                                | `{}`                      |
 | `metrics.podAnnotations`                   | Metrics exporter pod Annotation and Labels                                                                      | `{}`                      |
 
-
 ### Certificate injection parameters
 
 | Name                                                 | Description                                                                                                       | Value                                    |
@@ -288,7 +281,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `certificates.image.pullPolicy`                      | Container sidecar image pull policy                                                                               | `IfNotPresent`                           |
 | `certificates.image.pullSecrets`                     | Container sidecar image pull secrets                                                                              | `[]`                                     |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                          | Description                                                                                                                | Value   |
@@ -309,7 +301,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.denyConnectionsToExternal`         | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                             | `false` |
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                                 | `{}`    |
 
-
 The above parameters map to the env variables defined in [bitnami/moodle](https://github.com/bitnami/containers/tree/main/bitnami/moodle). For more information please refer to the [bitnami/moodle](https://github.com/bitnami/containers/tree/main/bitnami/moodle) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -327,7 +318,7 @@ The above command sets the Moodle™ administrator account username and pass
 Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/moodle
+helm install my-release -f values.yaml my-repo/moodle
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -425,24 +416,24 @@ This version standardizes the way of defining Ingress rules. When configuring a
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 9.0.0
 
@@ -455,22 +446,22 @@ 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:
 
 ```console
-$ helm upgrade moodle my-repo/moodle --set moodlePassword=$MOODLE_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 8.1.6
+helm upgrade moodle my-repo/moodle --set moodlePassword=$MOODLE_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 8.1.6
 ```
 
 Finally, upgrade you release to 9.0.0 reusing the existing PVC, and enabling back MariaDB:
 
 ```console
-$ helm upgrade moodle my-repo/moodle --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set moodlePassword=$MOODLE_PASSWORD
+helm upgrade moodle my-repo/moodle --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set moodlePassword=$MOODLE_PASSWORD
 ```
 
 You should see the lines below in MariaDB container logs:
@@ -495,7 +486,7 @@ This upgrade also adapts the chart to the latest Bitnami good practices. Check t
 
 Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
 
-In https://github.com/helm/charts/pull/17301 the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
+In <https://github.com/helm/charts/pull/17301> the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
 
 This major version signifies this change.
 
@@ -505,8 +496,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 moodle:
 
 ```console
-$ kubectl patch deployment moodle-moodle --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl delete statefulset moodle-mariadb --cascade=false
+kubectl patch deployment moodle-moodle --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl delete statefulset moodle-mariadb --cascade=false
 ```
 
 ## Community supported solution
@@ -525,10 +516,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/mxnet/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/mxnet
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mxnet
 ```
 
 ## 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/mxnet
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mxnet
 ```
 
 These commands deploy Apache MXNet (Incubating) on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured.
@@ -46,7 +46,7 @@ These commands deploy Apache MXNet (Incubating) on the Kubernetes cluster in the
 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.
@@ -61,7 +61,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                  | Value           |
@@ -78,7 +77,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the the deployment(s)/statefulset(s)                   | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the the deployment(s)/statefulset(s)                      | `["infinity"]`  |
 
-
 ### Common Mxnet parameters
 
 | Name                                  | Description                                                                                                               | Value                 |
@@ -113,7 +111,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `sidecars`                            | Attach additional containers to the pods (scheduler, worker and server nodes)                                             | `[]`                  |
 | `initContainers`                      | Attach additional init containers to the pods (scheduler, worker and server nodes)                                        | `[]`                  |
 
-
 ### Mxnet Standalone parameters (only for standalone mode)
 
 | Name                                               | Description                                                                                          | Value           |
@@ -174,7 +171,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `standalone.customLivenessProbe`                   | Custom liveness probe for the Web component                                                          | `{}`            |
 | `standalone.customReadinessProbe`                  | Custom readiness probe for the Web component                                                         | `{}`            |
 
-
 ### Mxnet Server parameters (only for distributed mode)
 
 | Name                                           | Description                                                                                      | Value           |
@@ -236,7 +232,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `server.customLivenessProbe`                   | Custom liveness probe for the Web component                                                      | `{}`            |
 | `server.customReadinessProbe`                  | Custom readiness probe for the Web component                                                     | `{}`            |
 
-
 ### Mxnet Worker parameters (only for distributed mode)
 
 | Name                                           | Description                                                                                      | Value           |
@@ -298,7 +293,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `worker.customLivenessProbe`                   | Custom liveness probe for the Web component                                                      | `{}`            |
 | `worker.customReadinessProbe`                  | Custom readiness probe for the Web component                                                     | `{}`            |
 
-
 ### Mxnet Scheduler parameters (only for distributed mode)
 
 | Name                                              | Description                                                                                         | Value           |
@@ -370,7 +364,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `scheduler.service.sessionAffinity`               | Session Affinity for Kubernetes service, can be "None" or "ClientIP"                                | `None`          |
 | `scheduler.service.sessionAffinityConfig`         | Additional settings for the sessionAffinity                                                         | `{}`            |
 
-
 ### Init containers parameters
 
 | Name                                   | Description                                                                                                                       | Value                   |
@@ -391,7 +384,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.limits`   | The resources limits for the container                                                                                            | `{}`                    |
 | `volumePermissions.resources.requests` | The requested resources for the container                                                                                         | `{}`                    |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -407,7 +399,7 @@ The above command creates 6 pods for Apache MXNet (Incubating): one scheduler, t
 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/mxnet
+helm install my-release -f values.yaml my-repo/mxnet
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -591,22 +583,22 @@ This version also introduces `bitnami/common`, a [library chart](https://helm.sh
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ## License
 
@@ -616,10 +608,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/mysql/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/mysql
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mysql
 ```
 
 ## 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/mysql
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/mysql
 ```
 
 These commands deploy MySQL 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 MySQL 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.
@@ -60,7 +60,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                               | Value           |
@@ -77,7 +76,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                                      | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                                         | `["infinity"]`  |
 
-
 ### MySQL common parameters
 
 | Name                       | Description                                                                                                                                                                         | Value                 |
@@ -103,7 +101,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `initdbScripts`            | Dictionary of initdb scripts                                                                                                                                                        | `{}`                  |
 | `initdbScriptsConfigMap`   | ConfigMap with the initdb scripts (Note: Overrides `initdbScripts`)                                                                                                                 | `""`                  |
 
-
 ### MySQL Primary parameters
 
 | Name                                            | Description                                                                                                     | Value               |
@@ -192,7 +189,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `primary.pdb.maxUnavailable`                    | Maximum number/percentage of MySQL primary pods that may be made unavailable                                    | `""`                |
 | `primary.podLabels`                             | MySQL Primary pod label. If labels are same as commonLabels , this will take precedence                         | `{}`                |
 
-
 ### MySQL Secondary parameters
 
 | Name                                              | Description                                                                                                         | Value               |
@@ -282,7 +278,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `secondary.pdb.maxUnavailable`                    | Maximum number/percentage of MySQL secondary pods that may be made unavailable                                      | `""`                |
 | `secondary.podLabels`                             | Additional pod labels for MySQL secondary pods                                                                      | `{}`                |
 
-
 ### RBAC parameters
 
 | Name                                          | Description                                                    | Value   |
@@ -294,7 +289,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `rbac.create`                                 | Whether to create & use RBAC resources or not                  | `false` |
 | `rbac.rules`                                  | Custom RBAC rules to set                                       | `[]`    |
 
-
 ### Network Policy
 
 | Name                                       | Description                                                                                                     | Value   |
@@ -303,7 +297,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.allowExternal`              | The Policy model to apply.                                                                                      | `true`  |
 | `networkPolicy.explicitNamespacesSelector` | A Kubernetes LabelSelector to explicitly select namespaces from which ingress traffic could be allowed to MySQL | `{}`    |
 
-
 ### Volume Permissions parameters
 
 | Name                                  | Description                                                                                                                       | Value                   |
@@ -317,7 +310,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.image.pullSecrets` | Specify docker-registry secret names as an array                                                                                  | `[]`                    |
 | `volumePermissions.resources`         | Init container volume-permissions resources                                                                                       | `{}`                    |
 
-
 ### Metrics parameters
 
 | Name                                         | Description                                                                                                                    | Value                     |
@@ -364,7 +356,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRule.additionalLabels`    | Additional labels that can be used so prometheusRule will be discovered by Prometheus                                          | `{}`                      |
 | `metrics.prometheusRule.rules`               | Prometheus Rule definitions                                                                                                    | `[]`                      |
 
-
 The above parameters map to the env variables defined in [bitnami/mysql](https://github.com/bitnami/containers/tree/main/bitnami/mysql). For more information please refer to the [bitnami/mysql](https://github.com/bitnami/containers/tree/main/bitnami/mysql) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -382,7 +373,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/mysql
+helm install my-release -f values.yaml my-repo/mysql
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -450,7 +441,7 @@ To enable network policy for MySQL, install [a networking plugin that implements
 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:
 
 ```console
-$ kubectl annotate namespace default "net.beta.kubernetes.io/network-policy={\"ingress\":{\"isolation\":\"DefaultDeny\"}}"
+kubectl annotate namespace default "net.beta.kubernetes.io/network-policy={\"ingress\":{\"isolation\":\"DefaultDeny\"}}"
 ```
 
 With NetworkPolicy enabled, traffic will be limited to just port 3306.
@@ -473,7 +464,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:
 
 ```console
-$ helm upgrade my-release my-repo/mysql --set auth.rootPassword=[ROOT_PASSWORD]
+helm upgrade my-release my-repo/mysql --set auth.rootPassword=[ROOT_PASSWORD]
 ```
 
 | Note: you need to substitute the placeholder _[ROOT_PASSWORD]_ with the value obtained in the installation notes.
@@ -503,7 +494,7 @@ Affected values:
 ### To 8.0.0
 
 - Several parameters were renamed or disappeared in favor of new ones on this major version:
-  - The terms *master* and *slave* have been replaced by the terms *primary* and *secondary*. Therefore, parameters prefixed with `master` or `slave` are now prefixed with `primary` or `secondary`, respectively.
+  - The terms _master_ and _slave_ have been replaced by the terms _primary_ and _secondary_. Therefore, parameters prefixed with `master` or `slave` are now prefixed with `primary` or `secondary`, respectively.
   - Credentials parameters are reorganized under the `auth` parameter.
   - `replication.enabled` parameter is deprecated in favor of `architecture` parameter that accepts two values: `standalone` and `replication`.
 - Chart labels were adapted to follow the [Helm charts standard labels](https://helm.sh/docs/chart_best_practices/labels/#standard-labels).
@@ -516,7 +507,7 @@ Consequences:
   - 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`:
 
 ```console
-$ helm install mysql my-repo/mysql --set auth.rootPassword=[ROOT_PASSWORD] --set primary.persistence.existingClaim=[EXISTING_PVC]
+helm install mysql my-repo/mysql --set auth.rootPassword=[ROOT_PASSWORD] --set primary.persistence.existingClaim=[EXISTING_PVC]
 ```
 
 | Note: you need to substitute the placeholder _[EXISTING_PVC]_ with the name of the PVC used on your previous release, and _[ROOT_PASSWORD]_ with the root password used in your previous release.
@@ -533,8 +524,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 mysql:
 
 ```console
-$ kubectl delete statefulset mysql-master --cascade=false
-$ kubectl delete statefulset mysql-slave --cascade=false
+kubectl delete statefulset mysql-master --cascade=false
+kubectl delete statefulset mysql-slave --cascade=false
 ```
 
 ## License
@@ -545,10 +536,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/nats/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/nats
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/nats
 ```
 
 ## Introduction
@@ -31,8 +31,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/nats
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/nats
 ```
 
 The command deploys NATS on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -44,7 +44,7 @@ The command deploys NATS on the Kubernetes cluster in the default configuration.
 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.
@@ -58,7 +58,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imageRegistry`    | Global Docker image registry                    | `""`  |
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                  | Value           |
@@ -74,7 +73,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                         | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                            | `["infinity"]`  |
 
-
 ### NATS parameters
 
 | Name                     | Description                                                                                           | Value                 |
@@ -116,7 +114,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsCM`         | ConfigMap with extra environment variables                                                            | `""`                  |
 | `extraEnvVarsSecret`     | Secret with extra environment variables                                                               | `""`                  |
 
-
 ### NATS deployment/statefulset parameters
 
 | Name                                    | Description                                                                                           | Value           |
@@ -175,7 +172,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `initContainers`                        | Add additional init containers to the NATS pods                                                       | `[]`            |
 | `sidecars`                              | Add additional sidecar containers to the NATS pods                                                    | `[]`            |
 
-
 ### Traffic Exposure parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -213,7 +209,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.allowExternal`      | The Policy model to apply                                                                                                        | `true`                   |
 | `networkPolicy.additionalRules`    | Additional NetworkPolicy Ingress "from" rules to set. Note that all rules are OR-ed.                                             | `{}`                     |
 
-
 ### Metrics parameters
 
 | Name                                       | Description                                                                                            | Value                   |
@@ -222,7 +217,7 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.image.registry`                   | Prometheus metrics exporter image registry                                                             | `docker.io`             |
 | `metrics.image.repository`                 | Prometheus metrics exporter image repository                                                           | `bitnami/nats-exporter` |
 | `metrics.image.tag`                        | Prometheus metrics exporter image tag (immutable tags are recommended)                                 | `0.10.1-debian-11-r32`  |
-| `metrics.image.digest`                     | Petete image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""`                    |
+| `metrics.image.digest`                     | NATS Exporter image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""`             |
 | `metrics.image.pullPolicy`                 | Prometheus metrics image pull policy                                                                   | `IfNotPresent`          |
 | `metrics.image.pullSecrets`                | Prometheus metrics image pull secrets                                                                  | `[]`                    |
 | `metrics.resources`                        | Metrics exporter resource requests and limits                                                          | `{}`                    |
@@ -243,7 +238,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.serviceMonitor.relabelings`       | Specify general relabeling                                                                             | `[]`                    |
 | `metrics.serviceMonitor.selector`          | Prometheus instance selector labels                                                                    | `{}`                    |
 
-
 ### Persistence parameters
 
 | Name                       | Description                                                         | Value               |
@@ -255,7 +249,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `persistence.annotations`  | Annotations for the PVC                                             | `{}`                |
 | `persistence.selector`     | Selector to match an existing Persistent Volume for NATS's data PVC | `{}`                |
 
-
 ### Other parameters
 
 | Name                 | Description                                                    | Value   |
@@ -264,7 +257,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `pdb.minAvailable`   | Minimum number/percentage of pods that should remain scheduled | `1`     |
 | `pdb.maxUnavailable` | Maximum number/percentage of pods that may be made unavailable | `""`    |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -280,7 +272,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/nats
+helm install my-release -f values.yaml my-repo/nats
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -333,7 +325,7 @@ NATS version 2.0.0 has renamed the server binary filename from `gnatsd` to `nats
 however, it is still possible to use the chart to deploy NATS version 1.x.x using the `natsFilename` property.
 
 ```console
-$ helm install nats-v1 --set natsFilename=gnatsd --set image.tag=1.4.1 my-repo/nats
+helm install nats-v1 --set natsFilename=gnatsd --set image.tag=1.4.1 my-repo/nats
 ```
 
 ### To 7.0.0
@@ -377,7 +369,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 nats:
 
 ```console
-$ kubectl delete statefulset nats-nats --cascade=false
+kubectl delete statefulset nats-nats --cascade=false
 ```
 
 ## License
@@ -388,10 +380,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/nats/values.yaml

@@ -684,7 +684,7 @@ metrics:
   ## @param metrics.image.registry Prometheus metrics exporter image registry
   ## @param metrics.image.repository Prometheus metrics exporter image repository
   ## @param metrics.image.tag Prometheus metrics exporter image tag (immutable tags are recommended)
-  ## @param metrics.image.digest Petete image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag
+  ## @param metrics.image.digest NATS Exporter image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag
   ## @param metrics.image.pullPolicy Prometheus metrics image pull policy
   ## @param metrics.image.pullSecrets Prometheus metrics image pull secrets
   ##

bitnami/nginx-ingress-controller/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/nginx-ingress-controller
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/nginx-ingress-controller
 ```
 
 ## 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/nginx-ingress-controller
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/nginx-ingress-controller
 ```
 
 These commands deploy nginx-ingress-controller on the Kubernetes cluster in the default configuration.
@@ -46,7 +46,7 @@ These commands deploy nginx-ingress-controller on the Kubernetes cluster in the
 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.
@@ -60,7 +60,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imageRegistry`    | Global Docker image registry                    | `""`  |
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                          | Value           |
@@ -74,7 +73,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraDeploy`       | Array of extra objects to deploy with the release                    | `[]`            |
 | `clusterDomain`     | Kubernetes cluster domain name                                       | `cluster.local` |
 
-
 ### Nginx Ingress Controller parameters
 
 | Name                                   | Description                                                                                                                                        | Value                              |
@@ -118,7 +116,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsCM`                       | Name of a existing ConfigMap containing extra environment variables                                                                                | `""`                               |
 | `extraEnvVarsSecret`                   | Name of a existing Secret containing extra environment variables                                                                                   | `""`                               |
 
-
 ### Nginx Ingress deployment / daemonset parameters
 
 | Name                                                | Description                                                                                                                                 | Value          |
@@ -185,7 +182,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `topologySpreadConstraints`                         | Topology spread constraints rely on node labels to identify the topology domain(s) that each Node is in                                     | `[]`           |
 | `podSecurityPolicy.enabled`                         | Whether to create a PodSecurityPolicy. WARNING: PodSecurityPolicy is deprecated in Kubernetes v1.21 or later, unavailable in v1.25 or later | `false`        |
 
-
 ### Default backend parameters
 
 | Name                                                   | Description                                                                                                     | Value                  |
@@ -261,7 +257,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `defaultBackend.pdb.minAvailable`                      | Minimum number/percentage of Default backend pods that should remain scheduled                                  | `1`                    |
 | `defaultBackend.pdb.maxUnavailable`                    | Maximum number/percentage of Default backend pods that may be made unavailable                                  | `""`                   |
 
-
 ### Traffic exposure parameters
 
 | Name                               | Description                                                                                                                            | Value          |
@@ -282,7 +277,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `service.sessionAffinity`          | Session Affinity for Kubernetes service, can be "None" or "ClientIP"                                                                   | `None`         |
 | `service.sessionAffinityConfig`    | Additional settings for the sessionAffinity                                                                                            | `{}`           |
 
-
 ### RBAC parameters
 
 | Name                                          | Description                                                    | Value  |
@@ -294,7 +288,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `rbac.create`                                 | Specifies whether RBAC rules should be created                 | `true` |
 | `rbac.rules`                                  | Custom RBAC rules                                              | `[]`   |
 
-
 ### Other parameters
 
 | Name                       | Description                                                               | Value   |
@@ -308,7 +301,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `autoscaling.targetCPU`    | Target CPU utilization percentage                                         | `""`    |
 | `autoscaling.targetMemory` | Target Memory utilization percentage                                      | `""`    |
 
-
 ### Metrics parameters
 
 | Name                                       | Description                                                                       | Value       |
@@ -334,7 +326,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRule.namespace`         | Namespace which Prometheus is running in                                          | `""`        |
 | `metrics.prometheusRule.rules`             | Rules to be prometheus in YAML format, check values for an example                | `[]`        |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -348,7 +339,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/nginx-ingress-controller
+helm install my-release -f values.yaml my-repo/nginx-ingress-controller
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -450,9 +441,9 @@ Consequences:
 
 #### Useful links**
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 1.0.0
 
@@ -475,10 +466,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/nginx/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/nginx
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/nginx
 ```
 
 ## 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/nginx
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/nginx
 ```
 
 These commands deploy NGINX Open Source on the Kubernetes cluster in the default configuration.
@@ -46,7 +46,7 @@ These commands deploy NGINX Open Source on the Kubernetes cluster in the default
 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.
@@ -60,7 +60,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imageRegistry`    | Global Docker image registry                    | `""`  |
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value           |
@@ -77,7 +76,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the the deployment(s)/statefulset(s)              | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the the deployment(s)/statefulset(s)                 | `["infinity"]`  |
 
-
 ### NGINX parameters
 
 | Name                 | Description                                                                                           | Value                  |
@@ -96,7 +94,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsCM`     | ConfigMap with extra environment variables                                                            | `""`                   |
 | `extraEnvVarsSecret` | Secret with extra environment variables                                                               | `""`                   |
 
-
 ### NGINX deployment parameters
 
 | Name                                          | Description                                                                               | Value           |
@@ -171,7 +168,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `pdb.minAvailable`                            | Min number of pods that must still be available after the eviction                        | `1`             |
 | `pdb.maxUnavailable`                          | Max number of pods that can be unavailable after the eviction                             | `0`             |
 
-
 ### Custom NGINX application parameters
 
 | Name                                       | Description                                                                                         | Value                 |
@@ -197,7 +193,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `staticSiteConfigmap`                      | Name of existing ConfigMap with the server static site content                                      | `""`                  |
 | `staticSitePVC`                            | Name of existing PVC with the server static site content                                            | `""`                  |
 
-
 ### Traffic Exposure parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -243,7 +238,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `healthIngress.ingressClassName`   | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `healthIngress.extraRules`         | The list of additional rules to be added to this ingress record. Evaluated as a template                                         | `[]`                     |
 
-
 ### Metrics parameters
 
 | Name                                       | Description                                                                                                                               | Value                    |
@@ -278,7 +272,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRule.additionalLabels`  | Additional labels that can be used so PrometheusRule will be discovered by Prometheus                                                     | `{}`                     |
 | `metrics.prometheusRule.rules`             | Prometheus Rule definitions                                                                                                               | `[]`                     |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -292,7 +285,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/nginx
+helm install my-release -f values.yaml my-repo/nginx
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -412,24 +405,24 @@ On 9 April 2022, security vulnerabilities in the [NGINX LDAP reference implement
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 7.0.0
 
@@ -448,8 +441,8 @@ Backwards compatibility is not guaranteed unless you modify the labels used on t
 Use the workaround below to upgrade from versions previous to 5.0.0. The following example assumes that the release name is nginx:
 
 ```console
-$ kubectl delete deployment nginx --cascade=false
-$ helm upgrade nginx my-repo/nginx
+kubectl delete deployment nginx --cascade=false
+helm upgrade nginx my-repo/nginx
 ```
 
 ### To 1.0.0
@@ -458,7 +451,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 nginx:
 
 ```console
-$ kubectl patch deployment nginx --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl patch deployment nginx --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
 ```
 
 ## Bitnami Kubernetes Documentation
@@ -479,10 +472,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/node-exporter/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/node-exporter
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/node-exporter
 ```
 
 ## Introduction
@@ -31,8 +31,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/node-exporter
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/node-exporter
 ```
 
 The command deploys Node Exporter on the Kubernetes cluster in the default configuration. The [configuration](#configuration-and-installation-details) section lists the parameters that can be configured during installation.
@@ -42,7 +42,7 @@ The command deploys Node Exporter on the Kubernetes cluster in the default confi
 To uninstall/delete the `my-release` release:
 
 ```console
-$ helm delete my-release
+helm delete my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -57,7 +57,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                  | Value           |
@@ -74,7 +73,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the the deployment(s)/statefulset(s)                   | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the the deployment(s)/statefulset(s)                      | `["infinity"]`  |
 
-
 ### Node Exporter parameters
 
 | Name                                          | Description                                                                                                                                                        | Value                   |
@@ -174,17 +172,16 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceMonitor.labels`                       | Extra labels for the ServiceMonitor                                                                                                                                | `{}`                    |
 | `serviceMonitor.honorLabels`                  | honorLabels chooses the metric's labels on collisions with target labels                                                                                           | `false`                 |
 
-
 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.
 
 ```console
-$ helm install my-release --set minReadySeconds=120 my-repo/node-exporter
+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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/node-exporter
+helm install my-release -f values.yaml my-repo/node-exporter
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -210,7 +207,7 @@ Find more information about how to deal with common errors related to Bitnami's
 ## Upgrading
 
 ```console
-$ helm upgrade my-release my-repo/node-exporter
+helm upgrade my-release my-repo/node-exporter
 ```
 
 ### To 3.0.0
@@ -218,6 +215,7 @@ $ helm upgrade my-release my-repo/node-exporter
 This major release renames several values in this chart and adds missing features, in order to be aligned with the rest of the assets in the Bitnami charts repository.
 
 Affected values:
+
 - `service.port` was renamed as `service.ports.metrics`.
 - `service.targetPort` was renamed as `containerPorts.metrics`.
 - `service.nodePort` was renamed as `service.nodePorts.metrics`.
@@ -242,10 +240,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/oauth2-proxy/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ 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
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ 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.
@@ -48,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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value           |
@@ -79,7 +78,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                    | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                       | `["infinity"]`  |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -111,7 +109,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.secrets`                  | Custom TLS certificates as secrets                                                                                               | `[]`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### OAuth2 Proxy Image parameters
 
 | Name                | Description                                                                                                  | Value                  |
@@ -123,7 +120,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `image.pullPolicy`  | OAuth2 Proxy image pull policy                                                                               | `IfNotPresent`         |
 | `image.pullSecrets` | OAuth2 Proxy image pull secrets                                                                              | `[]`                   |
 
-
 ### OAuth2 Proxy configuration parameters
 
 | Name                                                   | Description                                                                                              | Value              |
@@ -149,7 +145,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `configuration.redirectUrl`                            | OAuth Redirect URL                                                                                       | `""`               |
 | `configuration.whiteList`                              | Allowed domains for redirection after authentication. Prefix domain with a . or a *. to allow subdomains | `""`               |
 
-
 ### OAuth2 Proxy deployment parameters
 
 | Name                                          | Description                                                                                      | Value           |
@@ -220,7 +215,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account                                   | `true`          |
 | `serviceAccount.annotations`                  | Annotations for service account. Evaluated as a template. Only used if `create` is `true`.       | `{}`            |
 
-
 ### External Redis® parameters
 
 | Name                           | Description                                                | Value  |
@@ -230,7 +224,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalRedis.port`           | External Redis® server port                            | `6379` |
 | `externalRedis.existingSecret` | The name of an existing secret with Redis® credentials | `""`   |
 
-
 ### Redis® sub-chart parameters
 
 | Name                                   | Description                                                | Value        |
@@ -248,8 +241,7 @@ The command removes all the Kubernetes components associated with the chart and
 | `redis.sentinel.service.port`          | Redis® (with Sentinel) service port                    | `6379`       |
 | `redis.sentinel.service.sentinelPort`  | Redis® (with Sentinel) sentinel service port           | `26379`      |
 
-
-See https://github.com/bitnami-labs/readmenator to create the table
+See <https://github.com/bitnami-labs/readmenator> to create the table
 
 The above parameters map to the env variables defined in [bitnami/oauth2-proxy](https://github.com/bitnami/containers/tree/main/bitnami/oauth2-proxy). For more information please refer to the [bitnami/oauth2-proxy](https://github.com/bitnami/containers/tree/main/bitnami/oauth2-proxy) image documentation.
 
@@ -268,7 +260,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)
@@ -333,10 +325,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/odoo/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/odoo
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/odoo
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/odoo
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/odoo
 ```
 
 The command deploys Odoo on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,14 +48,12 @@ The command deploys Odoo on the Kubernetes cluster in the default configuration.
 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.
 > If persistence.resourcePolicy is set to keep, you should manually delete the PVCs.
 
-
-
 ## Parameters
 
 ### Global parameters
@@ -66,7 +64,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                          | Value                         |
@@ -89,7 +86,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `image.pullSecrets`      | Odoo image pull secrets                                                                              | `[]`                          |
 | `image.debug`            | Enable image debug mode                                                                              | `false`                       |
 
-
 ### Odoo Configuration parameters
 
 | Name                    | Description                                                          | Value              |
@@ -113,7 +109,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsCM`        | Name of existing ConfigMap containing extra env vars                 | `""`               |
 | `extraEnvVarsSecret`    | Name of existing Secret containing extra env vars                    | `""`               |
 
-
 ### Odoo deployment parameters
 
 | Name                                 | Description                                                                                                              | Value           |
@@ -174,7 +169,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `sidecars`                           | Add additional sidecar containers to the Odoo pod                                                                        | `[]`            |
 | `initContainers`                     | Add additional init containers to the Odoo pods                                                                          | `[]`            |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -205,7 +199,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.secrets`                  | Custom TLS certificates as secrets                                                                                               | `[]`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Persistence Parameters
 
 | Name                                                   | Description                                                                                                                           | Value           |
@@ -226,7 +219,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.containerSecurityContext.enabled`   | Enable init container's Security Context                                                                                              | `true`          |
 | `volumePermissions.containerSecurityContext.runAsUser` | Set init container's Security Context runAsUser                                                                                       | `0`             |
 
-
 ### RBAC Parameters
 
 | Name                                          | Description                                                                                              | Value   |
@@ -236,7 +228,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.automountServiceAccountToken` | Auto-mount the service account token in the pod                                                          | `false` |
 | `serviceAccount.annotations`                  | Additional custom annotations for the ServiceAccount                                                     | `{}`    |
 
-
 ### Other Parameters
 
 | Name                       | Description                                                    | Value   |
@@ -250,7 +241,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `autoscaling.targetCPU`    | Target CPU utilization percentage                              | `50`    |
 | `autoscaling.targetMemory` | Target Memory utilization percentage                           | `50`    |
 
-
 ### Database Parameters
 
 | Name                                                 | Description                                                              | Value          |
@@ -273,7 +263,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.existingSecretPasswordKey`         | Name of an existing secret key containing the non-root credentials       | `""`           |
 | `externalDatabase.existingSecretPostgresPasswordKey` | Name of an existing secret key containing the admin credentials          | `""`           |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                          | Description                                                                                                              | Value   |
@@ -291,7 +280,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.denyConnectionsToExternal`         | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                           | `false` |
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                               | `{}`    |
 
-
 The above parameters map to the env variables defined in [bitnami/odoo](https://github.com/bitnami/containers/tree/main/bitnami/odoo). For more information please refer to the [bitnami/odoo](https://github.com/bitnami/containers/tree/main/bitnami/odoo) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -309,7 +297,7 @@ The above command sets the Odoo administrator account password to `password` and
 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/odoo
+helm install my-release -f values.yaml my-repo/odoo
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -399,10 +387,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/opencart/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/opencart
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/opencart
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/opencart
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/opencart
 ```
 
 The command deploys OpenCart on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys OpenCart 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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                                  | Value |
@@ -76,7 +75,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `commonLabels`      | Common labels to add to all OpenCart resources (sub-charts are not considered). Evaluated as a template      | `{}`  |
 | `extraDeploy`       | Array of extra objects to deploy with the release (evaluated as a template)                                  | `[]`  |
 
-
 ### OpenCart parameters
 
 | Name                                    | Description                                                                                              | Value                   |
@@ -167,7 +165,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `podAnnotations`                        | Pod annotations                                                                                          | `{}`                    |
 | `podLabels`                             | Add additional labels to the pod (evaluated as a template)                                               | `{}`                    |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -199,7 +196,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.ingressClassName`         | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Database parameters
 
 | Name                                        | Description                                                                              | Value               |
@@ -223,7 +219,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.database`                 | Name of the existing database                                                            | `bitnami_opencart`  |
 | `externalDatabase.existingSecret`           | Name of an existing secret resource containing the DB password                           | `""`                |
 
-
 ### Volume Permissions parameters
 
 | Name                                   | Description                                                                                                                                               | Value                   |
@@ -238,7 +233,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.limits`   | The resources limits for the container                                                                                                                    | `{}`                    |
 | `volumePermissions.resources.requests` | The requested resources for the container                                                                                                                 | `{}`                    |
 
-
 ### Metrics parameters
 
 | Name                        | Description                                                                                                     | Value                     |
@@ -253,7 +247,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.resources`         | Metrics exporter resource requests and limits                                                                   | `{}`                      |
 | `metrics.podAnnotations`    | Metrics exporter pod Annotation and Labels                                                                      | `{}`                      |
 
-
 ### Certificate injection parameters
 
 | Name                                                 | Description                                                                                                       | Value                                    |
@@ -277,7 +270,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `certificates.image.pullPolicy`                      | Container sidecar image pull policy                                                                               | `IfNotPresent`                           |
 | `certificates.image.pullSecrets`                     | Container sidecar image pull secrets                                                                              | `[]`                                     |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                          | Description                                                                                                                  | Value   |
@@ -298,7 +290,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.denyConnectionsToExternal`         | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                               | `false` |
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                                   | `{}`    |
 
-
 The above parameters map to the env variables defined in [bitnami/opencart](https://github.com/bitnami/containers/tree/main/bitnami/opencart). For more information please refer to the [bitnami/opencart](https://github.com/bitnami/containers/tree/main/bitnami/opencart) image documentation.
 
 > **Note**:
@@ -330,7 +321,7 @@ The above command sets the OpenCart 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/opencart
+helm install my-release -f values.yaml my-repo/opencart
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -381,7 +372,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
 1. Install the chart
 
 ```console
-$ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/prestashop
+helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/prestashop
 ```
 
 ### Host path
@@ -397,7 +388,7 @@ $ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/prest
 1. Install the chart
 
     ```console
-    $ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/prestashop
+    helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/prestashop
     ```
 
     This will mount the `prestashop-data` volume into the `hostPath` directory. The site data will be persisted if the mount path contains valid data, else the site data will be initialized at first launch.
@@ -436,24 +427,24 @@ This version standardizes the way of defining Ingress rules. When configuring a
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 8.0.0
 
@@ -465,10 +456,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
@@ -496,7 +487,7 @@ MariaDB dependency version was bumped to a new major version that introduces sev
 
 Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
 
-In https://github.com/helm/charts/pull/17302 the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
+In <https://github.com/helm/charts/pull/17302> the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
 
 This major version signifies this change.
 
@@ -506,8 +497,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 opencart:
 
 ```console
-$ kubectl patch deployment opencart-opencart --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl delete statefulset opencart-mariadb --cascade=false
+kubectl patch deployment opencart-opencart --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl delete statefulset opencart-mariadb --cascade=false
 ```
 
 ## Community supported solution
@@ -526,10 +517,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/osclass/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/osclass
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/osclass
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/osclass
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/osclass
 ```
 
 The command deploys Osclass on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys Osclass 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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                        | Value |
@@ -75,7 +74,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `commonLabels`      | Labels to add to all deployed objects              | `{}`  |
 | `extraDeploy`       | Array of extra objects to deploy with the release  | `[]`  |
 
-
 ### Osclass Image parameters
 
 | Name                | Description                                                                                             | Value                |
@@ -88,7 +86,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `image.pullSecrets` | Osclass image pull secrets                                                                              | `[]`                 |
 | `image.debug`       | Enable Bitnami debug mode in Osclass image                                                              | `false`              |
 
-
 ### Osclass Configuration parameters
 
 | Name                 | Description                                            | Value              |
@@ -106,7 +103,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `smtpPassword`       | SMTP user password                                     | `""`               |
 | `smtpProtocol`       | SMTP protocol                                          | `""`               |
 
-
 ### Osclass deployment parameters
 
 | Name                                                 | Description                                                                                                     | Value                                    |
@@ -190,7 +186,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `schedulerName`                                      | Name of the k8s scheduler (other than default)                                                                  | `""`                                     |
 | `topologySpreadConstraints`                          | Topology Spread Constraints for pod assignment                                                                  | `[]`                                     |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -222,7 +217,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.ingressClassName`         | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Database Parameters
 
 | Name                                       | Description                                                                                                   | Value                   |
@@ -260,7 +254,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.limits`       | The resources limits for the init container                                                                   | `{}`                    |
 | `volumePermissions.resources.requests`     | The requested resources for the init container                                                                | `{}`                    |
 
-
 ### Other Parameters
 
 | Name                       | Description                                                    | Value   |
@@ -274,7 +267,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `autoscaling.targetCPU`    | Target CPU utilization percentage                              | `50`    |
 | `autoscaling.targetMemory` | Target Memory utilization percentage                           | `50`    |
 
-
 ### Metrics Parameters
 
 | Name                                       | Description                                                                                                     | Value                     |
@@ -303,7 +295,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.serviceMonitor.labels`            | Extra labels for the ServiceMonitor                                                                             | `{}`                      |
 | `metrics.serviceMonitor.jobLabel`          | The name of the label on the target service to use as the job name in prometheus.                               | `""`                      |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                          | Description                                                                                                                 | Value   |
@@ -324,7 +315,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.denyConnectionsToExternal`         | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                              | `false` |
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                                  | `{}`    |
 
-
 The above parameters map to the env variables defined in [bitnami/osclass](https://github.com/bitnami/containers/tree/main/bitnami/osclass). For more information please refer to the [bitnami/osclass](https://github.com/bitnami/containers/tree/main/bitnami/osclass) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -342,7 +332,7 @@ The above command sets the Osclass 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/osclass
+helm install my-release -f values.yaml my-repo/osclass
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -462,12 +452,12 @@ Consequences:
 - Backwards compatibility is not guaranteed. However, you can easily workaround this issue by removing Osclass deployment before upgrading (the following example assumes that the release name is `osclass`):
 
 ```console
-$ export APP_HOST=$(kubectl get svc --namespace default osclass --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
-$ export APP_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)
-$ kubectl delete deployments.apps osclass
-$ helm upgrade osclass my-repo/osclass --set osclassHost=$APP_HOST,osclassPassword=$APP_PASSWORD,mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD,mariadb.auth.password=$MARIADB_PASSWORD
+export APP_HOST=$(kubectl get svc --namespace default osclass --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")
+export APP_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)
+kubectl delete deployments.apps osclass
+helm upgrade osclass my-repo/osclass --set osclassHost=$APP_HOST,osclassPassword=$APP_PASSWORD,mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD,mariadb.auth.password=$MARIADB_PASSWORD
 ```
 
 ### To 8.0.0
@@ -479,30 +469,30 @@ In this major there were two main changes introduced:
 
 Please read the update notes carefully.
 
-**1. Adaptation to Helm v2 EOL**
+#### 1. Adaptation to Helm v2 EOL
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+##### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+##### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+##### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
-**2. Updated MariaDB dependency version**
+#### 2. Updated MariaDB dependency version
 
 In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-800) for more information.
 
@@ -513,31 +503,31 @@ 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:
 
 ```console
-  $ kubectl delete deployments.apps osclass
+  kubectl delete deployments.apps osclass
 
-  $ kubectl delete statefulsets.apps osclass-mariadb --cascade=false
+  kubectl delete statefulsets.apps osclass-mariadb --cascade=false
 ```
 
 Now the upgrade works:
 
 ```console
-$ helm upgrade osclass my-repo/osclass --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set osclassPassword=$OSCLASS_PASSWORD --set osclassHost=$OSCLASS_HOST
+helm upgrade osclass my-repo/osclass --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set osclassPassword=$OSCLASS_PASSWORD --set osclassHost=$OSCLASS_HOST
 ```
 
 You will have to delete the existing MariaDB pod and the new statefulset is going to create a new one
 
   ```console
-  $ kubectl delete pod osclass-mariadb-0
+  kubectl delete pod osclass-mariadb-0
   ```
 
 Finally, you should see the lines below in MariaDB container logs:
@@ -554,7 +544,7 @@ mariadb 12:13:25.01 INFO  ==> Running mysql_upgrade
 
 Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
 
-In https://github.com/helm/charts/pull/17303 the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
+In <https://github.com/helm/charts/pull/17303> the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
 
 This major version signifies this change.
 
@@ -564,8 +554,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 osclass:
 
 ```console
-$ kubectl patch deployment osclass-osclass --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl delete statefulset osclass-mariadb --cascade=false
+kubectl patch deployment osclass-osclass --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl delete statefulset osclass-mariadb --cascade=false
 ```
 
 ## Community supported solution
@@ -584,10 +574,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/parse/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/parse
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/parse
 ```
 
 ## 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/parse
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/parse
 ```
 
 The command deploys Parse 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 @@ The command deploys Parse on the Kubernetes cluster in the default configuration
 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.
@@ -61,7 +61,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common Parameters
 
 | Name                     | Description                                                                                  | Value          |
@@ -77,7 +76,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                         | `["sleep"]`    |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                            | `["infinity"]` |
 
-
 ### Parse server parameters
 
 | Name                                                     | Description                                                                                                              | Value                |
@@ -162,7 +160,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `server.service.sessionAffinity`                         | Control where client requests go, to the same pod or round-robin                                                         | `None`               |
 | `server.service.sessionAffinityConfig`                   | Additional settings for the sessionAffinity                                                                              | `{}`                 |
 
-
 ### Dashboard Parameters
 
 | Name                                                        | Description                                                                                                              | Value                     |
@@ -247,7 +244,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `dashboard.service.sessionAffinity`                         | Control where client requests go, to the same pod or round-robin                                                         | `None`                    |
 | `dashboard.service.sessionAffinityConfig`                   | Additional settings for the sessionAffinity                                                                              | `{}`                      |
 
-
 ### Traffic Exposure Parameters
 
 | Name                           | Description                                                                                                                      | Value                    |
@@ -271,7 +267,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.secrets`              | If you're providing your own certificates, please use this to add the certificates as secrets                                    | `[]`                     |
 | `ingress.extraRules`           | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Persistence Parameters
 
 | Name                        | Description                                                            | Value               |
@@ -285,7 +280,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `persistence.dataSource`    | Custom PVC data source                                                 | `{}`                |
 | `persistence.annotations`   | Persistent Volume Claim annotations                                    | `{}`                |
 
-
 ### Volume Permissions parameters
 
 | Name                                          | Description                                                                                                                                               | Value                   |
@@ -303,7 +297,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.annotations`                  | Additional Service Account annotations (evaluated as a template)                                                                                          | `{}`                    |
 | `serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account                                                                                            | `true`                  |
 
-
 ### MongoDB® Parameters
 
 | Name                               | Description                                 | Value           |
@@ -319,7 +312,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `mongodb.persistence.accessMode`   | PVC Access Mode for MongoDB® volume     | `ReadWriteOnce` |
 | `mongodb.persistence.size`         | PVC Storage Request for MongoDB® volume | `8Gi`           |
 
-
 The above parameters map to the env variables defined in [bitnami/parse](https://github.com/bitnami/containers/tree/main/bitnami/parse). For more information please refer to the [bitnami/parse](https://github.com/bitnami/containers/tree/main/bitnami/parse) image documentation.
 
 > **Note**:
@@ -351,7 +343,7 @@ The above command sets the Parse administrator account username and password to
 Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/parse
+helm install my-release -f values.yaml my-repo/parse
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -458,13 +450,13 @@ Affected values:
 
 Also MongoDB® subchart container images were updated to 5.0.x and it can affect compatibility with older versions of MongoDB®.
 
-- https://github.com/bitnami/charts/tree/main/bitnami/mongodb#to-1200
+- <https://github.com/bitnami/charts/tree/main/bitnami/mongodb#to-1200>
 
 ### To 16.0.0
 
 In this version, the mongodb-exporter bundled as part of the bitnami/mongodb dependency was updated to a new version which, even it is not a major change, can contain breaking changes (from `0.11.X` to `0.30.X`).
 
-Please visit the release notes from the upstream project at https://github.com/percona/mongodb_exporter/releases
+Please visit the release notes from the upstream project at <https://github.com/percona/mongodb_exporter/releases>
 
 ### To 15.0.0
 
@@ -480,37 +472,36 @@ This version standardizes the way of defining Ingress rules. When configuring a
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
-
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+#### Useful links
 
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 12.0.0
 
 MongoDB&reg; subchart container images were updated to 4.4.x and it can affect compatibility with older versions of MongoDB&reg;.
 
-- https://github.com/bitnami/charts/tree/main/bitnami/mongodb#to-900
+- <https://github.com/bitnami/charts/tree/main/bitnami/mongodb#to-900>
 
 ### To 11.0.0
 
 Backwards compatibility is not guaranteed since breaking changes were included in MongoDB&reg; subchart. More information in the link below:
 
-- https://github.com/bitnami/charts/tree/main/bitnami/mongodb#to-800
+- <https://github.com/bitnami/charts/tree/main/bitnami/mongodb#to-800>
 
 ### To 10.0.0
 
@@ -523,14 +514,14 @@ Backwards compatibility is not guaranteed. The following notables changes were i
 
 Parse & Parse Dashboard containers were moved to a non-root approach. There shouldn't be any issue when upgrading since the corresponding `securityContext` is enabled by default. Both container images and chart can be upgraded by running the command below:
 
-```
-$ helm upgrade my-release my-repo/parse
+```console
+helm upgrade my-release my-repo/parse
 ```
 
 If you use a previous container image (previous to **3.1.2-r14** for Parse or **1.2.0-r69** for Parse Dashboard), disable the `securityContext` by running the command below:
 
-```
-$ helm upgrade my-release my-repo/parse --set server.securityContext.enabled=false,dashboard.securityContext.enabled=false,server.image.tag=XXX,dashboard.image.tag=YYY
+```console
+helm upgrade my-release my-repo/parse --set server.securityContext.enabled=false,dashboard.securityContext.enabled=false,server.image.tag=XXX,dashboard.image.tag=YYY
 ```
 
 ### To 3.0.0
@@ -539,9 +530,9 @@ 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 parse:
 
 ```console
-$ kubectl patch deployment parse-parse-dashboard --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl patch deployment parse-parse-server --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl patch deployment parse-mongodb --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl patch deployment parse-parse-dashboard --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl patch deployment parse-parse-server --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl patch deployment parse-mongodb --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
 ```
 
 ## License
@@ -552,10 +543,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/phpbb/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/phpbb
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/phpbb
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/phpbb
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/phpbb
 ```
 
 The command deploys phpBB on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys phpBB on the Kubernetes cluster in the default configuration
 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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                               | Value |
@@ -76,7 +75,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `commonLabels`      | Common labels to add to all phpBB resources (sub-charts are not considered). Evaluated as a template      | `{}`  |
 | `extraDeploy`       | Array of extra objects to deploy with the release (evaluated as a template)                               | `[]`  |
 
-
 ### phpBB parameters
 
 | Name                                    | Description                                                                                                                                               | Value                   |
@@ -172,7 +170,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `podAnnotations`                        | Pod annotations                                                                                                                                           | `{}`                    |
 | `podLabels`                             | Pod extra labels                                                                                                                                          | `{}`                    |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -204,7 +201,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.ingressClassName`         | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Database parameters
 
 | Name                                        | Description                                                                          | Value               |
@@ -228,7 +224,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.password`                 | Password for the above username                                                      | `""`                |
 | `externalDatabase.database`                 | Name of the existing database                                                        | `bitnami_phpbb`     |
 
-
 ### Metrics parameters
 
 | Name                        | Description                                                                                                     | Value                     |
@@ -243,7 +238,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.resources`         | Metrics exporter resource requests and limits                                                                   | `{}`                      |
 | `metrics.podAnnotations`    | Additional annotations for Metrics exporter pod                                                                 | `{}`                      |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                          | Description                                                                                                               | Value   |
@@ -264,7 +258,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.denyConnectionsToExternal`         | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                            | `false` |
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                                | `{}`    |
 
-
 The above parameters map to the env variables defined in [bitnami/phpbb](https://github.com/bitnami/containers/tree/main/bitnami/phpbb). For more information please refer to the [bitnami/phpbb](https://github.com/bitnami/containers/tree/main/bitnami/phpbb) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -282,7 +275,7 @@ The above command sets the phpBB administrator account username and password to
 Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/phpbb
+helm install my-release -f values.yaml my-repo/phpbb
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -385,30 +378,30 @@ In this major there were two main changes introduced:
 
 Please read the update notes carefully.
 
-**1. Adaptation to Helm v2 EOL**
+#### 1. Adaptation to Helm v2 EOL
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+##### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+##### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+##### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
-**2. Updated MariaDB dependency version**
+#### 2. Updated MariaDB dependency version
 
 In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-800) for more information.
 
@@ -419,22 +412,22 @@ 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:
 
 ```console
-$ helm upgrade phpbb my-repo/phpbb --set phpbbPassword=$PHPBB_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 8.0.5
+helm upgrade phpbb my-repo/phpbb --set phpbbPassword=$PHPBB_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 8.0.5
 ```
 
 Finally, upgrade you release to 9.0.0 reusing the existing PVC, and enabling back MariaDB:
 
 ```console
-$ helm upgrade phpbb my-repo/phpbb --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set phpbbPassword=$PHPBB_PASSWORD
+helm upgrade phpbb my-repo/phpbb --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set phpbbPassword=$PHPBB_PASSWORD
 ```
 
 You should see the lines below in MariaDB container logs:
@@ -464,7 +457,7 @@ This upgrade also adapts the chart to the latest Bitnami good practices. Check t
 
 Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
 
-In https://github.com/helm/charts/pull/17307 the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
+In <https://github.com/helm/charts/pull/17307> the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
 
 This major version signifies this change.
 
@@ -474,8 +467,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 phpbb:
 
 ```console
-$ kubectl patch deployment phpbb-phpbb --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl delete statefulset phpbb-mariadb --cascade=false
+kubectl patch deployment phpbb-phpbb --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl delete statefulset phpbb-mariadb --cascade=false
 ```
 
 ## Community supported solution
@@ -494,10 +487,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/phpmyadmin/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/phpmyadmin
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/phpmyadmin
 ```
 
 ## 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/phpmyadmin
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/phpmyadmin
 ```
 
 The command deploys phpMyAdmin on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -46,7 +46,7 @@ The command deploys phpMyAdmin 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.
@@ -60,7 +60,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imageRegistry`    | Global Docker image registry                    | `""`  |
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                  | Value           |
@@ -73,7 +72,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `clusterDomain`     | Kubernetes Cluster Domain                                                                    | `cluster.local` |
 | `extraDeploy`       | Array of extra objects to deploy with the release                                            | `[]`            |
 
-
 ### phpMyAdmin parameters
 
 | Name                 | Description                                                                                                | Value                |
@@ -92,7 +90,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsCM`     | Name of a existing ConfigMap containing extra env vars                                                     | `""`                 |
 | `extraEnvVarsSecret` | Name of a existing Secret containing extra env vars                                                        | `""`                 |
 
-
 ### phpMyAdmin deployment parameters
 
 | Name                                    | Description                                                                               | Value           |
@@ -153,7 +150,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `initContainers`                        | Add init containers to the PhpMyAdmin pods                                                | `[]`            |
 | `sidecars`                              | Add sidecar containers to the PhpMyAdmin pods                                             | `[]`            |
 
-
 ### Traffic Exposure parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -186,7 +182,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.ingressClassName`         | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Database parameters
 
 | Name                       | Description                                                       | Value   |
@@ -204,7 +199,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `db.ssl.verify`            | Enable SSL certificate validation                                 | `true`  |
 | `mariadb`                  | MariaDB chart configuration                                       | `{}`    |
 
-
 ### Other Parameters
 
 | Name                                          | Description                                                            | Value   |
@@ -214,7 +208,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.automountServiceAccountToken` | Allows auto mount of ServiceAccountToken on the serviceAccount created | `true`  |
 | `serviceAccount.annotations`                  | Additional custom annotations for the ServiceAccount                   | `{}`    |
 
-
 ### Metrics parameters
 
 | Name                                       | Description                                                                                                     | Value                     |
@@ -247,7 +240,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.serviceMonitor.honorLabels`       | Specify honorLabels parameter to add the scrape endpoint                                                        | `false`                   |
 | `metrics.serviceMonitor.selector`          | ServiceMonitor selector labels                                                                                  | `{}`                      |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                          | Description                                                                                                                    | Value   |
@@ -268,7 +260,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.denyConnectionsToExternal`         | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                                 | `false` |
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                                     | `{}`    |
 
-
 For more information please refer to the [bitnami/phpmyadmin](https://github.com/bitnami/containers/tree/main/bitnami/phpmyadmin) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -283,7 +274,7 @@ The above command sets the phpMyAdmin to connect to a database in `mymariadb` ho
 Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/phpmyadmin
+helm install my-release -f values.yaml my-repo/phpmyadmin
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -426,10 +417,10 @@ Consequences:
 - Backwards compatibility is not guaranteed. However, you can easily workaround this issue by removing PhpMyAdmin deployment before upgrading (the following example assumes that the release name is `phpmyadmin`):
 
 ```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)
-$ kubectl delete deployments.apps phpmyadmin
-$ helm upgrade phpmyadmin my-repo/phpmyadmin --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD,mariadb.auth.password=$MARIADB_PASSWORD
+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)
+kubectl delete deployments.apps phpmyadmin
+helm upgrade phpmyadmin my-repo/phpmyadmin --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD,mariadb.auth.password=$MARIADB_PASSWORD
 ```
 
 ### To 7.0.0
@@ -441,30 +432,30 @@ In this major there were two main changes introduced:
 
 Please read the update notes carefully.
 
-**1. Adaptation to Helm v2 EOL**
+#### 1. Adaptation to Helm v2 EOL
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+##### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+##### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+##### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
-**2. Updated MariaDB dependency version**
+#### 2. Updated MariaDB dependency version
 
 In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-800) for more information.
 
@@ -475,26 +466,26 @@ 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:
 
 ```console
-  $ kubectl delete deployments.apps phpmyadmin
+  kubectl delete deployments.apps phpmyadmin
 
-  $ kubectl delete statefulsets.apps phpmyadmin-mariadb-master
+  kubectl delete statefulsets.apps phpmyadmin-mariadb-master
 
-  $ kubectl delete statefulsets.apps phpmyadmin-mariadb-slave
+  kubectl delete statefulsets.apps phpmyadmin-mariadb-slave
 
 ```
 
 Now the upgrade works:
 
 ```console
-$ helm upgrade phpmyadmin my-repo/phpmyadmin --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set db.bundleTestDB=true
+helm upgrade phpmyadmin my-repo/phpmyadmin --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set db.bundleTestDB=true
 ```
 
 Finally, you should see the lines below in MariaDB container logs:
@@ -528,7 +519,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 `phpmyadmin`:
 
 ```console
-$ kubectl patch deployment phpmyadmin-phpmyadmin --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl patch deployment phpmyadmin-phpmyadmin --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
 ```
 
 ## Community supported solution
@@ -547,10 +538,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/pinniped/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/pinniped
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/pinniped
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ 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.
@@ -48,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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                              | Value               |
@@ -83,7 +82,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `image.pullPolicy`  | Pinniped image pull policy                                                                               | `IfNotPresent`      |
 | `image.pullSecrets` | Pinniped image pull secrets                                                                              | `[]`                |
 
-
 ### Concierge Parameters
 
 | Name                                                        | Description                                                                                                              | Value           |
@@ -156,7 +154,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `concierge.sidecars`                                        | Add additional sidecar containers to the Concierge pod(s)                                                                | `[]`            |
 | `concierge.initContainers`                                  | Add additional init containers to the Concierge pod(s)                                                                   | `[]`            |
 
-
 ### Concierge RBAC settings
 
 | Name                                                                         | Description                                                                   | Value  |
@@ -175,7 +172,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `concierge.serviceAccount.kubeCertAgentService.automountServiceAccountToken` | Auto mount token for the Concierge kube-cert-agent-service Service Account    | `true` |
 | `concierge.serviceAccount.kubeCertAgentService.annotations`                  | Annotations for the Concierge Service Account                                 | `{}`   |
 
-
 ### Concierge Traffic Exposure Parameters
 
 | Name                                         | Description                                                                          | Value       |
@@ -193,7 +189,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `concierge.service.sessionAffinity`          | Control where client requests go, to the same pod or round-robin                     | `None`      |
 | `concierge.service.sessionAffinityConfig`    | Additional settings for the sessionAffinity                                          | `{}`        |
 
-
 ### Supervisor Parameters
 
 | Name                                                         | Description                                                                                                              | Value           |
@@ -260,7 +255,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `supervisor.sidecars`                                        | Add additional sidecar containers to the Supervisor pod(s)                                                               | `[]`            |
 | `supervisor.initContainers`                                  | Add additional init containers to the Supervisor pod(s)                                                                  | `[]`            |
 
-
 ### Supervisor RBAC settings
 
 | Name                                                     | Description                                                       | Value  |
@@ -271,7 +265,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `supervisor.serviceAccount.automountServiceAccountToken` | Auto mount token for the Supervisor Deployment Service Account    | `true` |
 | `supervisor.serviceAccount.annotations`                  | Annotations for the Supervisor Service Account                    | `{}`   |
 
-
 ### Supervisor Traffic Exposure Parameters
 
 | Name                                                 | Description                                                                                                                      | Value                       |
@@ -316,8 +309,7 @@ The command removes all the Kubernetes components associated with the chart and
 | `supervisor.ingress.secrets`                         | Custom TLS certificates as secrets                                                                                               | `[]`                        |
 | `supervisor.ingress.extraRules`                      | Additional rules to be covered with this ingress record                                                                          | `[]`                        |
 
-
-See https://github.com/bitnami-labs/readme-generator-for-helm to create the table
+See <https://github.com/bitnami-labs/readme-generator-for-helm> to create the table
 
 The above parameters map to the env variables defined in [bitnami/pinniped](https://github.com/bitnami/containers/tree/main/bitnami/pinniped). For more information please refer to the [bitnami/pinniped](https://github.com/bitnami/containers/tree/main/bitnami/pinniped) image documentation.
 
@@ -334,7 +326,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)
@@ -398,10 +390,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/postgresql-ha/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/postgresql-ha
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/postgresql-ha
 ```
 
 ## Introduction
@@ -36,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/postgresql-ha
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/postgresql-ha
 ```
 
 ## Uninstalling the Chart
@@ -45,7 +45,7 @@ $ helm install my-release my-repo/postgresql-ha
 To uninstall/delete the `my-release` deployment:
 
 ```console
-$ helm delete --purge my-release
+helm delete --purge my-release
 ```
 
 Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manually delete the PVCs.
@@ -72,7 +72,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `global.pgpool.adminPassword`      | Pgpool Admin password (overrides `pgpool.adminPassword`)                                        | `""`  |
 | `global.pgpool.existingSecret`     | Pgpool existing secret                                                                          | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                         | Value           |
@@ -89,7 +88,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `diagnosticMode.command` | Command to override all containers in the deployment                                                | `[]`            |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                                   | `[]`            |
 
-
 ### PostgreSQL with Repmgr parameters
 
 | Name                                                         | Description                                                                                                                                                                                                   | Value                       |
@@ -317,7 +315,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `witness.initdbScriptsCM`                                    | ConfigMap with scripts to be run at first boot                                                                                                                                                                | `""`                        |
 | `witness.initdbScriptsSecret`                                | Secret with scripts to be run at first boot                                                                                                                                                                   | `""`                        |
 
-
 ### Pgpool parameters
 
 | Name                                                     | Description                                                                                                                              | Value                |
@@ -430,7 +427,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `pgpool.tls.certKeyFilename`                             | Certificate key filename                                                                                                                 | `""`                 |
 | `pgpool.tls.certCAFilename`                              | CA Certificate filename                                                                                                                  | `""`                 |
 
-
 ### LDAP parameters
 
 | Name                            | Description                                                  | Value        |
@@ -446,7 +442,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `ldap.tlsReqcert`               | LDAP TLS check on server certificates                        | `""`         |
 | `ldap.nssInitgroupsIgnoreusers` | LDAP ignored users                                           | `root,nslcd` |
 
-
 ### Other Parameters
 
 | Name                                          | Description                                                                                                                                 | Value   |
@@ -459,7 +454,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `serviceAccount.automountServiceAccountToken` | Allows auto mount of ServiceAccountToken on the serviceAccount created                                                                      | `true`  |
 | `psp.create`                                  | Whether to create a PodSecurityPolicy. WARNING: PodSecurityPolicy is deprecated in Kubernetes v1.21 or later, unavailable in v1.25 or later | `false` |
 
-
 ### Metrics parameters
 
 | Name                                         | Description                                                                                                                                             | Value                       |
@@ -516,13 +510,12 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `metrics.serviceMonitor.scrapeTimeout`       | Service monitor scrape timeout                                                                                                                          | `""`                        |
 | `metrics.serviceMonitor.annotations`         | Additional annotations for the ServiceMonitor                                                                                                           | `{}`                        |
 | `metrics.serviceMonitor.labels`              | Additional labels that can be used so ServiceMonitor will be discovered by Prometheus                                                                   | `{}`                        |
-| `metrics.serviceMonitor.selector`            | Defaults to what's used if you follow CoreOS Prometheus Install Instructions (https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus#tldr) | `{}`                        |
+| `metrics.serviceMonitor.selector`            | Defaults to what's used if you follow CoreOS Prometheus Install Instructions (<https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus#tldr>) | `{}`                        |
 | `metrics.serviceMonitor.relabelings`         | ServiceMonitor relabelings. Value is evaluated as a template                                                                                            | `[]`                        |
 | `metrics.serviceMonitor.metricRelabelings`   | ServiceMonitor metricRelabelings. Value is evaluated as a template                                                                                      | `[]`                        |
 | `metrics.serviceMonitor.honorLabels`         | Specify honorLabels parameter to add the scrape endpoint                                                                                                | `false`                     |
 | `metrics.serviceMonitor.jobLabel`            | The name of the label on the target service to use as the job name in prometheus.                                                                       | `""`                        |
 
-
 ### Volume permissions parameters
 
 | Name                                             | Description                                                                                                                       | Value                   |
@@ -538,7 +531,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `volumePermissions.resources.limits`             | The resources limits for the container                                                                                            | `{}`                    |
 | `volumePermissions.resources.requests`           | The requested resources for the container                                                                                         | `{}`                    |
 
-
 ### Persistence parameters
 
 | Name                        | Description                                                                             | Value                 |
@@ -553,7 +545,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `persistence.labels`        | Persistent Volume Claim labels                                                          | `{}`                  |
 | `persistence.selector`      | Selector to match an existing Persistent Volume (this value is evaluated as a template) | `{}`                  |
 
-
 ### Traffic Exposure parameters
 
 | Name                                                  | Description                                                                                   | Value        |
@@ -576,7 +567,6 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
 | `networkPolicy.egressRules.denyConnectionsToExternal` | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53) | `false`      |
 | `networkPolicy.egressRules.customRules`               | Custom network policy rule                                                                    | `{}`         |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -660,7 +650,7 @@ LDAP support can be enabled in the chart by specifying the `ldap.` parameters wh
 
 For example:
 
-```
+```text
 ldap.enabled="true"
 ldap.uri="ldap://my_ldap_server"
 ldap.base="dc=example\,dc=org"
@@ -700,13 +690,13 @@ The above parameters (`initdbScripts`, `initdbScriptsCM`, and `initdbScriptsSecr
 
 The allowed extensions are `.sh`, `.sql` and `.sql.gz` in the **postgresql** container while only `.sh` in the case of the **pgpool** one.
 
-+info: https://github.com/bitnami/containers/tree/main/bitnami/postgresql#initializing-a-new-instance and https://github.com/bitnami/containers/tree/main/bitnami/pgpool#initializing-with-custom-scripts
++info: <https://github.com/bitnami/containers/tree/main/bitnami/postgresql#initializing-a-new-instance> and <https://github.com/bitnami/containers/tree/main/bitnami/pgpool#initializing-with-custom-scripts>
 
 ### Use of global variables
 
 In more complex scenarios, we may have the following tree of dependencies
 
-```
+```text
                      +--------------+
                      |              |
         +------------+   Chart 1    +-----------+
@@ -726,7 +716,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:
 
-```
+```text
 postgresql.postgresqlPassword=testtest
 subchart1.postgresql.postgresqlPassword=testtest
 subchart2.postgresql.postgresqlPassword=testtest
@@ -737,7 +727,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:
 
-```
+```text
 global.postgresql.postgresqlPassword=testtest
 global.postgresql.postgresqlDatabase=db1
 ```
@@ -769,8 +759,7 @@ $ helm upgrade my-release my-repo/postgresql-ha \
     --set postgresql.repmgrPassword=[REPMGR_PASSWORD]
 ```
 
-> Note: you need to substitute the placeholders _[POSTGRES_PASSWORD]_, and _[REPMGR_PASSWORD]_ with the values obtained from instructions in the installation notes.
-
+> Note: you need to substitute the placeholders *[POSTGRES_PASSWORD]*, and *[REPMGR_PASSWORD]* with the values obtained from instructions in the installation notes.
 > Note: As general rule, it is always wise to do a backup before the upgrading procedures.
 
 ### To 10.0.0
@@ -791,7 +780,7 @@ This chart major version updates the PostgreSQL image's version to the latest ma
 
 > Note: Keep in mind you will find an error such as the one below when upgrading since the new chart major version also bumps the application version. To workaround this issue you need to upgrade the database, please refer to the [official PostgreSQL documentation](https://www.postgresql.org/docs/current/upgrading.html) for more information about this.
 
-```
+```log
 postgresql-repmgr 14:41:21.00 INFO  ==> Setting up streaming replication slave...
 postgresql-repmgr 14:41:21.04 INFO  ==> Starting PostgreSQL in background...
 waiting for server to start....2022-04-12 14:41:21.069 GMT [220] FATAL:  database files are incompatible with server
@@ -822,7 +811,7 @@ $ helm upgrade my-release --version 8.0.0 my-repo/postgresql-ha \
     --set postgresql.replicaCount=[NUMBER_OF_REPLICAS]
 ```
 
-> Note: you need to substitute the placeholders _[POSTGRESQL_PASSWORD]_, and _[REPMGR_PASSWORD]_ with the values obtained from instructions in the installation notes.
+> Note: you need to substitute the placeholders *[POSTGRESQL_PASSWORD]*, and *[REPMGR_PASSWORD]* with the values obtained from instructions in the installation notes.
 
 ### To 6.4.0
 
@@ -833,24 +822,24 @@ As an alternative to this feature, users can still use the equivalent parameters
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 5.2.0
 
@@ -875,7 +864,7 @@ $ helm upgrade my-release --version 5.2.0 my-repo/postgresql-ha \
     --set postgresql.replicaCount=[NUMBER_OF_REPLICAS]
 ```
 
-> Note: you need to substitute the placeholders _[POSTGRESQL_PASSWORD]_, and _[REPMGR_PASSWORD]_ with the values obtained from instructions in the installation notes (`helm get notes RELEASE_NAME`).
+> Note: you need to substitute the placeholders *[POSTGRESQL_PASSWORD]*, and *[REPMGR_PASSWORD]* with the values obtained from instructions in the installation notes (`helm get notes RELEASE_NAME`).
 
 ### To 5.0.0
 
@@ -929,7 +918,7 @@ $ helm upgrade my-release --version 3.0.0 my-repo/postgresql-ha \
     --set postgresql.replicaCount=[NUMBER_OF_REPLICAS]
 ```
 
-> Note: you need to substitute the placeholders _[POSTGRESQL_PASSWORD]_, and _[REPMGR_PASSWORD]_ with the values obtained from instructions in the installation notes.
+> Note: you need to substitute the placeholders *[POSTGRESQL_PASSWORD]*, and *[REPMGR_PASSWORD]* with the values obtained from instructions in the installation notes.
 
 ### To 2.0.0
 
@@ -963,7 +952,7 @@ $ helm upgrade my-release --version 1.0.0 my-repo/postgresql-ha \
     --set postgresql.replicaCount=[NUMBER_OF_REPLICAS]
 ```
 
-> Note: you need to substitute the placeholders _[POSTGRESQL_PASSWORD]_, and _[REPMGR_PASSWORD]_ with the values obtained from instructions in the installation notes.
+> Note: you need to substitute the placeholders *[POSTGRESQL_PASSWORD]*, and *[REPMGR_PASSWORD]* with the values obtained from instructions in the installation notes.
 
 ### To 0.4.0
 
@@ -994,10 +983,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/postgresql/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/postgresql
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/postgresql
 ```
 
 ## 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/postgresql
+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.
@@ -47,7 +47,7 @@ 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.
@@ -55,7 +55,7 @@ The command removes all the Kubernetes components but PVC's associated with the
 To delete the PVC's associated with `my-release`:
 
 ```console
-$ kubectl delete pvc -l release=my-release
+kubectl delete pvc -l release=my-release
 ```
 
 > **Note**: Deleting the PVC's will delete postgresql data as well. Please be cautious before doing it.
@@ -79,7 +79,6 @@ $ kubectl delete pvc -l release=my-release
 | `global.postgresql.auth.secretKeys.replicationPasswordKey` | Name of key in existing secret to use for PostgreSQL credentials (overrides `auth.secretKeys.replicationPasswordKey`). Only used when `global.postgresql.auth.existingSecret` is set. | `""`  |
 | `global.postgresql.service.ports.postgresql`               | PostgreSQL service port (overrides `service.ports.postgresql`)                                                                                                                        | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                  | Value           |
@@ -95,7 +94,6 @@ $ kubectl delete pvc -l release=my-release
 | `diagnosticMode.command` | Command to override all containers in the statefulset                                        | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the statefulset                                           | `["infinity"]`  |
 
-
 ### PostgreSQL common parameters
 
 | Name                                     | Description                                                                                                                                                                                                                                                                                                                                   | Value                      |
@@ -158,7 +156,6 @@ $ kubectl delete pvc -l release=my-release
 | `tls.certCAFilename`                     | CA Certificate filename                                                                                                                                                                                                                                                                                                                       | `""`                       |
 | `tls.crlFilename`                        | File containing a Certificate Revocation List                                                                                                                                                                                                                                                                                                 | `""`                       |
 
-
 ### PostgreSQL Primary parameters
 
 | Name                                         | Description                                                                                                              | Value                 |
@@ -263,7 +260,6 @@ $ kubectl delete pvc -l release=my-release
 | `primary.persistence.selector`               | Selector to match an existing Persistent Volume (this value is evaluated as a template)                                  | `{}`                  |
 | `primary.persistence.dataSource`             | Custom PVC data source                                                                                                   | `{}`                  |
 
-
 ### PostgreSQL read only replica parameters (only used when `architecture` is set to `replication`)
 
 | Name                                              | Description                                                                                                              | Value                 |
@@ -355,7 +351,6 @@ $ kubectl delete pvc -l release=my-release
 | `readReplicas.persistence.selector`               | Selector to match an existing Persistent Volume (this value is evaluated as a template)                                  | `{}`                  |
 | `readReplicas.persistence.dataSource`             | Custom PVC data source                                                                                                   | `{}`                  |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                                      | Description                                                                                                                                        | Value   |
@@ -375,7 +370,6 @@ $ kubectl delete pvc -l release=my-release
 | `networkPolicy.egressRules.denyConnectionsToExternal`                     | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                                                     | `false` |
 | `networkPolicy.egressRules.customRules`                                   | Custom network policy rule                                                                                                                         | `{}`    |
 
-
 ### Volume Permissions parameters
 
 | Name                                                   | Description                                                                                                                       | Value                   |
@@ -391,7 +385,6 @@ $ kubectl delete pvc -l release=my-release
 | `volumePermissions.resources.requests`                 | Init container volume-permissions resource requests                                                                               | `{}`                    |
 | `volumePermissions.containerSecurityContext.runAsUser` | User ID for the init container                                                                                                    | `0`                     |
 
-
 ### Other Parameters
 
 | Name                                          | Description                                                                                                                                 | Value   |
@@ -404,7 +397,6 @@ $ kubectl delete pvc -l release=my-release
 | `rbac.rules`                                  | Custom RBAC rules to set                                                                                                                    | `[]`    |
 | `psp.create`                                  | Whether to create a PodSecurityPolicy. WARNING: PodSecurityPolicy is deprecated in Kubernetes v1.21 or later, unavailable in v1.25 or later | `false` |
 
-
 ### Metrics Parameters
 
 | Name                                            | Description                                                                                                | Value                       |
@@ -464,7 +456,6 @@ $ kubectl delete pvc -l release=my-release
 | `metrics.prometheusRule.labels`                 | Additional labels that can be used so PrometheusRule will be discovered by Prometheus                      | `{}`                        |
 | `metrics.prometheusRule.rules`                  | PrometheusRule definitions                                                                                 | `[]`                        |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -476,13 +467,12 @@ $ helm install my-release \
 The above command sets the PostgreSQL `postgres` account password to `secretpassword`.
 
 > NOTE: Once this chart is deployed, it is not possible to change the application's access credentials, such as usernames or passwords, using Helm. To change these application credentials after deployment, delete any persistent volumes (PVs) used by the chart and re-deploy it, or use the application's built-in administrative tools if available.
-
 > **Warning** Setting a password will be ignored on new installation in case when previous Posgresql release was deleted through the helm command. In that case, old PVC will have an old password, and setting it through helm won't take effect. Deleting persistent volumes (PVs) will solve the issue. Refer to [issue 2061](https://github.com/bitnami/charts/issues/2061) for more details
 
 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/postgresql
+helm install my-release -f values.yaml my-repo/postgresql
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -583,7 +573,7 @@ The exporter allows to create custom metrics from additional SQL queries. See th
 
 In more complex scenarios, we may have the following tree of dependencies
 
-```
+```text
                      +--------------+
                      |              |
         +------------+   Chart 1    +-----------+
@@ -603,7 +593,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 as well. In order to do so, subcharts 1 and 2 need to know the PostgreSQL credentials, so one option for deploying could be deploy Chart 1 with the following parameters:
 
-```
+```text
 postgresql.auth.username=testuser
 subchart1.postgresql.auth.username=testuser
 subchart2.postgresql.auth.username=testuser
@@ -617,7 +607,7 @@ subchart2.postgresql.auth.database=testdb
 
 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:
 
-```
+```text
 global.postgresql.auth.username=testuser
 global.postgresql.auth.password=testpass
 global.postgresql.auth.database=testdb
@@ -641,7 +631,7 @@ 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:
 
 ```console
-$ kubectl annotate namespace default "net.beta.kubernetes.io/network-policy={\"ingress\":{\"isolation\":\"DefaultDeny\"}}"
+kubectl annotate namespace default "net.beta.kubernetes.io/network-policy={\"ingress\":{\"isolation\":\"DefaultDeny\"}}"
 ```
 
 With NetworkPolicy enabled, traffic will be limited to just port 5432.
@@ -685,10 +675,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/prestashop/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/prestashop
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/prestashop
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/prestashop
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/prestashop
 ```
 
 The command deploys PrestaShop on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys PrestaShop 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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                                    | Value |
@@ -76,7 +75,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `commonLabels`      | Common labels to add to all PrestaShop resources (sub-charts are not considered). Evaluated as a template      | `{}`  |
 | `extraDeploy`       | Array with extra yaml to deploy with the chart. Evaluated as a template                                        | `[]`  |
 
-
 ### PrestaShop parameters
 
 | Name                                    | Description                                                                                                | Value                 |
@@ -173,7 +171,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `podAnnotations`                        | Pod annotations                                                                                            | `{}`                  |
 | `podLabels`                             | Pod extra labels                                                                                           | `{}`                  |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -205,7 +202,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.secrets`                  | If you're providing your own certificates, please use this to add the certificates as secrets                                    | `[]`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Database parameters
 
 | Name                                        | Description                                                                              | Value                |
@@ -229,7 +225,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.database`                 | Name of the existing database                                                            | `bitnami_prestashop` |
 | `externalDatabase.existingSecret`           | Name of an existing secret resource containing the DB password                           | `""`                 |
 
-
 ### Volume Permissions parameters
 
 | Name                                   | Description                                                                                                                                               | Value                   |
@@ -244,7 +239,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.limits`   | The resources limits for the container                                                                                                                    | `{}`                    |
 | `volumePermissions.resources.requests` | The requested resources for the container                                                                                                                 | `{}`                    |
 
-
 ### Metrics parameters
 
 | Name                         | Description                                                                                                     | Value                     |
@@ -260,7 +254,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.resources.limits`   | The resources limits for the container for the metrics exporter container                                       | `{}`                      |
 | `metrics.podAnnotations`     | Metrics exporter pod annotations                                                                                | `{}`                      |
 
-
 ### Certificate injection parameters
 
 | Name                                                 | Description                                                                                                       | Value                                    |
@@ -284,7 +277,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `certificates.image.pullPolicy`                      | Container sidecar image pull policy                                                                               | `IfNotPresent`                           |
 | `certificates.image.pullSecrets`                     | Container sidecar image pull secrets                                                                              | `[]`                                     |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                          | Description                                                                                                                    | Value   |
@@ -305,7 +297,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.denyConnectionsToExternal`         | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                                 | `false` |
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                                     | `{}`    |
 
-
 The above parameters map to the env variables defined in [bitnami/prestashop](https://github.com/bitnami/containers/tree/main/bitnami/prestashop). For more information please refer to the [bitnami/prestashop](https://github.com/bitnami/containers/tree/main/bitnami/prestashop) image documentation.
 
 > **Note**:
@@ -337,7 +328,7 @@ The above command sets the PrestaShop 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/prestashop
+helm install my-release -f values.yaml my-repo/prestashop
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -388,7 +379,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
 1. Install the chart
 
 ```console
-$ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/prestashop
+helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/prestashop
 ```
 
 ### Host path
@@ -404,15 +395,13 @@ $ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/prest
 1. Install the chart
 
    ```console
-   $ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/prestashop
+   helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/prestashop
    ```
 
    This will mount the `prestashop-data` volume into the `hostPath` directory. The site data will be persisted if the mount path contains valid data, else the site data will be initialized at first launch.
 
 1. Because the container cannot control the host machine's directory permissions, you must set the PrestaShop file directory permissions yourself and disable or clear PrestaShop cache.
 
-## Troubleshooting
-
 ### SSL
 
 One needs to explicitly turn on SSL in the Prestashop administration panel, else a `302` redirect to `http` scheme is returned on any page of the site by default.
@@ -455,24 +444,24 @@ This version standardizes the way of defining Ingress rules. When configuring a
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the _requirements.yaml_ to the _Chart.yaml_
 - After running `helm dependency update`, a _Chart.lock_ file is generated containing the same structure used in the previous _requirements.lock_
 - The different fields present in the _Chart.yaml_ file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 11.0.0
 
@@ -486,22 +475,22 @@ 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:
 
 ```console
-$ helm upgrade prestashop my-repo/prestashop --set prestashopPassword=$PRESTASHOP_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 10.0.0
+helm upgrade prestashop my-repo/prestashop --set prestashopPassword=$PRESTASHOP_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 10.0.0
 ```
 
 Finally, upgrade you release to 11.0.0 reusing the existing PVC, and enabling back MariaDB:
 
 ```console
-$ helm upgrade prestashop my-repo/prestashop --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set prestashopPassword=$PRESTASHOP_PASSWORD
+helm upgrade prestashop my-repo/prestashop --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set prestashopPassword=$PRESTASHOP_PASSWORD
 ```
 
 You should see the lines below in MariaDB container logs:
@@ -526,7 +515,7 @@ This upgrade also adapts the chart to the latest Bitnami good practices. Check t
 
 Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
 
-In https://github.com/helm/charts/pull/17308 the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
+In <https://github.com/helm/charts/pull/17308> the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
 
 This major version signifies this change.
 
@@ -536,8 +525,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 prestashop:
 
 ```console
-$ kubectl patch deployment prestashop-prestashop --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl delete statefulset prestashop-mariadb --cascade=false
+kubectl patch deployment prestashop-prestashop --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl delete statefulset prestashop-mariadb --cascade=false
 ```
 
 ## Community supported solution
@@ -556,10 +545,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/pytorch/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/pytorch
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/pytorch
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/pytorch
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/pytorch
 ```
 
 These commands deploy PyTorch on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured.
@@ -48,7 +48,7 @@ These commands deploy PyTorch 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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                  | Value          |
@@ -78,7 +77,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                         | `["sleep"]`    |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                            | `["infinity"]` |
 
-
 ### PyTorch parameters
 
 | Name                                              | Description                                                                                                              | Value                  |
@@ -157,7 +155,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `sidecars`                                        | Add additional sidecar containers to the Pytorch pod(s)                                                                  | `[]`                   |
 | `initContainers`                                  | Add additional init containers to the %%MAIN_CONTAINER_NAME%% pod(s)                                                     | `[]`                   |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                        | Value       |
@@ -174,7 +171,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `service.sessionAffinity`          | Control where client requests go, to the same pod or round-robin                   | `None`      |
 | `service.sessionAffinityConfig`    | Additional settings for the sessionAffinity                                        | `{}`        |
 
-
 ### Init Container Parameters
 
 | Name                                   | Description                                                                                                                                               | Value                   |
@@ -195,7 +191,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.limits`   | The resources limits for the container                                                                                                                    | `{}`                    |
 | `volumePermissions.resources.requests` | The requested resources for the container                                                                                                                 | `{}`                    |
 
-
 ### Persistence Parameters
 
 | Name                        | Description                                                                                             | Value               |
@@ -211,7 +206,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `persistence.selector`      | Selector to match an existing Persistent Volume for WordPress data PVC                                  | `{}`                |
 | `persistence.dataSource`    | Custom PVC data source                                                                                  | `{}`                |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -226,7 +220,7 @@ The above command create 4 pods for PyTorch: one master and three workers.
 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/pytorch
+helm install my-release -f values.yaml my-repo/pytorch
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -296,22 +290,22 @@ This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ## License
 
@@ -321,10 +315,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/rabbitmq-cluster-operator/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/rabbitmq-cluster-operator
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/rabbitmq-cluster-operator
 ```
 
 ## 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/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.
@@ -47,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.
@@ -58,7 +58,7 @@ In the Bitnami catalog we offer both the *bitnami/rabbitmq* and *bitnami/rabbitm
 
 The *bitnami/rabbitmq* chart deploys a single RabbitMQ installation using a Kubernetes StatefulSet object (together with Services, PVCs, ConfigMaps, etc.). The figure below shows the deployed objects in the cluster after executing *helm install*:
 
-```
+```text
                     +--------------+             +-----+
                     |              |             |     |
  Service            |   RabbitMQ   +<------------+ PVC |
@@ -78,7 +78,7 @@ Its lifecycle is managed using Helm and, at the RabbitMQ container level, the fo
 
 The *bitnami/rabbitmq-operator* chart deploys a RabbitMQ Operator installation using a Kubernetes Deployment.  The figure below shows the RabbitMQ operator deployment after executing *helm install*:
 
-```
+```text
 +--------------------+
 |                    |      +---------------+
 |  RabbitMQ Operator |      |               |
@@ -93,7 +93,7 @@ The *bitnami/rabbitmq-operator* chart deploys a RabbitMQ Operator installation u
 
 The operator will extend the Kubernetes API with the following object: *RabbitmqCluster*. From that moment, the user will be able to deploy objects of these kinds and the previously deployed Operator will take care of deploying all the required StatefulSets, ConfigMaps and Services for running a RabbitMQ instance. Its lifecycle is managed using *kubectl* on the RabbitmqCluster objects. The following figure shows the deployed objects after deploying a *RabbitmqCluster* object using *kubectl*:
 
-```
+```text
   +--------------------+
   |                    |      +---------------+
   |  RabbitMQ Operator |      |               |
@@ -140,7 +140,6 @@ This solution allows to easily deploy multiple RabbitMQ instances compared to th
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                          | Value           |
@@ -154,7 +153,6 @@ This solution allows to easily deploy multiple RabbitMQ instances compared to th
 | `extraDeploy`            | Array of extra objects to deploy with the release    | `[]`            |
 | `diagnosticMode.enabled` | Enable diagnostic mode (all probes will be disabled) | `false`         |
 
-
 ### RabbitMQ Cluster Operator Parameters
 
 | Name                                                              | Description                                                                                                                              | Value                                    |
@@ -238,7 +236,6 @@ This solution allows to easily deploy multiple RabbitMQ instances compared to th
 | `clusterOperator.serviceAccount.annotations`                      | Add annotations                                                                                                                          | `{}`                                     |
 | `clusterOperator.serviceAccount.automountServiceAccountToken`     | Automount API credentials for a service account.                                                                                         | `true`                                   |
 
-
 ### RabbitMQ Cluster Operator Metrics parameters
 
 | Name                                                       | Description                                                                 | Value                    |
@@ -266,7 +263,6 @@ This solution allows to easily deploy multiple RabbitMQ instances compared to th
 | `clusterOperator.metrics.serviceMonitor.relabelings`       | Specify general relabeling                                                  | `[]`                     |
 | `clusterOperator.metrics.serviceMonitor.labels`            | Extra labels for the ServiceMonitor                                         | `{}`                     |
 
-
 ### RabbitMQ Messaging Topology Operator Parameters
 
 | Name                                                                  | Description                                                                                                                          | Value                                     |
@@ -356,7 +352,6 @@ This solution allows to easily deploy multiple RabbitMQ instances compared to th
 | `msgTopologyOperator.serviceAccount.annotations`                      | Add annotations                                                                                                                      | `{}`                                      |
 | `msgTopologyOperator.serviceAccount.automountServiceAccountToken`     | Automount API credentials for a service account.                                                                                     | `true`                                    |
 
-
 ### RabbitMQ Messaging Topology Operator parameters
 
 | Name                                                           | Description                                                                 | Value                    |
@@ -384,15 +379,12 @@ This solution allows to easily deploy multiple RabbitMQ instances compared to th
 | `msgTopologyOperator.metrics.serviceMonitor.relabelings`       | Specify general relabeling                                                  | `[]`                     |
 | `msgTopologyOperator.metrics.serviceMonitor.labels`            | Extra labels for the ServiceMonitor                                         | `{}`                     |
 
-
 ### cert-manager parameters
 
 | Name             | Description                                                       | Value   |
 | ---------------- | ----------------------------------------------------------------- | ------- |
 | `useCertManager` | Deploy cert-manager objects (Issuer and Certificate) for webhooks | `false` |
 
-
-
 The above parameters map to the env variables defined in [bitnami/rabbitmq-cluster-operator](https://github.com/bitnami/containers/tree/main/bitnami/rabbitmq-cluster-operator). For more information please refer to the [bitnami/rabbitmq-cluster-operator](https://github.com/bitnami/containers/tree/main/bitnami/rabbitmq-cluster-operator) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -408,7 +400,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)
@@ -443,6 +435,7 @@ If additional containers are needed in the same pod as rabbitmq-cluster-operator
 This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
 
 As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
+
 ### Deploying extra resources
 
 There are cases where you may want to deploy extra objects, such your custom *RabbitmqCluster* objects. For covering this case, the chart allows adding the full specification of other objects using the `extraDeploy` parameter.
@@ -479,18 +472,18 @@ 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
 
 This new version adds the following components:
 
-  - RabbitMQ Messaging Topology Operator: all the settings are inside the `msgTopologyOperator` section.
-  - RabbitMQ Default User Credential Updater sidecar: this enables Hashicorp Vault integration for all `RabbitMQCluster` instances.
-  - `cert-manager` subchart: this is necessary for the RabbitMQ Messaging Topology Webhooks to work.
+- RabbitMQ Messaging Topology Operator: all the settings are inside the `msgTopologyOperator` section.
+- RabbitMQ Default User Credential Updater sidecar: this enables Hashicorp Vault integration for all `RabbitMQCluster` instances.
+- `cert-manager` subchart: this is necessary for the RabbitMQ Messaging Topology Webhooks to work.
 
 As a breaking change, all `rabbitmq-cluster-operator` deployment values were moved to the `clusterOperator` section.
 
@@ -503,8 +496,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
@@ -515,10 +508,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/rabbitmq/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/rabbitmq
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/rabbitmq
 ```
 
 ## 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/rabbitmq
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/rabbitmq
 ```
 
 The command deploys RabbitMQ on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -45,7 +45,7 @@ The command deploys RabbitMQ 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.
@@ -60,7 +60,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### RabbitMQ Image parameters
 
 | Name                | Description                                                                                              | Value                 |
@@ -73,7 +72,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `image.pullSecrets` | Specify docker-registry secret names as an array                                                         | `[]`                  |
 | `image.debug`       | Set to true if you would like to see extra information on logs                                           | `false`               |
 
-
 ### Common parameters
 
 | Name                                         | Description                                                                                                                                                             | Value                                             |
@@ -186,7 +184,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraSecrets`                               | Optionally specify extra secrets to be created by the chart.                                                                                                            | `{}`                                              |
 | `extraSecretsPrependReleaseName`             | Set this flag to true if extraSecrets should be created with <release-name> prepended.                                                                                  | `false`                                           |
 
-
 ### Statefulset parameters
 
 | Name                                    | Description                                                                                                              | Value           |
@@ -242,7 +239,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `pdb.minAvailable`                      | Minimum number/percentage of pods that should remain scheduled                                                           | `1`             |
 | `pdb.maxUnavailable`                    | Maximum number/percentage of pods that may be made unavailable                                                           | `""`            |
 
-
 ### RBAC parameters
 
 | Name                                          | Description                                                                                | Value  |
@@ -253,7 +249,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.annotations`                  | Annotations for service account. Evaluated as a template. Only used if `create` is `true`. | `{}`   |
 | `rbac.create`                                 | Whether RBAC rules should be created                                                       | `true` |
 
-
 ### Persistence parameters
 
 | Name                        | Description                                      | Value                      |
@@ -268,7 +263,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `persistence.size`          | PVC Storage Request for RabbitMQ data volume     | `8Gi`                      |
 | `persistence.annotations`   | Persistence annotations. Evaluated as a template | `{}`                       |
 
-
 ### Exposure parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -325,7 +319,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.allowExternal`      | Don't require client label for connections                                                                                       | `true`                   |
 | `networkPolicy.additionalRules`    | Additional NetworkPolicy Ingress "from" rules to set. Note that all rules are OR-ed.                                             | `[]`                     |
 
-
 ### Metrics Parameters
 
 | Name                                       | Description                                                                            | Value                 |
@@ -352,7 +345,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRule.namespace`         | namespace where prometheusRules resource should be created                             | `""`                  |
 | `metrics.prometheusRule.rules`             | List of rules, used as template by Helm.                                               | `[]`                  |
 
-
 ### Init Container Parameters
 
 | Name                                                   | Description                                                                                                                       | Value                   |
@@ -368,7 +360,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.requests`                 | Init container volume-permissions resource requests                                                                               | `{}`                    |
 | `volumePermissions.containerSecurityContext.runAsUser` | User ID for the init container                                                                                                    | `0`                     |
 
-
 The above parameters map to the env variables defined in [bitnami/rabbitmq](https://github.com/bitnami/containers/tree/main/bitnami/rabbitmq). For more information please refer to the [bitnami/rabbitmq](https://github.com/bitnami/containers/tree/main/bitnami/rabbitmq) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -386,7 +377,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/rabbitmq
+helm install my-release -f values.yaml my-repo/rabbitmq
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -424,8 +415,8 @@ To enable TLS support, first generate the certificates as described in the [Rabb
 
 Once the certificates are generated, you have two alternatives:
 
-* Create a secret with the certificates and associate the secret when deploying the chart
-* Include the certificates in the *values.yaml* file when deploying the chart
+- Create a secret with the certificates and associate the secret when deploying the chart
+- Include the certificates in the *values.yaml* file when deploying the chart
 
 Set the *auth.tls.failIfNoPeerCert* parameter to *false* to allow a TLS connection if the client fails to provide a certificate.
 
@@ -455,17 +446,17 @@ LDAP support can be enabled in the chart by specifying the `ldap.*` parameters w
 
 It is possible to configure a memory high watermark on RabbitMQ to define [memory thresholds](https://www.rabbitmq.com/memory.html#threshold) using the `memoryHighWatermark.*` parameters. To do so, you have two alternatives:
 
-* Set an absolute limit of RAM to be used on each RabbitMQ node, as shown in the configuration example below:
+- Set an absolute limit of RAM to be used on each RabbitMQ node, as shown in the configuration example below:
 
-```
+```text
 memoryHighWatermark.enabled="true"
 memoryHighWatermark.type="absolute"
 memoryHighWatermark.value="512MB"
 ```
 
-* Set a relative limit of RAM to be used on each RabbitMQ node. To enable this feature,  define the memory limits at pod level too. An example configuration is shown below:
+- Set a relative limit of RAM to be used on each RabbitMQ node. To enable this feature,  define the memory limits at pod level too. An example configuration is shown below:
 
-```
+```text
 memoryHighWatermark.enabled="true"
 memoryHighWatermark.type="relative"
 memoryHighWatermark.value="0.4"
@@ -557,7 +548,7 @@ The chart mounts a [Persistent Volume](https://kubernetes.io/docs/concepts/stora
 1. Install the chart
 
 ```console
-$ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/rabbitmq
+helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/rabbitmq
 ```
 
 ### Adjust permissions of the persistence volume mountpoint
@@ -592,7 +583,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:
 
 ```console
-$ helm upgrade my-release my-repo/rabbitmq --set auth.password=[PASSWORD] --set auth.erlangCookie=[RABBITMQ_ERLANG_COOKIE]
+helm upgrade my-release my-repo/rabbitmq --set auth.password=[PASSWORD] --set auth.erlangCookie=[RABBITMQ_ERLANG_COOKIE]
 ```
 
 | Note: you need to substitute the placeholders [PASSWORD] and [RABBITMQ_ERLANG_COOKIE] with the values obtained in the installation notes.
@@ -704,7 +695,7 @@ 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 rabbitmq:
 
 ```console
-$ kubectl delete statefulset rabbitmq --cascade=false
+kubectl delete statefulset rabbitmq --cascade=false
 ```
 
 ## Bitnami Kubernetes Documentation
@@ -725,10 +716,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/redis-cluster/README.md

@@ -11,8 +11,8 @@ Disclaimer: Redis is a registered trademark of Redis Ltd. Any rights therein are
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/redis-cluster
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/redis-cluster
 ```
 
 ## Introduction
@@ -44,16 +44,16 @@ The main features of each chart are the following:
 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/redis-cluster
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/redis-cluster
 ```
 
 The command deploys Redis® on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
 
 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
+```console
+helm install --timeout 600s myrelease my-repo/redis-cluster
 ```
 
 > **Tip**: List all releases using `helm list`
@@ -63,7 +63,7 @@ $ helm install --timeout 600s myrelease my-repo/redis-cluster
 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.
@@ -79,7 +79,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 | `global.redis.password`   | Redis® password (overrides `password`)      | `""`  |
 
-
 ### Redis® Cluster Common parameters
 
 | Name                                                    | Description                                                                                                                                         | Value                   |
@@ -169,7 +168,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.requests`                  | The requested resources for the container                                                                                                           | `{}`                    |
 | `podSecurityPolicy.create`                              | Whether to create a PodSecurityPolicy. WARNING: PodSecurityPolicy is deprecated in Kubernetes v1.21 or later, unavailable in v1.25 or later         | `false`                 |
 
-
 ### Redis® statefulset parameters
 
 | Name                                           | Description                                                                                                | Value           |
@@ -233,7 +231,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `redis.tolerations`                            | Tolerations for Redis® pods assignment                                                                 | `[]`            |
 | `redis.topologySpreadConstraints`              | Pod topology spread constraints for Redis® pod                                                         | `[]`            |
 
-
 ### Cluster update job parameters
 
 | Name                                  | Description                                                                                                    | Value  |
@@ -263,7 +260,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `updateJob.resources.limits`          | The resources limits for the container                                                                         | `{}`   |
 | `updateJob.resources.requests`        | The requested resources for the container                                                                      | `{}`   |
 
-
 ### Cluster management parameters
 
 | Name                                                      | Description                                                                                   | Value          |
@@ -282,7 +278,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `cluster.update.currentNumberOfReplicas`                  | Number of currently deployed Redis® replicas                                              | `1`            |
 | `cluster.update.newExternalIPs`                           | External IPs obtained from the services for the new nodes to add to the cluster               | `[]`           |
 
-
 ### Metrics sidecar parameters
 
 | Name                                                        | Description                                                                                                                        | Value                    |
@@ -321,7 +316,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.service.labels`                                    | Additional labels for the metrics service                                                                                          | `{}`                     |
 | `metrics.service.clusterIP`                                 | Service Cluster IP                                                                                                                 | `""`                     |
 
-
 ### Sysctl Image parameters
 
 | Name                                              | Description                                                                                                          | Value                   |
@@ -341,7 +335,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `sysctlImage.resources.limits`                    | The resources limits for the container                                                                               | `{}`                    |
 | `sysctlImage.resources.requests`                  | The requested resources for the container                                                                            | `{}`                    |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -357,11 +350,10 @@ The above command sets the Redis® server password to `secretpassword`.
 Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/redis-cluster
+helm install my-release -f values.yaml my-repo/redis-cluster
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
-
 > **Note for minikube users**: Current versions of minikube (v0.24.1 at the time of writing) provision `hostPath` persistent volumes that are only writable by root. Using chart defaults cause pod failure for the Redis® pod as it attempts to write to the `/bitnami` directory. See minikube issue [1990](https://github.com/kubernetes/minikube/issues/1990) for more information.
 
 ## Configuration and installation details
@@ -406,8 +398,8 @@ 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
+```console
+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,8 +409,8 @@ 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
+```console
+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,8 +420,8 @@ As we want to add a new node, we are setting `cluster.nodes=7` and we leave empt
 At this point, you will have a new Redis&reg; Pod that will remain in `crashLoopBackOff` state until we provide the LoadBalancerIP for the new service.
 Now, wait until the cluster provides the new LoadBalancerIP for the new service and perform the second upgrade:
 
-```
-$ 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
+```console
+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,8 +434,8 @@ 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" .
+```console
+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.
@@ -452,7 +444,7 @@ The cluster will continue working during the update as long as the quorum is not
 
 Once all the nodes are ready, get the list of nodes in the cluster using the `CLUSTER NODES` command. You will see references to the ones that were removed. Write down the node IDs of the nodes that show `fail`. In the following example the cluster scaled down from 7 to 6 nodes.
 
-```
+```console
 redis-cli -a $REDIS_PASSWORD CLUSTER NODES
 
 ...
@@ -462,24 +454,25 @@ b23bcffa1fd64368d445c1d9bd9aeb92641105f7 10.0.0.70:6379@16379 slave,fail - 16456
 
 In each cluster node, execute the following command. Replace the NODE_ID placeholder.
 
-```
+```console
 redis-cli -a $REDIS_PASSWORD CLUSTER FORGET NODE_ID
 ```
 
 In the previous example the commands would look like this in each cluster node:
 
-```
+```console
 redis-cli -a $REDIS_PASSWORD CLUSTER FORGET b23bcffa1fd64368d445c1d9bd9aeb92641105f7
 ```
 
 ### Using password file
+
 To use a password file for Redis&reg; you need to create a secret containing the password.
 
 > *NOTE*: It is important that the file with the password must be called `redis-password`
 
 And then deploy the Helm Chart using the secret name as parameter:
 
-```console
+```text
 usePassword=true
 usePasswordFile=true
 existingSecret=redis-password-secret
@@ -501,7 +494,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:
@@ -557,9 +550,11 @@ Alternatively, you can use a ConfigMap or a Secret with the environment variable
 The chart optionally can start a metrics exporter for [prometheus](https://prometheus.io). The metrics endpoint (port 9121) is exposed in the service. Metrics can be scraped from within the cluster using something similar as the described in the [example Prometheus scrape configuration](https://github.com/prometheus/prometheus/blob/master/documentation/examples/prometheus-kubernetes.yml). If metrics are to be scraped from outside the cluster, the Kubernetes API proxy can be utilized to access the endpoint.
 
 ### Host Kernel Settings
+
 Redis&reg; may require some changes in the kernel of the host machine to work as expected, in particular increasing the `somaxconn` value and disabling transparent huge pages.
 To do so, you can set up a privileged initContainer with the `sysctlImage` config values, for example:
-```
+
+```yaml
 sysctlImage:
   enabled: true
   mountHostSys: true
@@ -597,9 +592,11 @@ To enable network policy for Redis&reg;, install
 and set `networkPolicy.enabled` to `true`.
 
 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:
+the DefaultDeny namespace annotation. Note: this will enforce policy for *all* pods in the namespace:
 
-    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, only pods with the generated client label will be
 able to connect to Redis&reg;. This label will be displayed in the output
@@ -635,8 +632,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
@@ -653,24 +650,24 @@ This major version updates the Redis&reg; docker image version used from `6.0` t
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 3.0.0
 
@@ -688,10 +685,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/redis/README.md

@@ -11,8 +11,8 @@ Disclaimer: Redis is a registered trademark of Redis Ltd. Any rights therein are
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/redis
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/redis
 ```
 
 ## Introduction
@@ -47,8 +47,8 @@ The main features of each chart are the following:
 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/redis
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/redis
 ```
 
 The command deploys Redis® on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -60,7 +60,7 @@ The command deploys Redis® 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.
@@ -76,7 +76,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)           | `""`  |
 | `global.redis.password`   | Global Redis® password (overrides `auth.password`) | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value           |
@@ -94,7 +93,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                    | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                       | `["infinity"]`  |
 
-
 ### Redis® Image parameters
 
 | Name                | Description                                                                                                | Value                |
@@ -107,7 +105,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `image.pullSecrets` | Redis® image pull secrets                                                                              | `[]`                 |
 | `image.debug`       | Enable image debug mode                                                                                    | `false`              |
 
-
 ### Redis® common configuration parameters
 
 | Name                             | Description                                                                           | Value         |
@@ -122,7 +119,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `commonConfiguration`            | Common configuration to be added into the ConfigMap                                   | `""`          |
 | `existingConfigmap`              | The name of an existing ConfigMap with your custom configuration for Redis® nodes | `""`          |
 
-
 ### Redis® master configuration parameters
 
 | Name                                                 | Description                                                                                           | Value                    |
@@ -222,7 +218,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `master.serviceAccount.automountServiceAccountToken` | Whether to auto mount the service account token                                                       | `true`                   |
 | `master.serviceAccount.annotations`                  | Additional custom annotations for the ServiceAccount                                                  | `{}`                     |
 
-
 ### Redis® replicas configuration parameters
 
 | Name                                                  | Description                                                                                             | Value                    |
@@ -329,7 +324,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `replica.serviceAccount.automountServiceAccountToken` | Whether to auto mount the service account token                                                         | `true`                   |
 | `replica.serviceAccount.annotations`                  | Additional custom annotations for the ServiceAccount                                                    | `{}`                     |
 
-
 ### Redis® Sentinel configuration parameters
 
 | Name                                          | Description                                                                                                                                 | Value                    |
@@ -413,7 +407,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `sentinel.service.sessionAffinityConfig`      | Additional settings for the sessionAffinity                                                                                                 | `{}`                     |
 | `sentinel.terminationGracePeriodSeconds`      | Integer setting the termination grace period for the redis-node pods                                                                        | `30`                     |
 
-
 ### Other Parameters
 
 | Name                                          | Description                                                                                                                                 | Value   |
@@ -445,7 +438,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `tls.certCAFilename`                          | CA Certificate filename                                                                                                                     | `""`    |
 | `tls.dhParamsFilename`                        | File containing DH params (in order to support DH based ciphers)                                                                            | `""`    |
 
-
 ### Metrics Parameters
 
 | Name                                         | Description                                                                                                         | Value                    |
@@ -511,7 +503,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRule.additionalLabels`    | Additional labels for the prometheusRule                                                                            | `{}`                     |
 | `metrics.prometheusRule.rules`               | Custom Prometheus rules                                                                                             | `[]`                     |
 
-
 ### Init Container Parameters
 
 | Name                                                   | Description                                                                                                   | Value                   |
@@ -538,7 +529,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `sysctl.resources.limits`                              | The resources limits for the init container                                                                   | `{}`                    |
 | `sysctl.resources.requests`                            | The requested resources for the init container                                                                | `{}`                    |
 
-
 ### useExternalDNS Parameters
 
 | Name                                   | Description                                                                                                                              | Value                               |
@@ -548,7 +538,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `useExternalDNS.annotationKey`         | The annotation key utilized when `external-dns` is enabled. Setting this to `false` will disable annotations.                            | `external-dns.alpha.kubernetes.io/` |
 | `useExternalDNS.suffix`                | The DNS suffix utilized when `external-dns` is enabled.  Note that we prepend the suffix with the full name of the release.              | `""`                                |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -564,7 +553,7 @@ The above command sets the Redis® server password to `secretpassword`.
 Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/redis
+helm install my-release -f values.yaml my-repo/redis
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -617,10 +606,10 @@ useExternalDNS:
 
 On a cluster where the name of the Helm release is `a`, the hostname of a Pod is generated as: `a-redis-node-0.a-redis.prod.example.org`. The IP of that FQDN will match that of the associated Pod. This modifies the following parameters of the Redis/Sentinel configuration using this new FQDN:
 
-* `replica-announce-ip`
-* `known-sentinel`
-* `known-replica`
-* `announce-ip`
+- `replica-announce-ip`
+- `known-sentinel`
+- `known-replica`
+- `announce-ip`
 
 :warning: This requires a working installation of `external-dns` to be fully functional. :warning:
 
@@ -655,7 +644,7 @@ In addition to this, only one service is exposed:
 
 For read-only operations, access the service using port 6379. For write operations, it's necessary to access the Redis® Sentinel cluster and query the current master using the command below (using redis-cli or similar):
 
-```
+```console
 SENTINEL get-master-addr-by-name <name of your MasterSet. e.g: mymaster>
 ```
 
@@ -670,6 +659,7 @@ In case the current master crashes, the Sentinel containers will elect a new mas
 When `master.count` is greater than `1`, special care must be taken to create a consistent setup.
 
 An example of use case is the creation of a redundant set of standalone masters or master-replicas per Kubernetes node where you must ensure:
+
 - No more than `1` master can be deployed per Kubernetes node
 - Replicas and writers can only see the single master of their own Kubernetes node
 
@@ -727,7 +717,7 @@ By default, the chart mounts a [Persistent Volume](https://kubernetes.io/docs/co
 3. Install the chart
 
 ```console
-$ helm install my-release --set master.persistence.existingClaim=PVC_NAME my-repo/redis
+helm install my-release --set master.persistence.existingClaim=PVC_NAME my-repo/redis
 ```
 
 ## Backup and restore
@@ -763,6 +753,7 @@ This major version updates the Redis&reg; docker image version used from `6.2` t
 This major release renames several values in this chart and adds missing features, in order to be inline with the rest of assets in the Bitnami charts repository.
 
 Affected values:
+
 - `master.service.port` renamed as `master.service.ports.redis`.
 - `master.service.nodePort` renamed as `master.service.nodePorts.redis`.
 - `replica.service.port` renamed as `replica.service.ports.redis`.
@@ -786,11 +777,11 @@ The Redis&reg; sentinel exporter was removed in this version because the upstrea
 ### To 14.0.0
 
 - Several parameters were renamed or disappeared in favor of new ones on this major version:
-    - The term *slave* has been replaced by the term *replica*. Therefore, parameters prefixed with `slave` are now prefixed with `replicas`.
-    - Credentials parameter are reorganized under the `auth` parameter.
-    - `cluster.enabled` parameter is deprecated in favor of `architecture` parameter that accepts two values: `standalone` and `replication`.
-    - `securityContext.*` is deprecated in favor of `XXX.podSecurityContext` and `XXX.containerSecurityContext`.
-    - `sentinel.metrics.*` parameters are deprecated in favor of `metrics.sentinel.*` ones.
+  - The term *slave* has been replaced by the term *replica*. Therefore, parameters prefixed with `slave` are now prefixed with `replicas`.
+  - Credentials parameter are reorganized under the `auth` parameter.
+  - `cluster.enabled` parameter is deprecated in favor of `architecture` parameter that accepts two values: `standalone` and `replication`.
+  - `securityContext.*` is deprecated in favor of `XXX.podSecurityContext` and `XXX.containerSecurityContext`.
+  - `sentinel.metrics.*` parameters are deprecated in favor of `metrics.sentinel.*` ones.
 - New parameters to add custom command, environment variables, sidecars, init containers, etc. were added.
 - Chart labels were adapted to follow the [Helm charts standard labels](https://helm.sh/docs/chart_best_practices/labels/#standard-labels).
 - values.yaml metadata was adapted to follow the format supported by [Readme Generator for Helm](https://github.com/bitnami-labs/readme-generator-for-helm).
@@ -803,10 +794,10 @@ Backwards compatibility is not guaranteed. To upgrade to `14.0.0`, install a new
 - 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`:
 
 ```console
-$ helm install redis my-repo/redis --set auth.password=[PASSWORD] --set master.persistence.existingClaim=[EXISTING_PVC]
+helm install redis my-repo/redis --set auth.password=[PASSWORD] --set master.persistence.existingClaim=[EXISTING_PVC]
 ```
 
-| Note: you need to substitute the placeholder _[EXISTING_PVC]_ with the name of the PVC used on your previous release, and _[PASSWORD]_ with the password used in your previous release.
+| Note: you need to substitute the placeholder *[EXISTING_PVC]* with the name of the PVC used on your previous release, and *[PASSWORD]* with the password used in your previous release.
 
 ### To 13.0.0
 
@@ -820,41 +811,29 @@ This version also introduces `bitnami/common`, a [library chart](https://helm.sh
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
-
-### To 11.0.0
-
-When deployed with sentinel enabled, only a group of nodes is deployed and the master/slave role is handled in the group. To avoid breaking the compatibility, the settings for this nodes are given through the `slave.xxxx` parameters in `values.yaml`
-
-### To 9.0.0
-
-The metrics exporter has been changed from a separate deployment to a sidecar container, due to the latest changes in the Redis&reg; exporter code. Check the [official page](https://github.com/oliver006/redis_exporter/) for more information. The metrics container image was changed from oliver006/redis_exporter to bitnami/redis-exporter (Bitnami's maintained package of oliver006/redis_exporter).
-
-### To 7.0.0
-
-In order to improve the performance in case of slave failure, we added persistence to the read-only slaves. That means that we moved from Deployment to StatefulSets. This should not affect upgrades from previous versions of the chart, as the deployments did not contain any persistence at all.
-
-This version also allows enabling Redis&reg; Sentinel containers inside of the Redis&reg; Pods (feature disabled by default). In case the master crashes, a new Redis&reg; node will be elected as master. In order to query the current master (no redis master service is exposed), you need to query first the Sentinel cluster.
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### To 11.0.0
 
 When using sentinel, a new statefulset called `-node` was introduced. This will break upgrading from a previous version where the statefulsets are called master and slave. Hence the PVC will not match the new naming and won't be reused. If you want to keep your data, you will need to perform a backup and then a restore the data in this new version.
 
+When deployed with sentinel enabled, only a group of nodes is deployed and the master/slave role is handled in the group. To avoid breaking the compatibility, the settings for this nodes are given through the `slave.xxxx` parameters in `values.yaml`
+
 ### To 10.0.0
 
 For releases with `usePassword: true`, the value `sentinel.usePassword` controls whether the password authentication also applies to the sentinel port. This defaults to `true` for a secure configuration, however it is possible to disable to account for the following cases:
@@ -864,6 +843,10 @@ For releases with `usePassword: true`, the value `sentinel.usePassword` controls
 
 If using a master/slave topology, or with `usePassword: false`, no action is required.
 
+### To 9.0.0
+
+The metrics exporter has been changed from a separate deployment to a sidecar container, due to the latest changes in the Redis&reg; exporter code. Check the [official page](https://github.com/oliver006/redis_exporter/) for more information. The metrics container image was changed from oliver006/redis_exporter to bitnami/redis-exporter (Bitnami's maintained package of oliver006/redis_exporter).
+
 ### To 8.0.18
 
 For releases with `metrics.enabled: true` the default tag for the exporter image is now `v1.x.x`. This introduces many changes including metrics names. You'll want to use [this dashboard](https://github.com/oliver006/redis_exporter/blob/master/contrib/grafana_prometheus_redis_dashboard.json) now. Please see the [redis_exporter github page](https://github.com/oliver006/redis_exporter#upgrading-from-0x-to-1x) for more details.
@@ -874,16 +857,16 @@ 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>
-   ```
+```console
+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
-   ```
+```console
+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.
 
@@ -914,23 +897,23 @@ must be specified.
 
 This version removes the `chart` label from the `spec.selector.matchLabels`
 which is immutable since `StatefulSet apps/v1beta2`. It has been inadvertently
-added, causing any subsequent upgrade to fail. See https://github.com/helm/charts/issues/7726.
+added, causing any subsequent upgrade to fail. See <https://github.com/helm/charts/issues/7726>.
 
-It also fixes https://github.com/helm/charts/issues/7726 where a deployment `extensions/v1beta1` can not be upgraded if `spec.selector` is not explicitly set.
+It also fixes <https://github.com/helm/charts/issues/7726> where a deployment `extensions/v1beta1` can not be upgraded if `spec.selector` is not explicitly set.
 
-Finally, it fixes https://github.com/helm/charts/issues/7803 by removing mutable labels in `spec.VolumeClaimTemplate.metadata.labels` so that it is upgradable.
+Finally, it fixes <https://github.com/helm/charts/issues/7803> by removing mutable labels in `spec.VolumeClaimTemplate.metadata.labels` so that it is upgradable.
 
 In order to upgrade, delete the Redis&reg; StatefulSet before upgrading:
 
 ```console
-$ kubectl delete statefulsets.apps --cascade=false my-release-redis-master
+kubectl delete statefulsets.apps --cascade=false my-release-redis-master
 ```
 
 And edit the Redis&reg; slave (and metrics if enabled) deployment:
 
 ```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"}]'
+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
@@ -941,10 +924,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/redmine/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/redmine
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/redmine
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/redmine
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/redmine
 ```
 
 The command deploys Redmine on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ The command deploys Redmine 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.
@@ -57,8 +57,8 @@ 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
+```console
+helm install my-release my-repo/redmine --set databaseType=postgresql
 ```
 
 ## Parameters
@@ -71,7 +71,6 @@ $ helm install my-release my-repo/redmine --set databaseType=postgresql
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value           |
@@ -87,7 +86,6 @@ $ helm install my-release my-repo/redmine --set databaseType=postgresql
 | `diagnosticMode.command` | Command to override all containers in the the deployment                                | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the the deployment                                   | `["infinity"]`  |
 
-
 ### Redmine Configuration parameters
 
 | Name                    | Description                                                                                             | Value                 |
@@ -118,7 +116,6 @@ $ helm install my-release my-repo/redmine --set databaseType=postgresql
 | `extraEnvVarsCM`        | Name of existing ConfigMap containing extra env vars                                                    | `""`                  |
 | `extraEnvVarsSecret`    | Name of existing Secret containing extra env vars                                                       | `""`                  |
 
-
 ### Redmine deployment parameters
 
 | Name                                 | Description                                                                                                              | Value           |
@@ -178,7 +175,6 @@ $ helm install my-release my-repo/redmine --set databaseType=postgresql
 | `initContainers`                     | Add additional init containers to the Redmine pods                                                                       | `[]`            |
 | `sidecars`                           | Add additional sidecar containers to the Redmine pod                                                                     | `[]`            |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -209,7 +205,6 @@ $ helm install my-release my-repo/redmine --set databaseType=postgresql
 | `ingress.secrets`                  | If you're providing your own certificates, please use this to add the certificates as secrets                                    | `[]`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Persistence Parameters
 
 | Name                                                   | Description                                                                                     | Value   |
@@ -228,7 +223,6 @@ $ helm install my-release my-repo/redmine --set databaseType=postgresql
 | `volumePermissions.containerSecurityContext.enabled`   | Enable init container's Security Context                                                        | `true`  |
 | `volumePermissions.containerSecurityContext.runAsUser` | Set init container's Security Context runAsUser                                                 | `0`     |
 
-
 ### RBAC Parameters
 
 | Name                                          | Description                                                                                              | Value   |
@@ -238,7 +232,6 @@ $ helm install my-release my-repo/redmine --set databaseType=postgresql
 | `serviceAccount.automountServiceAccountToken` | Auto-mount the service account token in the pod                                                          | `false` |
 | `serviceAccount.annotations`                  | Additional custom annotations for the ServiceAccount                                                     | `{}`    |
 
-
 ### Other Parameters
 
 | Name                       | Description                                                    | Value   |
@@ -252,7 +245,6 @@ $ helm install my-release my-repo/redmine --set databaseType=postgresql
 | `autoscaling.targetCPU`    | Target CPU utilization percentage                              | `50`    |
 | `autoscaling.targetMemory` | Target Memory utilization percentage                           | `50`    |
 
-
 ### Database Parameters
 
 | Name                                         | Description                                                             | Value             |
@@ -278,7 +270,6 @@ $ helm install my-release my-repo/redmine --set databaseType=postgresql
 | `externalDatabase.existingSecret`            | Name of an existing secret resource containing the database credentials | `""`              |
 | `externalDatabase.existingSecretPasswordKey` | Name of an existing secret key containing the database credentials      | `""`              |
 
-
 ### Mail Receiver/Cron Job Parameters
 
 | Name                                                 | Description                                                                                                                                   | Value         |
@@ -334,7 +325,6 @@ $ helm install my-release my-repo/redmine --set databaseType=postgresql
 | `mailReceiver.extraVolumes`                          | Optionally specify extra list of additional volumes for mailReceiver container                                                                | `[]`          |
 | `mailReceiver.extraVolumeMounts`                     | Optionally specify extra list of additional volumeMounts for mailReceiver container                                                           | `[]`          |
 
-
 ### Custom Certificates parameters
 
 | Name                                                 | Description                                                                                             | Value                                    |
@@ -354,7 +344,6 @@ $ helm install my-release my-repo/redmine --set databaseType=postgresql
 | `certificates.image.pullSecrets`                     | Redmine image pull secrets                                                                              | `[]`                                     |
 | `certificates.extraEnvVars`                          | Container sidecar extra environment variables (e.g. proxy)                                              | `[]`                                     |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                          | Description                                                                                                                 | Value   |
@@ -372,7 +361,6 @@ $ helm install my-release my-repo/redmine --set databaseType=postgresql
 | `networkPolicy.egressRules.denyConnectionsToExternal`         | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                              | `false` |
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                                  | `{}`    |
 
-
 The above parameters map to the env variables defined in [bitnami/redmine](https://github.com/bitnami/containers/tree/main/bitnami/redmine). For more information please refer to the [bitnami/redmine](https://github.com/bitnami/containers/tree/main/bitnami/redmine) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -390,7 +378,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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/redmine
+helm install my-release -f values.yaml my-repo/redmine
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -410,7 +398,7 @@ Redmine writes uploaded files to a persistent volume. By default that volume can
 > **Important**: When running more than one instance of Redmine they must share the same `secret_key_base` to have sessions working acreoss all instances.
 > This can be achieved by setting
 >
-> ```
+> ```yaml
 >   extraEnvVars:
 >    - name: SECRET_KEY_BASE
 >      value: someredminesecretkeybase
@@ -418,7 +406,7 @@ Redmine writes uploaded files to a persistent volume. By default that volume can
 
 ### Deploying to a sub-URI
 
-(adapted from https://github.com/bitnami/containers/tree/main/bitnami/redmine)
+(adapted from <https://github.com/bitnami/containers/tree/main/bitnami/redmine>)
 
 On certain occasions, you may need that Redmine is available under a specific sub-URI path rather than the root. A common scenario to this problem may arise if you plan to set up your Redmine container behind a reverse proxy. To deploy your Redmine container using a certain sub-URI you just need to follow these steps:
 
@@ -505,7 +493,7 @@ The following example includes two PVCs, one for Redmine and another for MariaDB
 1. Install the chart
 
 ```console
-$ helm install test --set persistence.existingClaim=PVC_REDMINE,mariadb.persistence.existingClaim=PVC_MARIADB my-repo/redmine
+helm install test --set persistence.existingClaim=PVC_REDMINE,mariadb.persistence.existingClaim=PVC_MARIADB my-repo/redmine
 ```
 
 ## Certificates
@@ -523,12 +511,12 @@ certificates:
     - secret: my-ca-2
 ```
 
-#### Secret
+#### CA Certificates Secret
 
 Secret can be created with:
 
 ```console
-$ kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
+kubectl create secret generic my-ca-1 --from-file my-ca-1.crt
 ```
 
 ### TLS Certificate
@@ -548,18 +536,18 @@ certificates:
       key: chain.pem
 ```
 
-#### Secret
+#### TLS Certificate Secret
 
 The certificate tls secret can be created with:
 
 ```console
-$ kubectl create secret tls my-secret --cert tls.crt --key tls.key
+kubectl create secret tls my-secret --cert tls.crt --key tls.key
 ```
 
 The certificate chain is created with:
 
 ```console
-$ kubectl create secret generic my-cert-chain --from-file chain.pem
+kubectl create secret generic my-cert-chain --from-file chain.pem
 ```
 
 ## Troubleshooting
@@ -592,10 +580,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/schema-registry/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/schema-registry
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/schema-registry
 ```
 
 ## Introduction
@@ -33,8 +33,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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/schema-registry
+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.
@@ -46,7 +46,7 @@ These commands deploy Schema Registry on the Kubernetes cluster with the default
 To uninstall/delete the `my-release` chart:
 
 ```console
-$ helm delete my-release
+helm delete my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -62,7 +62,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 | `kubeVersion`             | Override Kubernetes version                     | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                          | Value           |
@@ -78,7 +77,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                                 | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                                    | `["infinity"]`  |
 
-
 ### Schema Registry parameters
 
 | Name                                            | Description                                                                                                     | Value                     |
@@ -114,7 +112,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsCM`                                | Name of existing ConfigMap containing extra env vars                                                            | `""`                      |
 | `extraEnvVarsSecret`                            | Name of existing Secret containing extra env vars                                                               | `""`                      |
 
-
 ### Schema Registry statefulset parameters
 
 | Name                                 | Description                                                                                                              | Value           |
@@ -177,7 +174,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `autoscaling.targetCPU`              | Target CPU utilization percentage                                                                                        | `""`            |
 | `autoscaling.targetMemory`           | Target Memory utilization percentage                                                                                     | `""`            |
 
-
 ### Exposure Parameters
 
 | Name                               | Description                                                                                           | Value                    |
@@ -214,7 +210,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.secrets`                  | Custom TLS certificates as secrets                                                                    | `[]`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                               | `[]`                     |
 
-
 ### RBAC parameters
 
 | Name                                          | Description                                                      | Value  |
@@ -224,7 +219,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.annotations`                  | Additional Service Account annotations (evaluated as a template) | `{}`   |
 | `serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account   | `true` |
 
-
 ### Kafka chart parameters
 
 | Name                                             | Description                                                                                                         | Value                            |
@@ -252,7 +246,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalKafka.auth.jaas.user`                   | User for SASL authentication                                                                                        | `user`                           |
 | `externalKafka.auth.jaas.password`               | Password for SASL authentication                                                                                    | `""`                             |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -266,7 +259,7 @@ 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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/schema-registry
+helm install my-release -f values.yaml my-repo/schema-registry
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -314,9 +307,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 +330,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
@@ -444,24 +437,24 @@ This version bump the version of charts used as dependency in a major. Kafka fro
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ## Troubleshooting
 
@@ -475,10 +468,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/sealed-secrets/README.md

@@ -6,13 +6,11 @@ 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
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ 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
 ```
 
 ## Introduction
@@ -33,8 +31,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/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.
@@ -46,7 +44,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.
@@ -61,7 +59,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                        | Value           |
@@ -75,7 +72,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `clusterDomain`     | Kubernetes cluster domain name                     | `cluster.local` |
 | `extraDeploy`       | Array of extra objects to deploy with the release  | `[]`            |
 
-
 ### Sealed Secrets Parameters
 
 | Name                                                | Description                                                                                                              | Value                    |
@@ -149,7 +145,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `sidecars`                                          | Add additional sidecar containers to the Sealed Secret pod(s)                                                            | `{}`                     |
 | `initContainers`                                    | Add additional init containers to the Sealed Secret pod(s)                                                               | `{}`                     |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                           | Value                    |
@@ -181,7 +176,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.secrets`                  | Custom TLS certificates as secrets                                                                    | `[]`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                               | `[]`                     |
 
-
 ### Other Parameters
 
 | Name                                          | Description                                                      | Value   |
@@ -198,7 +192,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.enabled`                       | Specifies whether a NetworkPolicy should be created              | `false` |
 | `networkPolicy.allowExternal`                 | Don't require client label for connections                       | `true`  |
 
-
 ### Metrics parameters
 
 | Name                                       | Description                                                                      | Value   |
@@ -215,7 +208,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.serviceMonitor.relabelings`       | Specify general relabeling                                                       | `[]`    |
 | `metrics.serviceMonitor.selector`          | Prometheus instance selector labels                                              | `{}`    |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -229,7 +221,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)
@@ -300,10 +292,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/solr/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/solr
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/solr
 ```
 
 ## 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/solr
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/solr
 ```
 
 These commands deploy Solr 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 Solr on the Kubernetes cluster in the default configuratio
 To uninstall/delete the `my-release` statefulset:
 
 ```console
-$ helm delete my-release
+helm delete my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release. Use the option `--purge` to delete all history too.
@@ -61,7 +61,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                  | Value           |
@@ -77,7 +76,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the statefulset                                        | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the statefulset                                           | `["infinity"]`  |
 
-
 ### Solr parameters
 
 | Name                             | Description                                                                                          | Value                   |
@@ -109,7 +107,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsCM`                 | ConfigMap with extra environment variables                                                           | `""`                    |
 | `extraEnvVarsSecret`             | Secret with extra environment variables                                                              | `""`                    |
 
-
 ### Solr statefulset parameters
 
 | Name                                    | Description                                                                                                              | Value           |
@@ -170,7 +167,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `initContainers`                        | Add init containers to the Solr pod(s)                                                                                   | `[]`            |
 | `sidecars`                              | Add sidecars to the Solr pod(s)                                                                                          | `[]`            |
 
-
 ### Traffic Exposure parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -201,7 +197,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.secrets`                  | If you're providing your own certificates, please use this to add the certificates as secrets                                    | `[]`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Persistence parameters
 
 | Name                        | Description                                                            | Value               |
@@ -217,7 +212,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `persistence.subPathExpr`   | Expanded path within the volume from which                             | `""`                |
 | `persistence.selector`      | Selector to match an existing Persistent Volume for WordPress data PVC | `{}`                |
 
-
 ### Volume Permissions parameters
 
 | Name                                                   | Description                                                                                                                       | Value                   |
@@ -233,7 +227,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.requests`                 | Init container volume-permissions resource requests                                                                               | `{}`                    |
 | `volumePermissions.containerSecurityContext.runAsUser` | User ID for the init container                                                                                                    | `0`                     |
 
-
 ### Other Parameters
 
 | Name                                          | Description                                                            | Value   |
@@ -243,7 +236,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.automountServiceAccountToken` | Allows auto mount of ServiceAccountToken on the serviceAccount created | `true`  |
 | `serviceAccount.annotations`                  | Additional custom annotations for the ServiceAccount                   | `{}`    |
 
-
 ### Solr TLS parameters
 
 | Name                         | Description                                                                      | Value   |
@@ -257,7 +249,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `tls.resources.limits`       | The resources limits for the TLS init container                                  | `{}`    |
 | `tls.resources.requests`     | The requested resources for the TLS init container                               | `{}`    |
 
-
 ### Metrics parameters
 
 | Name                                            | Description                                                                                                                    | Value                                                                 |
@@ -340,7 +331,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRule.additionalLabels`       | Additional labels for the prometheusRule                                                                                       | `{}`                                                                  |
 | `metrics.prometheusRule.rules`                  | Custom Prometheus rules                                                                                                        | `[]`                                                                  |
 
-
 ### ZooKeeper parameters
 
 | Name                                 | Description                                                               | Value                 |
@@ -355,7 +345,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `zookeeper.persistence.size`         | Persistent Volume size                                                    | `8Gi`                 |
 | `externalZookeeper.servers`          | List of external zookeeper servers to use                                 | `[]`                  |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -368,7 +357,7 @@ The above command enabled the Solr Cloud mode.
 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/solr
+helm install my-release -f values.yaml my-repo/solr
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -468,7 +457,9 @@ image:
   repository: bitnami/solr
   tag: 8.9.0
 ```
+
 VS
+
 ```yaml
 image:
   registry: docker.io
@@ -496,10 +487,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/sonarqube
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/sonarqube
 ```
 
 ## Introduction
@@ -31,8 +31,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/sonarqube
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/sonarqube
 ```
 
 The command deploys SonarQube™ on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -44,7 +44,7 @@ The command deploys SonarQube™ on the Kubernetes cluster in the default co
 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.
@@ -59,7 +59,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                             | Value           |
@@ -75,7 +74,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                    | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                       | `["infinity"]`  |
 
-
 ### SonarQube™ Image parameters
 
 | Name                | Description                                                                                                      | Value                |
@@ -88,7 +86,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `image.pullSecrets` | SonarQube™ image pull secrets                                                                              | `[]`                 |
 | `image.debug`       | Enable SonarQube™ image debug mode                                                                         | `false`              |
 
-
 ### SonarQube™ Configuration parameters
 
 | Name                          | Description                                                                                                                                                               | Value                                                    |
@@ -110,8 +107,8 @@ The command removes all the Kubernetes components associated with the chart and
 | `ldap.url`                    | URL of the LDAP server. If you are using ldaps, you should install the server certificate into the Java truststore                                                        | `""`                                                     |
 | `ldap.bindDn`                 | The username of an LDAP user to connect (or bind) with. Leave this blank for anonymous access to the LDAP directory.                                                      | `""`                                                     |
 | `ldap.bindPassword`           | The password of the user to connect with. Leave this blank for anonymous access to the LDAP directory.                                                                    | `""`                                                     |
-| `ldap.authentication`         | Possible values: simple, CRAM-MD5, DIGEST-MD5, GSSAPI. See the tutorial on authentication mechanisms (http://java.sun.com/products/jndi/tutorial/ldap/security/auth.html) | `simple`                                                 |
-| `ldap.realm`                  | See Digest-MD5 Authentication, CRAM-MD5 Authentication (http://java.sun.com/products/jndi/tutorial/ldap/security/digest.html)                                             | `""`                                                     |
+| `ldap.authentication`         | Possible values: simple, CRAM-MD5, DIGEST-MD5, GSSAPI. See the tutorial on authentication mechanisms (<http://java.sun.com/products/jndi/tutorial/ldap/security/auth.html>) | `simple`                                                 |
+| `ldap.realm`                  | See Digest-MD5 Authentication, CRAM-MD5 Authentication (<http://java.sun.com/products/jndi/tutorial/ldap/security/digest.html>)                                             | `""`                                                     |
 | `ldap.contextFactoryClass`    | Context factory class.                                                                                                                                                    | `com.sun.jndi.ldap.LdapCtxFactory`                       |
 | `ldap.StartTLS`               | Enable use of StartTLS                                                                                                                                                    | `false`                                                  |
 | `ldap.followReferrals`        | Follow referrals or not                                                                                                                                                   | `true`                                                   |
@@ -134,7 +131,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsCM`              | Name of existing ConfigMap containing extra env vars for SonarQube&trade; nodes                                                                                           | `""`                                                     |
 | `extraEnvVarsSecret`          | Name of existing Secret containing extra env vars for SonarQube&trade; nodes                                                                                              | `""`                                                     |
 
-
 ### SonarQube&trade; deployment parameters
 
 | Name                                    | Description                                                                                    | Value           |
@@ -190,7 +186,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `sidecars`                              | Add additional sidecar containers to the SonarQube&trade; pod(s)                               | `[]`            |
 | `initContainers`                        | Add additional init containers to the SonarQube&trade; pod(s)                                  | `[]`            |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -223,7 +218,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.secrets`                  | Custom TLS certificates as secrets                                                                                               | `[]`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### SonarQube caCerts provisioning parameters
 
 | Name                                         | Description                                                                                                   | Value                   |
@@ -240,7 +234,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `caCerts.resources.requests`                 | The requested resources for the init container                                                                | `{}`                    |
 | `caCerts.containerSecurityContext.runAsUser` | Set init container's Security Context runAsUser                                                               | `0`                     |
 
-
 ### SonarQube plugin provisioning parameters
 
 | Name                                         | Description                                                                                                   | Value                   |
@@ -258,7 +251,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `plugins.resources.requests`                 | The requested resources for the init container                                                                | `{}`                    |
 | `plugins.containerSecurityContext.runAsUser` | Set init container's Security Context runAsUser                                                               | `0`                     |
 
-
 ### Persistence Parameters
 
 | Name                                                   | Description                                                                                                   | Value                   |
@@ -281,7 +273,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.requests`                 | The requested resources for the init container                                                                | `{}`                    |
 | `volumePermissions.containerSecurityContext.runAsUser` | Set init container's Security Context runAsUser                                                               | `0`                     |
 
-
 ### Sysctl Image parameters
 
 | Name                        | Description                                                                                                   | Value                   |
@@ -296,7 +287,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `sysctl.resources.limits`   | The resources limits for the init container                                                                   | `{}`                    |
 | `sysctl.resources.requests` | The requested resources for the init container                                                                | `{}`                    |
 
-
 ### Other Parameters
 
 | Name                                          | Description                                                                                                         | Value   |
@@ -312,7 +302,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `autoscaling.targetCPU`                       | Target CPU utilization percentage                                                                                   | `50`    |
 | `autoscaling.targetMemory`                    | Target Memory utilization percentage                                                                                | `50`    |
 
-
 ### Metrics parameters
 
 | Name                                                | Description                                                                                                  | Value                  |
@@ -344,7 +333,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.serviceMonitor.relabelings`                | Specify general relabeling                                                                                   | `[]`                   |
 | `metrics.serviceMonitor.selector`                   | Prometheus instance selector labels                                                                          | `{}`                   |
 
-
 ### PostgreSQL subchart settings
 
 | Name                                           | Description                                                                        | Value               |
@@ -362,7 +350,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `postgresql.primary.persistence.accessMode`    | PVC Access Mode for PostgreSQL volume                                              | `ReadWriteOnce`     |
 | `postgresql.primary.persistence.size`          | PVC Storage Request for PostgreSQL volume                                          | `8Gi`               |
 
-
 ### External Database settings
 
 | Name                              | Description                                                                                                     | Value       |
@@ -374,7 +361,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.database`       | Database inside an external PostgreSQL to connect (only if postgresql.enabled=false)                            | `sonarqube` |
 | `externalDatabase.port`           | Port of an external PostgreSQL to connect (only if postgresql.enabled=false)                                    | `5432`      |
 
-
 The above parameters map to the env variables defined in [bitnami/sonarqube](https://github.com/bitnami/containers/tree/main/bitnami/sonarqube). For more information please refer to the [bitnami/sonarqube](https://github.com/bitnami/containers/tree/main/bitnami/sonarqube) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -394,7 +380,7 @@ The above command sets the sonarqube 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/sonarqube
+helm install my-release -f values.yaml my-repo/sonarqube
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -489,7 +475,7 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,

bitnami/spark/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/spark
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/spark
 ```
 
 ## 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/spark
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/spark
 ```
 
 These commands deploy Apache Spark 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 Apache Spark on the Kubernetes cluster in the default conf
 To uninstall/delete the `my-release` statefulset:
 
 ```console
-$ helm delete my-release
+helm delete my-release
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release. Use the option `--purge` to delete all persistent volumes too.
@@ -61,7 +61,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                                                                         | Value           |
@@ -81,7 +80,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                                                                                | `["sleep"]`     |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                                                                                   | `["infinity"]`  |
 
-
 ### Spark parameters
 
 | Name                | Description                                                                                           | Value                 |
@@ -95,7 +93,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `image.debug`       | Enable image debug mode                                                                               | `false`               |
 | `hostNetwork`       | Enable HOST Network                                                                                   | `false`               |
 
-
 ### Spark master parameters
 
 | Name                                                     | Description                                                                                                              | Value           |
@@ -166,7 +163,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `master.sidecars`                                        | Add additional sidecar containers to the master pod(s)                                                                   | `[]`            |
 | `master.initContainers`                                  | Add initContainers to the master pods.                                                                                   | `[]`            |
 
-
 ### Spark worker parameters
 
 | Name                                                     | Description                                                                                                              | Value           |
@@ -248,7 +244,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `worker.autoscaling.targetCPU`                           | Target CPU utilization percentage                                                                                        | `50`            |
 | `worker.autoscaling.targetMemory`                        | Target Memory utilization percentage                                                                                     | `""`            |
 
-
 ### Security parameters
 
 | Name                                 | Description                                                                   | Value     |
@@ -268,7 +263,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `security.ssl.resources.limits`      | The resources limits for the container                                        | `{}`      |
 | `security.ssl.resources.requests`    | The requested resources for the container                                     | `{}`      |
 
-
 ### Traffic Exposure parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -303,7 +297,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.secrets`                  | If you're providing your own certificates, please use this to add the certificates as secrets                                    | `[]`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Other parameters
 
 | Name                                          | Description                                            | Value  |
@@ -313,7 +306,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `serviceAccount.annotations`                  | Annotations for Spark Service Account                  | `{}`   |
 | `serviceAccount.automountServiceAccountToken` | Automount API credentials for a service account.       | `true` |
 
-
 ### Metrics parameters
 
 | Name                                       | Description                                                                                                                             | Value   |
@@ -332,7 +324,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRule.additionalLabels`  | Additional labels that can be used so prometheusRules will be discovered by Prometheus                                                  | `{}`    |
 | `metrics.prometheusRule.rules`             | Custom Prometheus [rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/)                                   | `[]`    |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
@@ -345,7 +336,7 @@ The above command sets the spark master web port to `8081`.
 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/spark
+helm install my-release -f values.yaml my-repo/spark
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -480,10 +471,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/spring-cloud-dataflow/README.md

@@ -6,13 +6,11 @@ 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
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/spring-cloud-dataflow
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/spring-cloud-dataflow
 ```
 
 ## Introduction
@@ -32,8 +30,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/spring-cloud-dataflow
+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.
@@ -45,7 +43,7 @@ These commands deploy Spring Cloud Data Flow on the Kubernetes cluster with the
 To uninstall/delete the `my-release` chart:
 
 ```console
-$ helm uninstall my-release
+helm uninstall my-release
 ```
 
 ## Parameters
@@ -58,7 +56,6 @@ $ helm uninstall my-release
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                           | Value           |
@@ -71,7 +68,6 @@ $ helm uninstall my-release
 | `clusterDomain`     | Default Kubernetes cluster domain                                                     | `cluster.local` |
 | `extraDeploy`       | Array of extra objects to deploy with the release                                     | `[]`            |
 
-
 ### Dataflow Server parameters
 
 | Name                                                | Description                                                                                                                                | Value                                                |
@@ -188,7 +184,6 @@ $ helm uninstall my-release
 | `server.proxy`                                      | Add proxy configuration for SCDF server                                                                                                    | `{}`                                                 |
 | `server.applicationProperties`                      | Specify common application properties added by SCDF server to streams and/or tasks                                                         | `{}`                                                 |
 
-
 ### Dataflow Skipper parameters
 
 | Name                                         | Description                                                                                                          | Value                          |
@@ -281,7 +276,6 @@ $ helm uninstall my-release
 | `externalSkipper.host`                       | Host of a external Skipper Server                                                                                    | `localhost`                    |
 | `externalSkipper.port`                       | External Skipper Server port number                                                                                  | `7577`                         |
 
-
 ### Deployer parameters
 
 | Name                                          | Description                                                                                                                                     | Value          |
@@ -302,7 +296,6 @@ $ helm uninstall my-release
 | `deployer.entryPointStyle`                    | An entry point style affects how application properties are passed to the container to be deployed. Allowed values: exec (default), shell, boot | `exec`         |
 | `deployer.imagePullPolicy`                    | An image pull policy defines when a Docker image should be pulled to the local registry. Allowed values: IfNotPresent (default), Always, Never  | `IfNotPresent` |
 
-
 ### RBAC parameters
 
 | Name                                          | Description                                                                                                             | Value  |
@@ -313,7 +306,6 @@ $ helm uninstall my-release
 | `serviceAccount.annotations`                  | Annotations for service account. Evaluated as a template. Only used if `create` is `true`.                              | `{}`   |
 | `rbac.create`                                 | Whether to create and use RBAC resources or not                                                                         | `true` |
 
-
 ### Metrics parameters
 
 | Name                                         | Description                                                                                                                | Value                              |
@@ -391,7 +383,6 @@ $ helm uninstall my-release
 | `metrics.autoscaling.targetCPU`              | Target CPU utilization percentage                                                                                          | `""`                               |
 | `metrics.autoscaling.targetMemory`           | Target Memory utilization percentage                                                                                       | `""`                               |
 
-
 ### Init Container parameters
 
 | Name                                 | Description                                                                                                                     | Value                 |
@@ -406,7 +397,6 @@ $ helm uninstall my-release
 | `waitForBackends.resources.limits`   | Init container wait-for-backend resource limits                                                                                 | `{}`                  |
 | `waitForBackends.resources.requests` | Init container wait-for-backend resource requests                                                                               | `{}`                  |
 
-
 ### Database parameters
 
 | Name                                      | Description                                                                                         | Value        |
@@ -436,7 +426,6 @@ $ helm uninstall my-release
 | `externalDatabase.skipper.username`       | Existing username in the external db to be used by Skipper server                                   | `skipper`    |
 | `externalDatabase.hibernateDialect`       | Hibernate Dialect used by Dataflow/Skipper servers                                                  | `""`         |
 
-
 ### RabbitMQ chart parameters
 
 | Name                                      | Description                                                                     | Value       |
@@ -451,7 +440,6 @@ $ helm uninstall my-release
 | `externalRabbitmq.vhost`                  | External RabbitMQ virtual host. It will be saved in a kubernetes secret         | `""`        |
 | `externalRabbitmq.existingPasswordSecret` | Existing secret with RabbitMQ password. It will be saved in a kubernetes secret | `""`        |
 
-
 ### Kafka chart parameters
 
 | Name                                  | Description                             | Value            |
@@ -464,11 +452,10 @@ $ helm uninstall my-release
 | `externalKafka.brokers`               | External Kafka brokers                  | `localhost:9092` |
 | `externalKafka.zkNodes`               | External Zookeeper nodes                | `localhost:2181` |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
-$ helm install my-release --set server.replicaCount=2 my-repo/spring-cloud-dataflow
+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.
@@ -476,7 +463,7 @@ The above command installs Spring Cloud Data Flow chart with 2 Dataflow server r
 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/spring-cloud-dataflow
+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)
@@ -634,6 +621,7 @@ This chart will facilitate the creation of TLS secrets for use with the ingress
 - An additional tool (like [cert-manager](https://github.com/jetstack/cert-manager/)) manages the secrets for the application.
 In the first two cases, it's needed a certificate and a key. We would expect them to look like this:
 - certificate files should look like (and there can be more than one certificate if there is a certificate chain)
+
   ```console
   -----BEGIN CERTIFICATE-----
   MIID6TCCAtGgAwIBAgIJAIaCwivkeB5EMA0GCSqGSIb3DQEBCwUAMFYxCzAJBgNV
@@ -641,7 +629,9 @@ In the first two cases, it's needed a certificate and a key. We would expect the
   jScrvkiBO65F46KioCL9h5tDvomdU1aqpI/CBzhvZn1c0ZTf87tGQR8NK7v7
   -----END CERTIFICATE-----
   ```
+
 - keys should look like:
+
   ```console
   -----BEGIN RSA PRIVATE KEY-----
   MIIEogIBAAKCAQEAvLYcyu8f3skuRyUgeeNpeDvYBCDcgq+LsWap6zbX5f8oLqp4
@@ -649,6 +639,7 @@ In the first two cases, it's needed a certificate and a key. We would expect the
   wrj2wDbCDCFmfqnSJ+dKI3vFLlEz44sAV8jX/kd4Y6ZTQhlLbYc=
   -----END RSA PRIVATE KEY-----
   ```
+
 - If you are going to use Helm to manage the certificates based on the parameters, please copy these values into the `certificate` and `key` values for a given `server.ingress.secrets` entry.
 - In case you are going to manage TLS secrets separately, please know that you must create a TLS secret with name *INGRESS_HOSTNAME-tls* (where *INGRESS_HOSTNAME* is a placeholder to be replaced with the hostname you set using the `server.ingress.hostname` parameter).
 - To use self-signed certificates created by Helm, set `server.ingress.tls` to `true` and `server.ingress.certManager` to `false`.
@@ -713,11 +704,11 @@ 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:
 
 ```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)
+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:
+1. Upgrade your release using the same Kafka version:
 
 ```console
 $ export CURRENT_KAFKA_VERSION=$(kubectl exec scdf-kafka-0 -- bash -c 'echo $BITNAMI_IMAGE_VERSION')
@@ -753,35 +744,35 @@ This major updates the Kafka subchart to its newest major 13.0.0. For more infor
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+#### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+#### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+#### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
 ### v0.x.x
 
 ```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]
+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
 
 ```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]
+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
@@ -795,11 +786,11 @@ 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:
 
 ```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)
+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:
@@ -842,10 +833,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/suitecrm/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/suitecrm
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/suitecrm
 ```
 
 ## Introduction
@@ -37,8 +37,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/suitecrm
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/suitecrm
 ```
 
 The command deploys SuiteCRM on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -50,7 +50,7 @@ The command deploys SuiteCRM 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.
@@ -65,7 +65,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                                  | Value |
@@ -77,7 +76,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `commonAnnotations` | Common annotations to add to all SuiteCRM resources (sub-charts are not considered). Evaluated as a template | `{}`  |
 | `commonLabels`      | Common labels to add to all SuiteCRM resources (sub-charts are not considered). Evaluated as a template      | `{}`  |
 
-
 ### SuiteCRM parameters
 
 | Name                                    | Description                                                                                              | Value                 |
@@ -163,7 +161,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `podAnnotations`                        | Pod annotations                                                                                          | `{}`                  |
 | `podLabels`                             | Pod extra labels                                                                                         | `{}`                  |
 
-
 ### Database parameters
 
 | Name                                        | Description                                                                              | Value               |
@@ -187,7 +184,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `externalDatabase.database`                 | Name of the existing database                                                            | `bitnami_suitecrm`  |
 | `externalDatabase.existingSecret`           | Name of an existing secret resource containing the DB password                           | `""`                |
 
-
 ### Persistence parameters
 
 | Name                        | Description                              | Value               |
@@ -200,7 +196,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `persistence.hostPath`      | Host mount path for SuiteCRM volume      | `""`                |
 | `persistence.annotations`   | Persistent Volume Claim annotations      | `{}`                |
 
-
 ### Volume Permissions parameters
 
 | Name                                   | Description                                                                                                                                               | Value                   |
@@ -215,7 +210,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.limits`   | The resources limits for the container                                                                                                                    | `{}`                    |
 | `volumePermissions.resources.requests` | The requested resources for the container                                                                                                                 | `{}`                    |
 
-
 ### Traffic Exposure Parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -247,7 +241,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.ingressClassName`         | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)                                                    | `""`                     |
 | `ingress.extraRules`               | Additional rules to be covered with this ingress record                                                                          | `[]`                     |
 
-
 ### Metrics parameters
 
 | Name                                       | Description                                                                                                     | Value                     |
@@ -271,7 +264,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.service.sessionAffinity`          | Session Affinity for Kubernetes service, can be "None" or "ClientIP"                                            | `None`                    |
 | `metrics.service.sessionAffinityConfig`    | Additional settings for the sessionAffinity                                                                     | `{}`                      |
 
-
 ### Certificate injection parameters
 
 | Name                                                 | Description                                                                                                       | Value                                    |
@@ -295,7 +287,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `certificates.image.pullPolicy`                      | Container sidecar image pull policy                                                                               | `IfNotPresent`                           |
 | `certificates.image.pullSecrets`                     | Container sidecar image pull secrets                                                                              | `[]`                                     |
 
-
 ### NetworkPolicy parameters
 
 | Name                                                          | Description                                                                                                                  | Value   |
@@ -316,7 +307,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.egressRules.denyConnectionsToExternal`         | Enable egress rule that denies outgoing traffic outside the cluster, except for DNS (port 53).                               | `false` |
 | `networkPolicy.egressRules.customRules`                       | Custom network policy rule                                                                                                   | `{}`    |
 
-
 The above parameters map to the env variables defined in [bitnami/suitecrm](https://github.com/bitnami/containers/tree/main/bitnami/suitecrm). For more information please refer to the [bitnami/suitecrm](https://github.com/bitnami/containers/tree/main/bitnami/suitecrm) image documentation.
 
 > **Note**:
@@ -348,7 +338,7 @@ The above command sets the SuiteCRM 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/suitecrm
+helm install my-release -f values.yaml my-repo/suitecrm
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -399,7 +389,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
 1. Install the chart
 
     ```console
-    $ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/suitecrm
+    helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/suitecrm
     ```
 
 ### Host path
@@ -415,7 +405,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
 1. Install the chart
 
     ```console
-    $ helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/suitecrm
+    helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT my-repo/suitecrm
     ```
 
     This will mount the `suitecrm-data` volume into the `hostPath` directory. The site data will be persisted if the mount path contains valid data, else the site data will be initialized at first launch.
@@ -453,34 +443,34 @@ In this major there were three main changes introduced:
 
 Please read the update notes carefully.
 
-**1. Adaptation to Helm v2 EOL**
+#### 1. Adaptation to Helm v2 EOL
 
 [On November 13, 2020, Helm v2 support was formally finished](https://github.com/helm/charts#status-of-the-project), this major version is the result of the required changes applied to the Helm Chart to be able to incorporate the different features added in Helm v3 and to be consistent with the Helm project itself regarding the Helm v2 EOL.
 
-**What changes were introduced in this major version?**
+##### What changes were introduced in this major version?
 
 - Previous versions of this Helm Chart use `apiVersion: v1` (installable by both Helm 2 and 3), this Helm Chart was updated to `apiVersion: v2` (installable by Helm 3 only). [Here](https://helm.sh/docs/topics/charts/#the-apiversion-field) you can find more information about the `apiVersion` field.
 - Move dependency information from the *requirements.yaml* to the *Chart.yaml*
 - After running `helm dependency update`, a *Chart.lock* file is generated containing the same structure used in the previous *requirements.lock*
 - The different fields present in the *Chart.yaml* file has been ordered alphabetically in a homogeneous way for all the Bitnami Helm Charts
 
-**Considerations when upgrading to this version**
+##### Considerations when upgrading to this version
 
 - If you want to upgrade to this version from a previous one installed with Helm v3, you shouldn't face any issues
 - If you want to upgrade to this version using Helm v2, this scenario is not supported as this version doesn't support Helm v2 anymore
 - If you installed the previous version with Helm v2 and wants to upgrade to this version with Helm v3, please refer to the [official Helm documentation](https://helm.sh/docs/topics/v2_v3_migration/#migration-use-cases) about migrating from Helm v2 to v3
 
-**Useful links**
+##### Useful links
 
-- https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/
-- https://helm.sh/docs/topics/v2_v3_migration/
-- https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/
+- <https://docs.bitnami.com/tutorials/resolve-helm2-helm3-post-migration-issues/>
+- <https://helm.sh/docs/topics/v2_v3_migration/>
+- <https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/>
 
-**2. Updated MariaDB dependency version**
+#### 2. Updated MariaDB dependency version
 
 In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-800) for more information.
 
-**3. Migration of the SuiteCRM image to non-root **
+#### 3. Migration of the SuiteCRM image to non-root
 
 The [Bitnami SuiteCRM](https://github.com/bitnami/containers/tree/main/bitnami/suitecrm) image was updated to support and enable the "non-root" user approach
 
@@ -498,23 +488,23 @@ 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:
 
 ```console
-$ helm upgrade suitecrm my-repo/suitecrm --set suitecrmPassword=$SUITECRM_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 8.0.26
+helm upgrade suitecrm my-repo/suitecrm --set suitecrmPassword=$SUITECRM_PASSWORD --set replicaCount=0 --set mariadb.enabled=false --version 8.0.26
 ```
 
 Finally, upgrade your release to `9.0.0` reusing the existing PVC, and enabling back MariaDB:
 
 ```console
-$ helm upgrade suitecrm my-repo/suitecrm --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set suitecrmPassword=$SUITECRM_PASSWORD --set containerSecurityContext.runAsUser=0 --set podSecurityContext.fsGroup=0
+helm upgrade suitecrm my-repo/suitecrm --set mariadb.primary.persistence.existingClaim=$MARIADB_PVC --set mariadb.auth.rootPassword=$MARIADB_ROOT_PASSWORD --set mariadb.auth.password=$MARIADB_PASSWORD --set suitecrmPassword=$SUITECRM_PASSWORD --set containerSecurityContext.runAsUser=0 --set podSecurityContext.fsGroup=0
 ```
 
 You should see the lines below in MariaDB container logs:
@@ -533,7 +523,7 @@ This upgrade also adapts the chart to the latest Bitnami good practices. Check t
 
 Helm performs a lookup for the object based on its group (apps), version (v1), and kind (Deployment). Also known as its GroupVersionKind, or GVK. Changing the GVK is considered a compatibility breaker from Kubernetes' point of view, so you cannot "upgrade" those objects to the new GVK in-place. Earlier versions of Helm 3 did not perform the lookup correctly which has since been fixed to match the spec.
 
-In https://github.com/helm/charts/pull/17310 the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
+In <https://github.com/helm/charts/pull/17310> the `apiVersion` of the deployment resources was updated to `apps/v1` in tune with the api's deprecated, resulting in compatibility breakage.
 
 This major version signifies this change.
 
@@ -543,8 +533,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 suitecrm:
 
 ```console
-$ kubectl patch deployment suitecrm-suitecrm --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
-$ kubectl delete statefulset suitecrm-mariadb --cascade=false
+kubectl patch deployment suitecrm-suitecrm --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl delete statefulset suitecrm-mariadb --cascade=false
 ```
 
 ## Community supported solution
@@ -563,10 +553,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/tensorflow-resnet/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/tensorflow-resnet
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/tensorflow-resnet
 ```
 
 ## Introduction
@@ -31,8 +31,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/tensorflow-resnet
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/tensorflow-resnet
 ```
 
 These commands deploy Tensorflow Serving ResNet model on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -44,12 +44,13 @@ These commands deploy Tensorflow Serving ResNet model on the Kubernetes cluster
 To uninstall/delete the `my-release` deployment:
 
 ```console
-$ helm delete my-release
+helm delete my-release
 ```
+
 You can check your releases with:
 
 ```console
-$ helm list
+helm list
 ```
 
 The command removes all the Kubernetes components associated with the chart and deletes the release.
@@ -63,7 +64,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imageRegistry`    | Global Docker image registry                    | `""`  |
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 
-
 ### Common parameters
 
 | Name                     | Description                                                                                  | Value          |
@@ -78,7 +78,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `diagnosticMode.command` | Command to override all containers in the deployment                                         | `["sleep"]`    |
 | `diagnosticMode.args`    | Args to override all containers in the deployment                                            | `["infinity"]` |
 
-
 ### TensorFlow parameters
 
 | Name                                    | Description                                                                                                        | Value                        |
@@ -167,17 +166,16 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.enabled`                       | Enable Prometheus exporter to expose Tensorflow server metrics                                                     | `false`                      |
 | `metrics.podAnnotations`                | Prometheus exporter pod annotations                                                                                | `{}`                         |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
-$ helm install my-release my-repo/tensorflow-resnet --set imagePullPolicy=Always
+helm install my-release my-repo/tensorflow-resnet --set imagePullPolicy=Always
 ```
 
 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/tensorflow-resnet
+helm install my-release -f values.yaml my-repo/tensorflow-resnet
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -218,16 +216,15 @@ This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs
 
 [Learn more about this change and related upgrade considerations](https://docs.bitnami.com/kubernetes/infrastructure/tensorflow-resnet/administration/upgrade-helm3/).
 
-
 ### To 2.0.0
 
 Backwards compatibility is not guaranteed unless you modify the labels used on the chart's deployments.
 Use the workaround below to upgrade from versions previous to 2.0.0. The following example assumes that the release name is tensorflow-resnet:
 
 ```console
-$ kubectl delete deployment  tensorflow-resnet --cascade=false
-$ helm upgrade tensorflow-resnet my-repo/tensorflow-resnet
-$ kubectl delete rs "$(kubectl get rs -l app=tensorflow-resnet -o jsonpath='{.items[0].metadata.name}')"
+kubectl delete deployment  tensorflow-resnet --cascade=false
+helm upgrade tensorflow-resnet my-repo/tensorflow-resnet
+kubectl delete rs "$(kubectl get rs -l app=tensorflow-resnet -o jsonpath='{.items[0].metadata.name}')"
 ```
 
 ## License
@@ -238,10 +235,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/thanos/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/thanos
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/thanos
 ```
 
 ## 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/thanos
+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.
@@ -45,14 +45,14 @@ These commands deploy Thanos on the Kubernetes cluster with the default configur
 To uninstall/delete the `my-release` chart:
 
 ```console
-$ helm uninstall my-release
+helm uninstall my-release
 ```
 
 ## Architecture
 
 This charts allows you install several Thanos components, so you deploy an architecture as the one below:
 
-```
+```text
                        +--------------+                  +--------------+      +--------------+
                        | Thanos       |----------------> | Thanos Store |      | Thanos       |
                        | Query        |           |      | Gateway      |      | Compactor    |
@@ -91,7 +91,6 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                  | Value           |
@@ -104,7 +103,6 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `clusterDomain`     | Kubernetes Cluster Domain                                                                    | `cluster.local` |
 | `extraDeploy`       | Array of extra objects to deploy with the release                                            | `[]`            |
 
-
 ### Thanos common parameters
 
 | Name                                          | Description                                                                                                         | Value               |
@@ -138,7 +136,6 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account                                                      | `true`              |
 | `serviceAccount.annotations`                  | Annotations for service account. Evaluated as a template. Only used if `create` is `true`.                          | `{}`                |
 
-
 ### Thanos Query parameters
 
 | Name                                                      | Description                                                                                                                             | Value                    |
@@ -289,7 +286,6 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `query.ingress.grpc.path`                                 | Ingress Path                                                                                                                            | `/`                      |
 | `query.ingress.grpc.pathType`                             | Ingress Path type                                                                                                                       | `ImplementationSpecific` |
 
-
 ### Thanos Query Frontend parameters
 
 | Name                                                              | Description                                                                                                                      | Value                    |
@@ -397,7 +393,6 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `queryFrontend.ingress.path`                                      | Ingress path                                                                                                                     | `/`                      |
 | `queryFrontend.ingress.pathType`                                  | Ingress path type                                                                                                                | `ImplementationSpecific` |
 
-
 ### Thanos Bucket Web parameters
 
 | Name                                                          | Description                                                                                                                      | Value                    |
@@ -501,7 +496,6 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `bucketweb.ingress.path`                                      | Ingress path                                                                                                                     | `/`                      |
 | `bucketweb.ingress.pathType`                                  | Ingress path type                                                                                                                | `ImplementationSpecific` |
 
-
 ### Thanos Compactor parameters
 
 | Name                                                          | Description                                                                                                                      | Value                    |
@@ -604,7 +598,6 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `compactor.persistence.annotations`                           | Annotations for the PVC                                                                                                          | `{}`                     |
 | `compactor.persistence.existingClaim`                         | Name of an existing PVC to use                                                                                                   | `""`                     |
 
-
 ### Thanos Store Gateway parameters
 
 | Name                                                             | Description                                                                                                                              | Value                       |
@@ -745,7 +738,6 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `storegateway.sharded.service.http.nodePorts`                    | Array of http node ports used for Store Gateway service. Length must be the same as the number of shards                                 | `[]`                        |
 | `storegateway.sharded.service.grpc.nodePorts`                    | Array of grpc node ports used for Store Gateway service. Length must be the same as the number of shards                                 | `[]`                        |
 
-
 ### Thanos Ruler parameters
 
 | Name                                                      | Description                                                                                                                      | Value                    |
@@ -863,7 +855,6 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `ruler.ingress.path`                                      | Ingress path                                                                                                                     | `/`                      |
 | `ruler.ingress.pathType`                                  | Ingress path type                                                                                                                | `ImplementationSpecific` |
 
-
 ### Thanos Receive parameters
 
 | Name                                                        | Description                                                                                                                      | Value                    |
@@ -990,7 +981,6 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `receive.ingress.path`                                      | Ingress Path                                                                                                                     | `/`                      |
 | `receive.ingress.pathType`                                  | Ingress Path type                                                                                                                | `ImplementationSpecific` |
 
-
 ### Thanos Receive Distributor parameters
 
 | Name                                                                   | Description                                                                                                                 | Value           |
@@ -1071,7 +1061,6 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `receiveDistributor.pdb.minAvailable`                                  | Minimum number/percentage of pods that should remain scheduled                                                              | `1`             |
 | `receiveDistributor.pdb.maxUnavailable`                                | Maximum number/percentage of pods that may be made unavailable                                                              | `""`            |
 
-
 ### Metrics parameters
 
 | Name                                                                                    | Description                                                                                                                                                   | Value   |
@@ -1147,7 +1136,6 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `metrics.prometheusRule.additionalLabels`                                               | Additional labels for the prometheusRule                                                                                                                      | `{}`    |
 | `metrics.prometheusRule.groups`                                                         | Prometheus Rule Groups for Thanos components                                                                                                                  | `[]`    |
 
-
 ### Volume Permissions parameters
 
 | Name                                  | Description                                                                                                                       | Value                   |
@@ -1160,7 +1148,6 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `volumePermissions.image.pullPolicy`  | Init container volume-permissions image pull policy                                                                               | `IfNotPresent`          |
 | `volumePermissions.image.pullSecrets` | Specify docker-registry secret names as an array                                                                                  | `[]`                    |
 
-
 ### MinIO® chart parameters
 
 | Name                      | Description                                                                                                                       | Value    |
@@ -1171,7 +1158,6 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `minio.auth.rootPassword` | Password for MinIO® root user                                                                                                 | `""`     |
 | `minio.defaultBuckets`    | Comma, semi-colon or space separated list of MinIO® buckets to create                                                         | `thanos` |
 
-
 ### NetWorkPolicy parameters
 
 | Name                                       | Description                                                                                    | Value   |
@@ -1180,11 +1166,10 @@ Check the section [Integrate Thanos with Prometheus and Alertmanager](#integrate
 | `networkPolicy.allowExternal`              | Don't require client label for connections                                                     | `true`  |
 | `networkPolicy.explicitNamespacesSelector` | A Kubernetes LabelSelector to explicitly select namespaces from which traffic could be allowed | `{}`    |
 
-
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
-$ helm install my-release --set query.replicaCount=2 my-repo/thanos
+helm install my-release --set query.replicaCount=2 my-repo/thanos
 ```
 
 The above command install Thanos chart with 2 Thanos Query replicas.
@@ -1192,7 +1177,7 @@ 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,
 
 ```console
-$ helm install my-release -f values.yaml my-repo/thanos
+helm install my-release -f values.yaml my-repo/thanos
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -1511,7 +1496,7 @@ This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs
 
 The querier component and its settings have been renamed to query. Configuration of the query component by using keys under `querier` in your `values.yaml` will continue to work. Support for keys under `querier` will be dropped in a future release.
 
-```
+```text
 querier.enabled                               -> query.enabled
 querier.logLevel                              -> query.logLevel
 querier.replicaLabel                          -> query.replicaLabel
@@ -1628,7 +1613,7 @@ To specify the values via CLI::
 
 If you are upgrading from a `<1.0.0` release you need to move your Querier Ingress information to the new values settings:
 
-```
+```text
 ingress.enabled -> querier.ingress.enabled
 ingress.certManager -> querier.ingress.certManager
 ingress.hostname -> querier.ingress.hostname
@@ -1650,10 +1635,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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/tomcat/README.md

@@ -11,8 +11,8 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-$ helm repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/tomcat
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/tomcat
 ```
 
 ## Introduction
@@ -35,8 +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 repo add my-repo https://charts.bitnami.com/bitnami
-$ helm install my-release my-repo/tomcat
+helm repo add my-repo https://charts.bitnami.com/bitnami
+helm install my-release my-repo/tomcat
 ```
 
 These commands deploy Tomcat on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -48,7 +48,7 @@ These commands deploy Tomcat 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.
@@ -63,7 +63,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]`  |
 | `global.storageClass`     | Global StorageClass for Persistent Volume(s)    | `""`  |
 
-
 ### Common parameters
 
 | Name                | Description                                                                                  | Value           |
@@ -76,7 +75,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `clusterDomain`     | Kubernetes Cluster Domain                                                                    | `cluster.local` |
 | `extraDeploy`       | Array of extra objects to deploy with the release                                            | `[]`            |
 
-
 ### Tomcat parameters
 
 | Name                          | Description                                                                                            | Value                  |
@@ -99,7 +97,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `extraEnvVarsCM`              | Name of existing ConfigMap containing extra environment variables                                      | `""`                   |
 | `extraEnvVarsSecret`          | Name of existing Secret containing extra environment variables                                         | `""`                   |
 
-
 ### Tomcat deployment parameters
 
 | Name                                       | Description                                                                                                              | Value               |
@@ -168,7 +165,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `networkPolicy.allowExternal`              | Don't require client label for connections                                                                               | `true`              |
 | `networkPolicy.explicitNamespacesSelector` | A Kubernetes LabelSelector to explicitly select namespaces from which traffic could be allowed                           | `{}`                |
 
-
 ### Traffic Exposure parameters
 
 | Name                               | Description                                                                                                                      | Value                    |
@@ -199,7 +195,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `ingress.path`                     | Ingress path                                                                                                                     | `/`                      |
 | `ingress.pathType`                 | Ingress path type                                                                                                                | `ImplementationSpecific` |
 
-
 ### Volume Permissions parameters
 
 | Name                                   | Description                                                                                                                       | Value                   |
@@ -214,7 +209,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `volumePermissions.resources.limits`   | Init container volume-permissions resource  limits                                                                                | `{}`                    |
 | `volumePermissions.resources.requests` | Init container volume-permissions resource  requests                                                                              | `{}`                    |
 
-
 ### Metrics parameters
 
 | Name                                                | Description                                                                                                  | Value                                                                                                                                                                                                               |
@@ -249,7 +243,6 @@ The command removes all the Kubernetes components associated with the chart and
 | `metrics.prometheusRule.namespace`                  | namespace where prometheusRules resource should be created                                                   | `""`                                                                                                                                                                                                                |
 | `metrics.prometheusRule.rules`                      | Create specified [Rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/)         | `[]`                                                                                                                                                                                                                |
 
-
 The above parameters map to the env variables defined in [bitnami/tomcat](https://github.com/bitnami/containers/tree/main/bitnami/tomcat). For more information please refer to the [bitnami/tomcat](https://github.com/bitnami/containers/tree/main/bitnami/tomcat) image documentation.
 
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -266,7 +259,7 @@ The above command sets the Tomcat management username and password to `manager`
 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/tomcat
+helm install my-release -f values.yaml my-repo/tomcat
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -350,9 +343,9 @@ Consequences:
 - Backwards compatibility is not guaranteed. However, you can easily workaround this issue by removing Tomcat deployment before upgrading (the following example assumes that the release name is `tomcat`):
 
 ```console
-$ export TOMCAT_PASSWORD=$(kubectl get secret --namespace default tomcat -o jsonpath="{.data.tomcat-password}" | base64 -d)
-$ kubectl delete deployments.apps tomcat
-$ helm upgrade tomcat my-repo/tomcat --set tomcatPassword=$TOMCAT_PASSWORD
+export TOMCAT_PASSWORD=$(kubectl get secret --namespace default tomcat -o jsonpath="{.data.tomcat-password}" | base64 -d)
+kubectl delete deployments.apps tomcat
+helm upgrade tomcat my-repo/tomcat --set tomcatPassword=$TOMCAT_PASSWORD
 ```
 
 ### To 7.0.0
@@ -369,14 +362,14 @@ This release updates the Bitnami Tomcat container to `9.0.26-debian-9-r0`, which
 
 Tomcat container was moved to a non-root approach. There shouldn't be any issue when upgrading since the corresponding `securityContext` is enabled by default. Both the container image and the chart can be upgraded by running the command below:
 
-```
-$ helm upgrade my-release my-repo/tomcat
+```console
+helm upgrade my-release my-repo/tomcat
 ```
 
 If you use a previous container image (previous to **8.5.35-r26**) disable the `securityContext` by running the command below:
 
-```
-$ helm upgrade my-release my-repo/tomcat --set securityContext.enabled=false,image.tag=XXX
+```console
+helm upgrade my-release my-repo/tomcat --set securityContext.enabled=false,image.tag=XXX
 ```
 
 ### To 1.0.0
@@ -385,7 +378,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 tomcat:
 
 ```console
-$ kubectl patch deployment tomcat --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
+kubectl patch deployment tomcat --type=json -p='[{"op": "remove", "path": "/spec/selector/matchLabels/chart"}]'
 ```
 
 ## License
@@ -396,10 +389,10 @@ Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at
 
-    http://www.apache.org/licenses/LICENSE-2.0
+<http://www.apache.org/licenses/LICENSE-2.0>
 
 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.