[bitnami/*] Make Helm charts 100% OCI (#15998)

* [bitnami/*] Make Helm charts 100% OCI

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

* Add main files and scaffolding

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

* Bump chart version

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

* Improve helm upgrade instruction

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

* Revert bitnami/common version bump

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

* Prettify Chart.yamls

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

* Regenerate Chart.lock and bump chart versions

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

---------

Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
This commit is contained in:
Carlos Rodríguez Hernández
2023-04-20 11:06:43 +02:00
committed by GitHub
parent 4596ed932f
commit 884151035e
344 changed files with 1320 additions and 1544 deletions

View File

@@ -1,6 +1,6 @@
dependencies:
- name: common
repository: https://charts.bitnami.com/bitnami
repository: oci://registry-1.docker.io/bitnamicharts
version: 2.2.4
digest: sha256:634d19e9b7f6e4c07d7c04a0161ab96b3f83335ebdd70b35b952319ef0a2586b
generated: "2023-03-19T00:31:08.537841512Z"
digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
generated: "2023-04-20T09:36:15.52127+02:00"

View File

@@ -5,7 +5,7 @@ apiVersion: v2
appVersion: 3.11.13
dependencies:
- name: common
repository: https://charts.bitnami.com/bitnami
repository: oci://registry-1.docker.io/bitnamicharts
tags:
- bitnami-common
version: 2.x.x
@@ -23,4 +23,4 @@ name: rabbitmq
sources:
- https://github.com/bitnami/containers/tree/main/bitnami/rabbitmq
- https://www.rabbitmq.com
version: 11.13.0
version: 11.14.0

View File

@@ -11,8 +11,7 @@ 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 install my-release oci://registry-1.docker.io/bitnamicharts/rabbitmq
```
## Introduction
@@ -32,8 +31,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
To install the chart with the release name `my-release`:
```console
helm repo add my-repo https://charts.bitnami.com/bitnami
helm install my-release my-repo/rabbitmq
helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -371,7 +369,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
```console
helm install my-release \
--set auth.username=admin,auth.password=secretpassword,auth.erlangCookie=secretcookie \
my-repo/rabbitmq
oci://registry-1.docker.io/bitnamicharts/rabbitmq
```
The above command sets the RabbitMQ admin username and password to `admin` and `secretpassword` respectively. Additionally the secure erlang cookie is set to `secretcookie`.
@@ -381,7 +379,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 oci://registry-1.docker.io/bitnamicharts/rabbitmq
```
> **Tip**: You can use the default [values.yaml](values.yaml)
@@ -513,7 +511,7 @@ This happens if the pod management policy of the statefulset is not `Parallel` a
```console
$ kubectl delete statefulset STATEFULSET_NAME --cascade=false
helm upgrade RELEASE_NAME my-repo/rabbitmq \
helm upgrade RELEASE_NAME oci://registry-1.docker.io/bitnamicharts/rabbitmq \
--set podManagementPolicy=Parallel \
--set replicaCount=NUMBER_OF_REPLICAS \
--set auth.password=PASSWORD \
@@ -525,7 +523,7 @@ For a faster resyncronization of the nodes, you can temporarily disable the read
If the steps above don't bring the cluster to a healthy state, it could be possible that none of the RabbitMQ nodes think they were the last node to be up during the shutdown. In those cases, you can force the boot of the nodes by specifying the `clustering.forceBoot=true` parameter (which will execute [`rabbitmqctl force_boot`](https://www.rabbitmq.com/rabbitmqctl.8.html#force_boot) in each pod):
```console
helm upgrade RELEASE_NAME my-repo/rabbitmq \
helm upgrade RELEASE_NAME oci://registry-1.docker.io/bitnamicharts/rabbitmq \
--set podManagementPolicy=Parallel \
--set clustering.forceBoot=true \
--set replicaCount=NUMBER_OF_REPLICAS \
@@ -552,7 +550,7 @@ The chart mounts a [Persistent Volume](https://kubernetes.io/docs/concepts/stora
3. 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 oci://registry-1.docker.io/bitnamicharts/rabbitmq
```
### Adjust permissions of the persistence volume mountpoint
@@ -587,7 +585,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 oci://registry-1.docker.io/bitnamicharts/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.

View File

@@ -152,7 +152,7 @@ Validate values of rabbitmq - LDAP support
rabbitmq: LDAP
Invalid LDAP configuration. When enabling LDAP support, the parameters "ldap.servers" or "ldap.uri" are mandatory
to configure the connection and "ldap.userDnPattern" or "ldap.basedn" are necessary to lookup the users. Please provide them:
$ helm install {{ .Release.Name }} my-repo/rabbitmq \
$ helm install {{ .Release.Name }} oci://registry-1.docker.io/bitnamicharts/rabbitmq \
--set ldap.enabled=true \
--set ldap.servers[0]=my-ldap-server" \
--set ldap.port="389" \
@@ -174,7 +174,7 @@ rabbitmq: memoryHighWatermark
You enabled configuring memory high watermark using a relative limit. However,
no memory limits were defined at POD level. Define your POD limits as shown below:
$ helm install {{ .Release.Name }} my-repo/rabbitmq \
$ helm install {{ .Release.Name }} oci://registry-1.docker.io/bitnamicharts/rabbitmq \
--set memoryHighWatermark.enabled=true \
--set memoryHighWatermark.type="relative" \
--set memoryHighWatermark.value="0.4" \
@@ -182,7 +182,7 @@ rabbitmq: memoryHighWatermark
Altenatively, user an absolute value for the memory memory high watermark :
$ helm install {{ .Release.Name }} my-repo/rabbitmq \
$ helm install {{ .Release.Name }} oci://registry-1.docker.io/bitnamicharts/rabbitmq \
--set memoryHighWatermark.enabled=true \
--set memoryHighWatermark.type="absolute" \
--set memoryHighWatermark.value="512MB"
@@ -247,7 +247,7 @@ Get the extraConfigurationExistingSecret secret.
{{- if not (empty .Values.extraConfigurationExistingSecret) -}}
{{- include "getValueFromSecret" (dict "Namespace" .Release.Namespace "Name" .Values.extraConfigurationExistingSecret "Length" 10 "Key" "extraConfiguration") -}}
{{- else -}}
{{- tpl .Values.extraConfiguration . -}}
{{- tpl .Values.extraConfiguration . -}}
{{- end -}}
{{- end -}}