[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>

README.md

@@ -10,13 +10,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 install my-release oci://registry-1.docker.io/bitnamicharts/<chart>
 ```
 
-![Installing a chart](demo.gif)
-
 ## Vulnerabilities scanner
 
 Each Helm chart contains one or more containers. Those containers use images provided by Bitnami through its test & release pipeline and whose source code can be found at [bitnami/containers](https://github.com/bitnami/containers).
@@ -50,20 +46,6 @@ Helm is a tool for managing Kubernetes charts. Charts are packages of pre-config
 
 To install Helm, refer to the [Helm install guide](https://github.com/helm/helm#install) and ensure that the `helm` binary is in the `PATH` of your shell.
 
-### Add Repo
-
-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
-```
-
-> **_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.
->
-> This full index is updated every time the [truncated index file](https://raw.githubusercontent.com/bitnami/charts/index/bitnami/index.yaml) is updated. Take into account that this full index is under the [Github's rate limits](https://docs.github.com/en/developers/apps/building-github-apps/rate-limits-for-github-apps).
->
-> You can find more information in the [Bitnami index FAQ](https://github.com/bitnami/charts/issues/10833) pinned issue.
-
 ### Using Helm
 
 Once you have installed the Helm client, you can deploy a Bitnami Helm Chart into a Kubernetes cluster.
@@ -72,9 +54,8 @@ Please refer to the [Quick Start guide](https://helm.sh/docs/intro/quickstart/)
 
 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`
+- Install a chart: `helm install my-release oci://registry-1.docker.io/bitnamicharts/<chart>`
+- Upgrade your application: `helm upgrade my-release oci://registry-1.docker.io/bitnamicharts/<chart>`
 
 ## License
 

bitnami/airflow/Chart.lock

@@ -1,12 +1,12 @@
 dependencies:
 - name: redis
-  repository: https://charts.bitnami.com/bitnami
-  version: 17.9.2
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 17.9.5
 - name: postgresql
-  repository: https://charts.bitnami.com/bitnami
-  version: 12.2.6
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 12.2.8
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:9aef8c2ce2f98c143a055ee12ff948057363d426eeaddbca09234d8fcd0a0e8d
-generated: "2023-04-01T13:28:48.999832572Z"
+digest: sha256:5d98965bc63154164f23bd7ea59bc6ca413f9e73c60ee146a9be385db6bbe249
+generated: "2023-04-20T09:29:30.865803+02:00"

bitnami/airflow/Chart.yaml

@@ -6,14 +6,14 @@ appVersion: 2.5.3
 dependencies:
   - condition: redis.enabled
     name: redis
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 17.x.x
   - condition: postgresql.enabled
     name: postgresql
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 12.x.x
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -32,4 +32,4 @@ name: airflow
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/airflow
   - https://airflow.apache.org/
-version: 14.0.17
+version: 14.1.0

bitnami/airflow/README.md

@@ -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/airflow
+helm install my-release oci://registry-1.docker.io/bitnamicharts/airflow
 ```
 
 ## Introduction
@@ -31,8 +30,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/airflow
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -491,7 +489,7 @@ helm install my-release \
                --set auth.password=my-passsword \
                --set auth.fernetKey=my-fernet-key \
                --set auth.secretKey=my-secret-key \
-               my-repo/airflow
+               oci://registry-1.docker.io/bitnamicharts/airflow
 ```
 
 The above command sets the credentials to access the Airflow web UI.
@@ -501,7 +499,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 oci://registry-1.docker.io/bitnamicharts/airflow
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)

bitnami/airflow/templates/NOTES.txt

@@ -61,7 +61,7 @@ host. To configure Airflow with the URL of your service:
     {{ include "common.utils.secret.getvalue" (dict "secret" $airflowSecretName "field" "airflow-password" "context" $) }}
     {{ include "common.utils.secret.getvalue" (dict "secret" $airflowSecretName "field" "airflow-fernet-key" "context" $) }}
     {{ include "common.utils.secret.getvalue" (dict "secret" $airflowSecretName "field" "airflow-secret-key" "context" $) }}
-    helm upgrade --namespace {{ $releaseNamespace }} {{ .Release.Name }} my-repo/{{ .Chart.Name }} \
+    helm upgrade --namespace {{ $releaseNamespace }} {{ .Release.Name }} oci://registry-1.docker.io/bitnamicharts/{{ .Chart.Name }} \
       --set service.type={{ .Values.service.type }} \
       --set web.baseUrl=http://$AIRFLOW_HOST:$AIRFLOW_PORT \
       --set auth.password=$AIRFLOW_PASSWORD \

bitnami/apache/Chart.lock

@@ -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-07T16:09:45.753811428Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:29:36.2193+02:00"

bitnami/apache/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 2.4.57
 dependencies:
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -26,4 +26,4 @@ name: apache
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/apache
   - https://httpd.apache.org
-version: 9.3.3
+version: 9.4.0

bitnami/apache/README.md

@@ -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/apache
+helm install my-release oci://registry-1.docker.io/bitnamicharts/apache
 ```
 
 ## Introduction
@@ -35,8 +34,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/apache
+helm install my-release oci://registry-1.docker.io/bitnamicharts/apache
 ```
 
 These commands deploy Apache on the Kubernetes cluster in the default configuration.
@@ -247,7 +245,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
   --set imagePullPolicy=Always \
-    my-repo/apache
+    oci://registry-1.docker.io/bitnamicharts/apache
 ```
 
 The above command sets the `imagePullPolicy` to `Always`.
@@ -255,7 +253,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 oci://registry-1.docker.io/bitnamicharts/apache
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)

bitnami/appsmith/Chart.lock

@@ -1,12 +1,12 @@
 dependencies:
 - name: redis
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 17.9.5
 - name: mongodb
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 13.9.4
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:821a8b2cecd54caef7f9b1e3ff9391c13d79379cfd582ef6a6606f08f67ebed8
-generated: "2023-04-19T19:45:45.995253253Z"
+digest: sha256:0ac7d6e5c27bd24f85f477a9de42d9eac28733788d5f1759338cef8723bfd53f
+generated: "2023-04-20T09:29:41.813678+02:00"

bitnami/appsmith/Chart.yaml

@@ -6,14 +6,14 @@ appVersion: 1.9.16
 dependencies:
   - condition: redis.enabled
     name: redis
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 17.x.x
   - condition: mongodb.enabled
     name: mongodb
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 13.x.x
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -30,4 +30,4 @@ name: appsmith
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/appsmith
   - https://github.com/appsmithorg/appsmith/
-version: 0.1.23
+version: 0.2.0

bitnami/appsmith/README.md

@@ -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/appsmith
+helm install my-release oci://registry-1.docker.io/bitnamicharts/appsmith
 ```
 
 ## Introduction
@@ -37,8 +36,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/appsmith
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -438,7 +436,7 @@ helm install my-release \
   --set appsmithUsername=admin \
   --set appsmithPassword=password \
   --set mariadb.auth.rootPassword=secretpassword \
-    my-repo/appsmith
+    oci://registry-1.docker.io/bitnamicharts/appsmith
 ```
 
 The above command sets the appsmith administrator account username and password to `admin` and `password` respectively. Additionally, it sets the MariaDB `root` user password to `secretpassword`.
@@ -448,7 +446,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 oci://registry-1.docker.io/bitnamicharts/appsmith
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)

bitnami/argo-cd/Chart.lock

@@ -1,9 +1,9 @@
 dependencies:
 - name: redis
-  repository: https://charts.bitnami.com/bitnami
-  version: 17.9.2
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 17.9.5
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:70e895c1713e538dbed39e2bc51ab9c438cfa84bb7b26202ef5ca483dad54f85
-generated: "2023-04-01T10:21:51.971522719Z"
+digest: sha256:76be7ac900c3052b2b931b325d3160648aa3dbfa48b0387553954bfa84f2270a
+generated: "2023-04-20T09:29:48.084376+02:00"

bitnami/argo-cd/Chart.yaml

@@ -6,10 +6,10 @@ appVersion: 2.6.7
 dependencies:
   - condition: redis.enabled
     name: redis
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 17.x.x
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -30,4 +30,4 @@ sources:
   - https://github.com/argoproj/argo-cd/
   - https://github.com/bitnami/containers/tree/main/bitnami/dex
   - https://github.com/dexidp/dex
-version: 4.5.7
+version: 4.6.0

bitnami/argo-cd/README.md

@@ -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/argo-cd
+helm install my-release oci://registry-1.docker.io/bitnamicharts/argo-cd
 ```
 
 ## Introduction
@@ -33,8 +32,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/argo-cd
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -875,7 +873,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 helm install my-release \
   --set controller.replicaCount=2 \
   --set server.metrics.enabled=true \
-    my-repo/argo-cd
+    oci://registry-1.docker.io/bitnamicharts/argo-cd
 ```
 
 The above command sets the argo-cd controller replicas to 2, and enabled argo-cd server metrics.
@@ -885,7 +883,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 oci://registry-1.docker.io/bitnamicharts/argo-cd
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)

bitnami/argo-workflows/Chart.lock

@@ -1,12 +1,12 @@
 dependencies:
 - name: postgresql
-  repository: https://charts.bitnami.com/bitnami
-  version: 12.2.7
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 12.2.8
 - name: mysql
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 9.7.1
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:2af41f53f877194afb39bd2bb5fd666b9954e9e51f7c17c6ab4897849e00c2a3
-generated: "2023-04-14T15:39:29.013643977Z"
+digest: sha256:feb2539fe1bf8815c981135767f339c760cee3a04745085c286fef14d02731ec
+generated: "2023-04-20T09:29:54.600098+02:00"

bitnami/argo-workflows/Chart.yaml

@@ -6,14 +6,14 @@ appVersion: 3.4.7
 dependencies:
   - condition: postgresql.enabled
     name: postgresql
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 12.x.x
   - condition: mysql.enabled
     name: mysql
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 9.x.x
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -35,4 +35,4 @@ sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/argo-workflow-controller
   - https://github.com/bitnami/containers/tree/main/bitnami/argo-workflow-exec
   - https://argoproj.github.io/workflows/
-version: 5.1.14
+version: 5.2.0

bitnami/argo-workflows/README.md

@@ -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/argo-workflows
+helm install my-release oci://registry-1.docker.io/bitnamicharts/argo-workflows
 ```
 
 ## Introduction
@@ -33,8 +32,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/argo-workflows
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -372,7 +370,7 @@ helm install my-release \
   --set argo-workflowsUsername=admin \
   --set argo-workflowsPassword=password \
   --set mysql.auth.rootPassword=secretpassword \
-    my-repo/argo-workflows
+    oci://registry-1.docker.io/bitnamicharts/argo-workflows
 ```
 
 The above command sets the Argo Workflows administrator account username and password to `admin` and `password` respectively. Additionally, it sets the MySQL `root` user password to `secretpassword`.
@@ -382,7 +380,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 oci://registry-1.docker.io/bitnamicharts/argo-workflows
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)

bitnami/aspnet-core/Chart.lock

@@ -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-14T20:11:57.0742482Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:29:59.966106+02:00"

bitnami/aspnet-core/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 7.0.5
 dependencies:
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -22,4 +22,4 @@ name: aspnet-core
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/aspnet-core
   - https://dotnet.microsoft.com/apps/aspnet
-version: 4.0.11
+version: 4.1.0

bitnami/aspnet-core/README.md

@@ -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/aspnet-core
+helm install my-release oci://registry-1.docker.io/bitnamicharts/aspnet-core
 ```
 
 ## Introduction
@@ -33,8 +32,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/aspnet-core
+helm install my-release oci://registry-1.docker.io/bitnamicharts/aspnet-core
 ```
 
 These commands deploy a ASP.NET Core application on the Kubernetes cluster in the default configuration.
@@ -235,7 +233,7 @@ The command removes all the Kubernetes components associated with the chart and
 Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
 
 ```console
-helm install my-release --set replicaCount=2 my-repo/aspnet-core
+helm install my-release --set replicaCount=2 oci://registry-1.docker.io/bitnamicharts/aspnet-core
 ```
 
 The above command install ASP.NET Core chart with 2 replicas.
@@ -243,7 +241,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 oci://registry-1.docker.io/bitnamicharts/aspnet-core
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)

bitnami/cassandra/Chart.lock

@@ -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-30T17:03:09.169242221Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:30:05.929616+02:00"

bitnami/cassandra/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 4.1.1
 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: cassandra
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/cassandra
   - http://cassandra.apache.org
-version: 10.1.3
+version: 10.2.0

bitnami/cassandra/README.md

@@ -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/cassandra
+helm install my-release oci://registry-1.docker.io/bitnamicharts/cassandra
 ```
 
 ## 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/cassandra
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -298,13 +296,13 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
     --set dbUser.user=admin,dbUser.password=password \
-    my-repo/cassandra
+    oci://registry-1.docker.io/bitnamicharts/cassandra
 ```
 
 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 oci://registry-1.docker.io/bitnamicharts/cassandra
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -377,7 +375,7 @@ Find more information about how to deal with common errors related to Bitnami's
 It's necessary to set the `dbUser.password` parameter when upgrading for readiness/liveness probes to work properly. When you install this chart for the first time, some notes will be displayed providing the credentials you must use. Please note down the password and run the command below to upgrade your chart:
 
 ```console
-helm upgrade my-release my-repo/cassandra --set dbUser.password=[PASSWORD]
+helm upgrade my-release oci://registry-1.docker.io/bitnamicharts/cassandra --set dbUser.password=[PASSWORD]
 ```
 
 | Note: you need to substitute the placeholder *[PASSWORD]* with the value obtained in the installation notes.

bitnami/cert-manager/Chart.lock

@@ -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-18T21:23:47.554697037Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:30:10.012001+02:00"

bitnami/cert-manager/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 1.11.1
 dependencies:
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -26,4 +26,4 @@ sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/cert-manager-webhook
   - https://github.com/bitnami/containers/tree/main/bitnami/cainjector
   - https://github.com/jetstack/cert-manager
-version: 0.9.6
+version: 0.10.0

bitnami/cert-manager/README.md

@@ -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/cert-manager
+helm install my-release oci://registry-1.docker.io/bitnamicharts/cert-manager
 ```
 
 ## Introduction
@@ -34,8 +33,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/cert-manager
+helm install my-release oci://registry-1.docker.io/bitnamicharts/cert-manager
 ```
 
 > **Tip**: List all releases using `helm list`
@@ -291,14 +289,14 @@ 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 my-repo/cert-manager \
+helm install my-release oci://registry-1.docker.io/bitnamicharts/cert-manager \
   --set installCRDs=true
 ```
 
 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 oci://registry-1.docker.io/bitnamicharts/cert-manager
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)

bitnami/clickhouse/Chart.lock

@@ -1,9 +1,9 @@
 dependencies:
 - name: zookeeper
-  repository: https://charts.bitnami.com/bitnami
-  version: 11.1.5
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 11.1.6
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:a9cc33255fae632899c931e89126a7a0e9cec72fa758d499dd75f1ab752d1b0e
-generated: "2023-04-01T10:33:18.34925286Z"
+digest: sha256:8f7871559c22caaab01610a9404e89e01bcbe71227fe194f0c8f3b4e637ac083
+generated: "2023-04-20T09:30:14.880466+02:00"

bitnami/clickhouse/Chart.yaml

@@ -6,10 +6,10 @@ appVersion: 23.3.1
 dependencies:
   - condition: zookeeper.enabled
     name: zookeeper
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 11.x.x
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -26,4 +26,4 @@ name: clickhouse
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/clickhouse
   - https://github.com/ClickHouse/ClickHouse
-version: 3.1.6
+version: 3.2.0

bitnami/clickhouse/README.md

@@ -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/clickhouse
+helm install my-release oci://registry-1.docker.io/bitnamicharts/clickhouse
 ```
 
 ## Introduction
@@ -41,8 +40,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/clickhouse
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -349,7 +347,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 helm install my-release \
   --set auth.username=admin \
   --set auth.password=password \
-    my-repo/clickhouse
+    oci://registry-1.docker.io/bitnamicharts/clickhouse
 ```
 
 The above command sets the ClickHouse administrator account username and password to `admin` and `password` respectively.
@@ -359,7 +357,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 oci://registry-1.docker.io/bitnamicharts/clickhouse
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)

bitnami/common/README.md

@@ -8,7 +8,7 @@ A [Helm Library Chart](https://helm.sh/docs/topics/library_charts/#helm) for gro
 dependencies:
   - name: common
     version: 1.x.x
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
 ```
 
 ```console

bitnami/concourse/Chart.lock

@@ -1,9 +1,9 @@
 dependencies:
 - name: postgresql
-  repository: https://charts.bitnami.com/bitnami
-  version: 12.2.6
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 12.2.8
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:2f015b889c20d8a5ce515f1bcbc1c971566519ea667b3391dbaa1ce6111e9524
-generated: "2023-04-01T11:29:23.500026959Z"
+digest: sha256:8fa3132cf8f0a780f19c461dc2c659667c98d6287a3ceea0ecd618f5e6e1be20
+generated: "2023-04-20T09:30:20.268078+02:00"

bitnami/concourse/Chart.yaml

@@ -6,10 +6,10 @@ appVersion: 7.9.1
 dependencies:
   - condition: postgresql.enabled
     name: postgresql
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 12.X.X
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -30,4 +30,4 @@ name: concourse
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/concourse
   - https://github.com/concourse/concourse
-version: 2.0.7
+version: 2.1.0

bitnami/concourse/README.md

@@ -9,8 +9,7 @@ Concourse is an automation system written in Go. It is most commonly used for CI
 ## TL;DR
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/concourse
+helm install my-release oci://registry-1.docker.io/bitnamicharts/concourse
 ```
 
 ## Introduction
@@ -33,8 +32,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/concourse
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -398,7 +396,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
   --set secrets.localUsers=admin:password \
-    my-repo/concourse
+    oci://registry-1.docker.io/bitnamicharts/concourse
 ```
 
 The above command sets the Concourse account username and password to `admin` and `password` respectively.
@@ -408,7 +406,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 oci://registry-1.docker.io/bitnamicharts/concourse
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)

bitnami/concourse/templates/NOTES.txt

@@ -57,7 +57,7 @@ host. To configure Concourse with the URL of your service:
     {{- if and .Values.secrets.localAuth.enabled }}
     {{ include "common.utils.secret.getvalue" (dict "secret" $concourseWebSecretName "field" "local_users" "context" $) }}
     {{- end }}
-    helm upgrade --namespace {{ $releaseNamespace }} {{ .Release.Name }} my-repo/{{ .Chart.Name }} \
+    helm upgrade --namespace {{ $releaseNamespace }} {{ .Release.Name }} oci://registry-1.docker.io/bitnamicharts/{{ .Chart.Name }} \
       {{- if and .Values.secrets.localAuth.enabled }}
       --set secrets.localUsers=$LOCAL_USERS \
       {{- end }}
@@ -72,7 +72,7 @@ host. To configure Concourse with the URL of your service:
   {{- else }}
 
     ## PLEASE UPDATE THE EXTERNAL DATABASE CONNECTION PARAMETERS IN THE FOLLOWING COMMAND AS NEEDED ##
-    helm upgrade --namespace {{ $releaseNamespace }} {{ .Release.Name }} my-repo/{{ .Chart.Name }} \
+    helm upgrade --namespace {{ $releaseNamespace }} {{ .Release.Name }} oci://registry-1.docker.io/bitnamicharts/{{ .Chart.Name }} \
       {{- if and .Values.secrets.localAuth.enabled }}
       --set secrets.localUsers=$LOCAL_USERS \
       {{- end }}

bitnami/consul/Chart.lock

@@ -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-08T01:35:43.216545464Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:30:24.690468+02:00"

bitnami/consul/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 1.15.2
 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: consul
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/consul
   - https://www.consul.io/
-version: 10.10.2
+version: 10.11.0

bitnami/consul/README.md

@@ -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/consul
+helm install my-release oci://registry-1.docker.io/bitnamicharts/consul
 ```
 
 ## 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/consul
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -261,7 +259,7 @@ helm delete --purge my-release
 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 oci://registry-1.docker.io/bitnamicharts/consul
 ```
 
 The above command sets the HashiCorp Consul domain to `consul-domain` and sets the gossip key to `secretkey`.
@@ -271,7 +269,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 oci://registry-1.docker.io/bitnamicharts/consul
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -482,7 +480,7 @@ The field `podManagementPolicy` can't be updated in a StatefulSet, so you need t
 
 ```console
 kubectl delete statefulset consul
-helm upgrade <DEPLOYMENT_NAME> my-repo/consul
+helm upgrade <DEPLOYMENT_NAME> oci://registry-1.docker.io/bitnamicharts/consul
 ```
 
 ### To 6.0.0
@@ -494,13 +492,13 @@ 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:
 
 ```console
-helm upgrade my-release my-repo/consul
+helm upgrade my-release oci://registry-1.docker.io/bitnamicharts/consul
 ```
 
 If you use a previous container image (previous to **1.4.0-r16**) disable the `securityContext` by running the command below:
 
 ```console
-helm upgrade my-release my-repo/consul --set securityContext.enabled=false,image.tag=XXX
+helm upgrade my-release oci://registry-1.docker.io/bitnamicharts/consul --set securityContext.enabled=false,image.tag=XXX
 ```
 
 ### To 2.0.0

bitnami/contour-operator/Chart.lock

@@ -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-18T21:40:04.794730798Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:30:32.441224+02:00"

bitnami/contour-operator/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 1.24.0
 dependencies:
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -25,4 +25,4 @@ name: contour-operator
 sources:
   - https://github.com/projectcontour/contour-operator
   - https://github.com/bitnami/containers/tree/main/bitnami/contour-operator
-version: 4.0.3
+version: 4.1.0

bitnami/contour-operator/README.md

@@ -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/contour-operator
+helm install my-release oci://registry-1.docker.io/bitnamicharts/contour-operator
 ```
 
 ## Introduction
@@ -33,8 +32,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/contour-operator
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -268,7 +266,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
   --set livenessProbe.enabled=false \
-    my-repo/contour-operator
+    oci://registry-1.docker.io/bitnamicharts/contour-operator
 ```
 
 The above command disables the Operator liveness probes.
@@ -276,7 +274,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 oci://registry-1.docker.io/bitnamicharts/contour-operator
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)

bitnami/contour/Chart.lock

@@ -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-14T22:34:50.940686005Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:30:28.457298+02:00"

bitnami/contour/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 1.24.3
 dependencies:
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -25,4 +25,4 @@ sources:
   - https://github.com/envoyproxy/envoy
   - https://github.com/bitnami/containers/tree/main/bitnami/contour
   - https://projectcontour.io
-version: 11.1.3
+version: 11.2.0

bitnami/contour/README.md

@@ -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/contour
+helm install my-release oci://registry-1.docker.io/bitnamicharts/contour
 ```
 
 ## Introduction
@@ -34,8 +33,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/contour
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -426,7 +424,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
   --set envoy.readinessProbe.successThreshold=5 \
-    my-repo/contour
+    oci://registry-1.docker.io/bitnamicharts/contour
 ```
 
 The above command sets the `envoy.readinessProbe.successThreshold` to `5`.
@@ -619,7 +617,7 @@ 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 oci://registry-1.docker.io/bitnamicharts/contour
 ```
 
 If you made a backup earlier, restore the objects:

bitnami/discourse/Chart.lock

@@ -1,12 +1,12 @@
 dependencies:
 - name: redis
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 17.9.5
 - name: postgresql
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 12.2.8
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:a5ae630b50f722f253e26f9ba65867a625ace06acfb3244193320d5cf47fe56c
-generated: "2023-04-18T12:06:21.978889686Z"
+digest: sha256:bd145402361271d21b2a56635eef72cd76327158dacdad931ac3bd33fb0dd9e6
+generated: "2023-04-20T09:30:37.775796+02:00"

bitnami/discourse/Chart.yaml

@@ -6,14 +6,14 @@ appVersion: 3.0.3
 dependencies:
   - condition: redis.enabled
     name: redis
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 17.X.X
   - condition: postgresql.enabled
     name: postgresql
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 12.X.X
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -35,4 +35,4 @@ sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/discourse
   - https://github.com/spinnaker
   - https://www.discourse.org/
-version: 10.0.6
+version: 10.1.0

bitnami/discourse/README.md

@@ -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/discourse
+helm install my-release oci://registry-1.docker.io/bitnamicharts/discourse
 ```
 
 ## Introduction
@@ -35,8 +34,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/discourse
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -331,7 +329,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=password \
-    my-repo/discourse
+    oci://registry-1.docker.io/bitnamicharts/discourse
 ```
 
 The above command sets the Discourse administrator account username and password to `admin` and `password` respectively.
@@ -341,7 +339,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 oci://registry-1.docker.io/bitnamicharts/discourse
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -363,7 +361,7 @@ By default, this Chart only deploys a single pod running Discourse. Should you w
 1. Create a conventional release, that will be scaled later:
 
     ```console
-    helm install my-release my-repo/discourse
+    helm install my-release oci://registry-1.docker.io/bitnamicharts/discourse
     ...
     ```
 
@@ -380,7 +378,7 @@ By default, this Chart only deploys a single pod running Discourse. Should you w
 3. 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 oci://registry-1.docker.io/bitnamicharts/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.

bitnami/discourse/templates/NOTES.txt

@@ -57,7 +57,7 @@ This deployment will be incomplete until you configure Discourse with a resolvab
 
 2. Complete your Discourse deployment by running:
 
-    helm upgrade --namespace {{ $releaseNamespace }} {{ .Release.Name }} my-repo/{{ .Chart.Name }} \
+    helm upgrade --namespace {{ $releaseNamespace }} {{ .Release.Name }} oci://registry-1.docker.io/bitnamicharts/{{ .Chart.Name }} \
       {{- if .Values.global }}
       {{- if .Values.global.imagePullSecrets }}
       --set global.imagePullSecrets={{ .Values.global.imagePullSecrets }} \

bitnami/dokuwiki/Chart.lock

@@ -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-18T21:36:49.83497022Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:30:43.222621+02:00"

bitnami/dokuwiki/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 20220731.1.0
 dependencies:
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -26,4 +26,4 @@ name: dokuwiki
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/dokuwiki
   - http://www.dokuwiki.org/
-version: 13.1.21
+version: 13.2.0

bitnami/dokuwiki/README.md

@@ -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/dokuwiki
+helm install my-release oci://registry-1.docker.io/bitnamicharts/dokuwiki
 ```
 
 ## Introduction
@@ -33,8 +32,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/dokuwiki
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -243,7 +241,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
   --set dokuwikiUsername=admin,dokuwikiPassword=password \
-    my-repo/dokuwiki
+    oci://registry-1.docker.io/bitnamicharts/dokuwiki
 ```
 
 The above command sets the DokuWiki administrator account username and password to `admin` and `password` respectively.
@@ -253,7 +251,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 oci://registry-1.docker.io/bitnamicharts/dokuwiki
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)

bitnami/drupal/Chart.lock

@@ -1,9 +1,9 @@
 dependencies:
 - name: mariadb
-  repository: https://charts.bitnami.com/bitnami
-  version: 11.5.5
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 11.5.7
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:98b3e98458c1a31704262285b04d8f546e4a8154f2f6bccdc1b909c9186f336d
-generated: "2023-03-24T16:21:26.737902417Z"
+digest: sha256:d1cd39becdc633408c58a5232dff5560569fa02b67810a916f6b6063aa5a0e96
+generated: "2023-04-20T09:30:48.305064+02:00"

bitnami/drupal/Chart.yaml

@@ -6,10 +6,10 @@ appVersion: 10.0.7
 dependencies:
   - condition: mariadb.enabled
     name: mariadb
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 11.x.x
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -31,4 +31,4 @@ name: drupal
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/drupal
   - https://www.drupal.org/
-version: 13.0.13
+version: 13.1.0

bitnami/drupal/README.md

@@ -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/drupal
+helm install my-release oci://registry-1.docker.io/bitnamicharts/drupal
 ```
 
 ## Introduction
@@ -35,8 +34,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/drupal
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -319,7 +317,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
   --set drupalUsername=admin,drupalPassword=password,mariadb.auth.rootPassword=secretpassword \
-    my-repo/drupal
+    oci://registry-1.docker.io/bitnamicharts/drupal
 ```
 
 The above command sets the Drupal administrator account username and password to `admin` and `password` respectively. Additionally, it sets the MariaDB `root` user password to `secretpassword`.
@@ -329,7 +327,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 oci://registry-1.docker.io/bitnamicharts/drupal
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -380,7 +378,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
 3. 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 oci://registry-1.docker.io/bitnamicharts/drupal
 ```
 
 ### Host path
@@ -396,7 +394,7 @@ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/drupal
 2. 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 oci://registry-1.docker.io/bitnamicharts/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.
@@ -470,13 +468,13 @@ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=dru
 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 oci://registry-1.docker.io/bitnamicharts/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 oci://registry-1.docker.io/bitnamicharts/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:

bitnami/drupal/templates/NOTES.txt

@@ -61,7 +61,7 @@ host. To configure Drupal to use and external database host:
 
   ## PLEASE UPDATE THE EXTERNAL DATABASE CONNECTION PARAMETERS IN THE FOLLOWING COMMAND AS NEEDED ##
 
-  helm upgrade --namespace {{ include "common.names.namespace" . }} {{ .Release.Name }} my-repo/{{ .Chart.Name }} \
+  helm upgrade --namespace {{ include "common.names.namespace" . }} {{ .Release.Name }} oci://registry-1.docker.io/bitnamicharts/{{ .Chart.Name }} \
     --set drupalPassword=$APP_PASSWORD,service.type={{ .Values.service.type }},mariadb.enabled=false{{- if not (empty .Values.externalDatabase.user) }},externalDatabase.user={{ .Values.externalDatabase.user }}{{- end }}{{- if not (empty .Values.externalDatabase.password) }},externalDatabase.password={{ .Values.externalDatabase.password }}{{- end }}{{- if not (empty .Values.externalDatabase.database) }},externalDatabase.database={{ .Values.externalDatabase.database }}{{- end }},externalDatabase.host=YOUR_EXTERNAL_DATABASE_HOST{{- if .Values.global }}{{- if .Values.global.imagePullSecrets }},global.imagePullSecrets={{ .Values.global.imagePullSecrets }}{{- end }}{{- end }}
 
 {{- end }}

bitnami/ejbca/Chart.lock

@@ -1,9 +1,9 @@
 dependencies:
 - name: mariadb
-  repository: https://charts.bitnami.com/bitnami
-  version: 11.5.5
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 11.5.7
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:7e8d5325d3fd53e1f59f23b676e886b7fb11e6c0ab95853b8c3f03521d6386a2
-generated: "2023-04-01T13:00:39.425228584Z"
+digest: sha256:57f65b94e928bdac501e9ac7cef1e507d3d7b672b66d07d43d16c685389d5374
+generated: "2023-04-20T09:30:53.75481+02:00"

bitnami/ejbca/Chart.yaml

@@ -6,12 +6,12 @@ appVersion: 7.11.0
 dependencies:
   - condition: mariadb.enabled
     name: mariadb
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - ejbca-database
     version: 11.x.x
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -30,4 +30,4 @@ name: ejbca
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/ejbca
   - https://www.ejbca.org/
-version: 6.3.17
+version: 6.4.0

bitnami/ejbca/README.md

@@ -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/ejbca
+helm install my-release oci://registry-1.docker.io/bitnamicharts/ejbca
 ```
 
 ## Introduction
@@ -34,8 +33,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/ejbca
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -243,7 +241,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
   --set ejbcaAdminUsername=admin,ejbcaAdminPassword=password,mariadb.auth.password=secretpassword \
-    my-repo/discourse
+    oci://registry-1.docker.io/bitnamicharts/discourse
 ```
 
 The above command sets the EJBCA administrator account username and password to `admin` and `password` respectively. Additionally, it sets the MariaDB `bn_ejbca` user password to `secretpassword`.
@@ -253,7 +251,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 oci://registry-1.docker.io/bitnamicharts/ejbca
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -358,13 +356,13 @@ export MARIADB_PVC=$(kubectl get pvc -l app=mariadb,component=master,release=ejb
 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 oci://registry-1.docker.io/bitnamicharts/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 oci://registry-1.docker.io/bitnamicharts/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:

bitnami/elasticsearch/Chart.lock

@@ -1,9 +1,9 @@
 dependencies:
 - name: kibana
-  repository: https://charts.bitnami.com/bitnami
-  version: 10.2.17
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 10.2.18
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:04254a3f2621a4a60ee3130fad63e7624bfc0442dbdaaa7180f983f8cb15319b
-generated: "2023-04-01T12:57:18.300624603Z"
+digest: sha256:19f2ad778d92aa2f36d1a4c587e87e659454405a7b82acabff55a3aab4d51008
+generated: "2023-04-20T09:30:58.794944+02:00"

bitnami/elasticsearch/Chart.yaml

@@ -6,10 +6,10 @@ appVersion: 8.7.0
 dependencies:
   - condition: global.kibanaEnabled
     name: kibana
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 10.x.x
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -25,4 +25,4 @@ name: elasticsearch
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/elasticsearch
   - https://www.elastic.co/products/elasticsearch
-version: 19.6.1
+version: 19.7.0

bitnami/elasticsearch/README.md

@@ -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/elasticsearch
+helm install my-release oci://registry-1.docker.io/bitnamicharts/elasticsearch
 ```
 
 ## 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/elasticsearch
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -634,7 +632,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
   --set name=my-elastic,client.service.port=8080 \
-  my-repo/elasticsearch
+  oci://registry-1.docker.io/bitnamicharts/elasticsearch
 ```
 
 The above command sets the Elasticsearch cluster name to `my-elastic` and REST port number to `8080`.
@@ -642,7 +640,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 oci://registry-1.docker.io/bitnamicharts/elasticsearch
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml).
@@ -915,7 +913,7 @@ The field `podManagementPolicy` can't be updated in a StatefulSet, so you need t
 
 ```console
 kubectl delete statefulset elasticsearch-master
-helm upgrade <DEPLOYMENT_NAME> my-repo/elasticsearch
+helm upgrade <DEPLOYMENT_NAME> oci://registry-1.docker.io/bitnamicharts/elasticsearch
 ```
 
 ### TO 10.0.0

bitnami/elasticsearch/templates/NOTES.txt

@@ -39,7 +39,7 @@ APP VERSION: {{ .Chart.AppVersion }}
     As an alternative, you can specify "sysctlImage.enabled=true" to use a
     privileged initContainer to change those settings in the Kernel:
 
-      helm upgrade --namespace {{ include "common.names.namespace" . }} {{ .Release.Name }} my-repo/elasticsearch --set sysctlImage.enabled=true
+      helm upgrade --namespace {{ include "common.names.namespace" . }} {{ .Release.Name }} oci://registry-1.docker.io/bitnamicharts/elasticsearch --set sysctlImage.enabled=true
 
     Note that this requires the ability to run privileged containers, which is likely not
     the case on many secure clusters. To cover this use case, you can also set some parameters

bitnami/etcd/Chart.lock

@@ -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-27T20:09:36.556764081Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:31:03.856397+02:00"

bitnami/etcd/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 3.5.8
 dependencies:
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -25,4 +25,4 @@ name: etcd
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/etcd
   - https://coreos.com/etcd/
-version: 8.9.0
+version: 8.10.0

bitnami/etcd/README.md

@@ -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/etcd
+helm install my-release oci://registry-1.docker.io/bitnamicharts/etcd
 ```
 
 ## 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/etcd
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -311,7 +309,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 
 ```console
 helm install my-release \
-  --set auth.rbac.rootPassword=secretpassword my-repo/etcd
+  --set auth.rbac.rootPassword=secretpassword oci://registry-1.docker.io/bitnamicharts/etcd
 ```
 
 The above command sets the etcd `root` account password to `secretpassword`.
@@ -321,7 +319,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 oci://registry-1.docker.io/bitnamicharts/etcd
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -503,7 +501,7 @@ To upgrade from previous charts versions, create a snapshot of the keyspace and
 You can use the command below to upgrade your chart by starting a new cluster using an existing snapshot, available in an existing PVC, to initialize the members:
 
 ```console
-helm install new-release my-repo/etcd \
+helm install new-release oci://registry-1.docker.io/bitnamicharts/etcd \
   --set statefulset.replicaCount=3 \
   --set persistence.enabled=true \
   --set persistence.size=8Gi \

bitnami/external-dns/Chart.lock

@@ -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-08T18:24:22.012878826Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:31:07.732139+02:00"

bitnami/external-dns/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 0.13.4
 dependencies:
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -24,4 +24,4 @@ sources:
   - https://github.com/kubernetes-sigs/external-dns
   - https://github.com/bitnami/containers/tree/main/bitnami/external-dns
   - https://github.com/kubernetes-sigs/external-dns
-version: 6.18.0
+version: 6.19.0

bitnami/external-dns/README.md

@@ -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/external-dns
+helm install my-release oci://registry-1.docker.io/bitnamicharts/external-dns
 ```
 
 ## Introduction
@@ -31,8 +30,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/external-dns
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -348,13 +346,13 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 
 ```console
 helm install my-release \
-  --set provider=aws my-repo/external-dns
+  --set provider=aws oci://registry-1.docker.io/bitnamicharts/external-dns
 ```
 
 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 oci://registry-1.docker.io/bitnamicharts/external-dns
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -402,7 +400,7 @@ helm install my-release \
   --set aws.zoneType=public \
   --set txtOwnerId=HOSTED_ZONE_IDENTIFIER \
   --set domainFilters[0]=HOSTED_ZONE_NAME \
-  my-repo/external-dns
+  oci://registry-1.docker.io/bitnamicharts/external-dns
 ```
 
 ## Troubleshooting
@@ -469,7 +467,7 @@ Use the workaround below to upgrade from versions previous to 1.0.0. The followi
 
 ```console
 kubectl delete deployment my-release-external-dns
-helm upgrade my-release my-repo/external-dns
+helm upgrade my-release oci://registry-1.docker.io/bitnamicharts/external-dns
 ```
 
 Other mayor changes included in this major version are:

bitnami/flink/Chart.lock

@@ -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-04-05T15:08:27.034698506Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:31:11.725452+02:00"

bitnami/flink/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 1.16.1
 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: flink
 sources:
   - https://github.com/apache/flink
   - https://flink.apache.org/
-version: 0.1.2
+version: 0.2.0

bitnami/flink/README.md

@@ -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/flink
+helm install my-release oci://registry-1.docker.io/bitnamicharts/flink
 ```
 
 ## Introduction
@@ -33,8 +32,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/flink
+helm install my-release oci://registry-1.docker.io/bitnamicharts/flink
 ```
 
 These commands deploy flink on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.

bitnami/fluentd/Chart.lock

@@ -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-18T21:55:19.952478988Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:31:15.79128+02:00"

bitnami/fluentd/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 1.16.1
 dependencies:
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -25,4 +25,4 @@ name: fluentd
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/fluentd
   - https://www.fluentd.org/
-version: 5.6.5
+version: 5.7.0

bitnami/fluentd/README.md

@@ -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/fluentd
+helm install my-release oci://registry-1.docker.io/bitnamicharts/fluentd
 ```
 
 ## Introduction
@@ -34,8 +33,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/fluentd
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -333,7 +331,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 
 ```console
 helm install my-release \
-  --set aggregator.port=24444 my-repo/fluentd
+  --set aggregator.port=24444 oci://registry-1.docker.io/bitnamicharts/fluentd
 ```
 
 The above command sets the aggregators to listen on port 24444.
@@ -341,7 +339,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 oci://registry-1.docker.io/bitnamicharts/fluentd
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)

bitnami/flux/Chart.lock

@@ -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-21T18:32:49.039161+01:00"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:31:19.526445+02:00"

bitnami/flux/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 0.36.1
 dependencies:
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -31,4 +31,4 @@ sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/fluxcd-image-automation-controller
   - https://github.com/bitnami/containers/tree/main/bitnami/fluxcd-image-reflector-controller
   - https://github.com/fluxcd
-version: 0.1.2
+version: 0.2.0

bitnami/flux/README.md

@@ -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/flux
+helm install my-release oci://registry-1.docker.io/bitnamicharts/flux
 ```
 
 ## Introduction
@@ -31,7 +30,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm install my-release my-repo/flux
+helm install my-release oci://registry-1.docker.io/bitnamicharts/flux
 ```
 
 The command deploys flux on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.

bitnami/ghost/Chart.lock

@@ -1,9 +1,9 @@
 dependencies:
 - name: mysql
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 9.7.1
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:532f991f5b483c603f31885d358fcc085a77617319b964b330797a2620765547
-generated: "2023-04-14T15:08:45.368319671Z"
+digest: sha256:0763fa7b671765c38ab253bda59673357da64c56261ceda82bcbb097977acbfe
+generated: "2023-04-20T09:31:24.548282+02:00"

bitnami/ghost/Chart.yaml

@@ -6,12 +6,12 @@ appVersion: 5.44.0
 dependencies:
   - condition: mysql.enabled
     name: mysql
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - ghost-database
     version: 9.x.x
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -33,4 +33,4 @@ name: ghost
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/ghost
   - https://www.ghost.org/
-version: 19.1.81
+version: 19.2.0

bitnami/ghost/README.md

@@ -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/ghost
+helm install my-release oci://registry-1.docker.io/bitnamicharts/ghost
 ```
 
 ## Introduction
@@ -35,8 +34,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/ghost
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -289,7 +287,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
   --set ghostUsername=admin,ghostPassword=password,mysql.auth.rootPassword=secretpassword \
-    my-repo/ghost
+    oci://registry-1.docker.io/bitnamicharts/ghost
 ```
 
 The above command sets the Ghost administrator account username and password to `admin` and `password` respectively. Additionally, it sets the MySQL `root` user password to `secretpassword`.
@@ -299,7 +297,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 oci://registry-1.docker.io/bitnamicharts/ghost
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -470,7 +468,7 @@ Delete the Ghost deployment and delete the MariaDB statefulset. Notice the optio
 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 oci://registry-1.docker.io/bitnamicharts/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:

bitnami/ghost/templates/NOTES.txt

@@ -41,14 +41,14 @@ host. To configure Ghost with the URL of your service:
 
 {{- if .Values.mysql.enabled }}
 
-  helm upgrade --namespace {{ .Release.Namespace }} {{ .Release.Name }} my-repo/{{ .Chart.Name }} \
+  helm upgrade --namespace {{ .Release.Namespace }} {{ .Release.Name }} oci://registry-1.docker.io/bitnamicharts/{{ .Chart.Name }} \
     --set service.type={{ .Values.service.type }},ghostHost=$APP_HOST,ghostPassword=$GHOST_PASSWORD,mysql.auth.rootPassword=$MYSQL_ROOT_PASSWORD,mysql.auth.password=$MYSQL_PASSWORD{{- if .Values.global }}{{- if .Values.global.imagePullSecrets }},global.imagePullSecrets={{ .Values.global.imagePullSecrets }}{{- end }}{{- end }}
 
 {{- else }}
 
   ## PLEASE UPDATE THE EXTERNAL DATABASE CONNECTION PARAMETERS IN THE FOLLOWING COMMAND AS NEEDED ##
 
-  helm upgrade --namespace {{ .Release.Namespace }} {{ .Release.Name }} my-repo/{{ .Chart.Name }} \
+  helm upgrade --namespace {{ .Release.Namespace }} {{ .Release.Name }} oci://registry-1.docker.io/bitnamicharts/{{ .Chart.Name }} \
     --set service.type={{ .Values.service.type }},ghostHost=$APP_HOST,ghostPassword=$APP_PASSWORD,{{- if contains "NodePort" .Values.service.type }}service.nodePort=$APP_PORT,{{- end }}mysql.enabled=false{{- if not (empty .Values.externalDatabase.host) }},externalDatabase.host={{ .Values.externalDatabase.host }}{{- end }}{{- if not (empty .Values.externalDatabase.user) }},externalDatabase.user={{ .Values.externalDatabase.user }}{{- end }}{{- if not (empty .Values.externalDatabase.password) }},externalDatabase.password={{ .Values.externalDatabase.password }}{{- end }}{{- if not (empty .Values.externalDatabase.database) }},externalDatabase.database={{ .Values.externalDatabase.database }}{{- end }}
 
 {{- end }}
@@ -128,7 +128,7 @@ host. To configure Ghost to use and external database host:
 
   ## PLEASE UPDATE THE EXTERNAL DATABASE CONNECTION PARAMETERS IN THE FOLLOWING COMMAND AS NEEDED ##
 
-  helm upgrade --namespace {{ .Release.Namespace }} {{ .Release.Name }} my-repo/{{ .Chart.Name }} \
+  helm upgrade --namespace {{ .Release.Namespace }} {{ .Release.Name }} oci://registry-1.docker.io/bitnamicharts/{{ .Chart.Name }} \
     --set ghostPassword=$APP_PASSWORD,ghostHost=$APP_HOST,service.type={{ .Values.service.type }},mysql.enabled=false{{- if not (empty .Values.externalDatabase.user) }},externalDatabase.user={{ .Values.externalDatabase.user }}{{- end }}{{- if not (empty .Values.externalDatabase.password) }},externalDatabase.password={{ .Values.externalDatabase.password }}{{- end }}{{- if not (empty .Values.externalDatabase.database) }},externalDatabase.database={{ .Values.externalDatabase.database }}{{- end }},externalDatabase.host=YOUR_EXTERNAL_DATABASE_HOST
 {{- end }}
 

bitnami/gitea/Chart.lock

@@ -1,9 +1,9 @@
 dependencies:
 - name: postgresql
-  repository: https://charts.bitnami.com/bitnami
-  version: 12.2.7
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 12.2.8
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:aeb8038e211446eb78f1ba2201df69cfa757e67b93009a5304eae5a055f71063
-generated: "2023-04-13T04:30:11.345229135Z"
+digest: sha256:1ffe1f1e1224683ebc96b783957c21afc0480dc0854b57f2859b3a523253427b
+generated: "2023-04-20T09:31:30.23742+02:00"

bitnami/gitea/Chart.yaml

@@ -6,10 +6,10 @@ appVersion: 1.19.1
 dependencies:
   - condition: postgresql.enabled
     name: postgresql
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 12.x.x
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -30,4 +30,4 @@ name: gitea
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/gitea
   - https://gitea.io/
-version: 0.1.19
+version: 0.2.0

bitnami/gitea/README.md

@@ -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/gitea
+helm install my-release oci://registry-1.docker.io/bitnamicharts/gitea
 ```
 
 ## Introduction
@@ -35,8 +34,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/gitea
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -246,7 +244,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
   --set adminUsername=user,giteaPassword=password,postgresql.auth.rootPassword=secretpassword \
-    my-repo/gitea
+    oci://registry-1.docker.io/bitnamicharts/gitea
 ```
 
 The above command sets the Gitea administrator account username and password to `user` and `password` respectively. Additionally, it sets the PostgreSQL `root` user password to `secretpassword`.
@@ -256,7 +254,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 oci://registry-1.docker.io/bitnamicharts/gitea
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -307,7 +305,7 @@ See the [Parameters](#parameters) section to configure the PVC or to disable per
 3. 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 oci://registry-1.docker.io/bitnamicharts/gitea
 ```
 
 ### Host path
@@ -323,7 +321,7 @@ helm install my-release --set persistence.existingClaim=PVC_NAME my-repo/gitea
 2. 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 oci://registry-1.docker.io/bitnamicharts/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.

bitnami/gitea/templates/NOTES.txt

@@ -66,7 +66,7 @@ host. To configure Gitea to use and external database host:
 
   ## PLEASE UPDATE THE EXTERNAL DATABASE CONNECTION PARAMETERS IN THE FOLLOWING COMMAND AS NEEDED ##
 
-  helm upgrade --namespace {{ include "common.names.namespace" . }} {{ .Release.Name }} my-repo/{{ .Chart.Name }} \
+  helm upgrade --namespace {{ include "common.names.namespace" . }} {{ .Release.Name }} oci://registry-1.docker.io/bitnamicharts/{{ .Chart.Name }} \
     --set giteaPassword=$APP_PASSWORD,service.type={{ .Values.service.type }},postgresql.enabled=false{{- if not (empty .Values.externalDatabase.user) }},externalDatabase.user={{ .Values.externalDatabase.user }}{{- end }}{{- if not (empty .Values.externalDatabase.password) }},externalDatabase.password={{ .Values.externalDatabase.password }}{{- end }}{{- if not (empty .Values.externalDatabase.database) }},externalDatabase.database={{ .Values.externalDatabase.database }}{{- end }},externalDatabase.host=YOUR_EXTERNAL_DATABASE_HOST{{- if .Values.global }}{{- if .Values.global.imagePullSecrets }},global.imagePullSecrets={{ .Values.global.imagePullSecrets }}{{- end }}{{- end }}
 
 {{- end }}

bitnami/grafana-loki/Chart.lock

@@ -1,18 +1,18 @@
 dependencies:
 - name: memcached
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 6.3.14
 - name: memcached
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 6.3.14
 - name: memcached
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 6.3.14
 - name: memcached
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 6.3.14
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:6ea0c3fac9016a094bb3f200e9c9ba6c5ce47b4d3b8b7749ab46c515bc5d8fe9
-generated: "2023-04-14T11:38:39.282448532Z"
+digest: sha256:6979c8d1c87bd4d10de37cc592900301a515e32a41087d1f43534464d3760ad4
+generated: "2023-04-20T09:31:40.258569+02:00"

bitnami/grafana-loki/Chart.yaml

@@ -7,25 +7,25 @@ dependencies:
   - alias: memcachedchunks
     condition: memcachedchunks.enabled
     name: memcached
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 6.x.x
   - alias: memcachedfrontend
     condition: memcachedfrontend.enabled
     name: memcached
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 6.x.x
   - alias: memcachedindexqueries
     condition: memcachedindexqueries.enabled
     name: memcached
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 6.x.x
   - alias: memcachedindexwrites
     condition: memcachedindexwrites.enabled
     name: memcached
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 6.x.x
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -44,4 +44,4 @@ name: grafana-loki
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/grafana-loki
   - https://github.com/grafana/loki/
-version: 2.6.3
+version: 2.7.0

bitnami/grafana-loki/README.md

@@ -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/grafana-loki
+helm install my-release oci://registry-1.docker.io/bitnamicharts/grafana-loki
 ```
 
 ## Introduction
@@ -36,8 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/grafana-loki
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -1176,7 +1174,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
   --set loki.traces.jaeger.grpc=true \
-  my-repo/grafana-loki
+  oci://registry-1.docker.io/bitnamicharts/grafana-loki
 ```
 
 The above command enables the Jaeger GRPC traces.
@@ -1184,7 +1182,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 oci://registry-1.docker.io/bitnamicharts/grafana-loki
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)

bitnami/grafana-mimir/Chart.lock

@@ -1,21 +1,21 @@
 dependencies:
 - name: minio
-  repository: https://charts.bitnami.com/bitnami
-  version: 12.2.3
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 12.2.6
 - name: memcached
-  repository: https://charts.bitnami.com/bitnami
-  version: 6.3.13
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 6.3.14
 - name: memcached
-  repository: https://charts.bitnami.com/bitnami
-  version: 6.3.13
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 6.3.14
 - name: memcached
-  repository: https://charts.bitnami.com/bitnami
-  version: 6.3.13
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 6.3.14
 - name: memcached
-  repository: https://charts.bitnami.com/bitnami
-  version: 6.3.13
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 6.3.14
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:92950d7da3fe8ac1f46c534100ce0202574c47eb9c1ac7b994b2b94d2c8490f9
-generated: "2023-04-01T12:55:10.228411305Z"
+digest: sha256:fba5016b975c6da7929afeeadd1bec05734892674e84a14bfdb73961aba1d153
+generated: "2023-04-20T09:31:48.481161+02:00"

bitnami/grafana-mimir/Chart.yaml

@@ -6,30 +6,30 @@ appVersion: 2.7.1
 dependencies:
   - condition: minio.enabled
     name: minio
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 12.x.x
   - alias: memcachedmetadata
     condition: memcachedmetadata.enabled
     name: memcached
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 6.x.x
   - alias: memcachedindex
     condition: memcachedindex.enabled
     name: memcached
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 6.x.x
   - alias: memcachedfrontend
     condition: memcachedfrontend.enabled
     name: memcached
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 6.x.x
   - alias: memcachedchunks
     condition: memcachedchunks.enabled
     name: memcached
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 6.x.x
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -48,4 +48,4 @@ name: grafana-mimir
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/grafana-mimir
   - https://github.com/grafana/mimir
-version: 0.2.3
+version: 0.3.0

bitnami/grafana-mimir/README.md

@@ -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/grafana-mimir
+helm install my-release oci://registry-1.docker.io/bitnamicharts/grafana-mimir
 ```
 
 ## Introduction
@@ -36,7 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm install my-release my-repo/grafana-mimir
+helm install my-release oci://registry-1.docker.io/bitnamicharts/grafana-mimir
 ```
 
 The command deploys grafana-mimir on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
@@ -1226,7 +1225,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
   --set mimir.image.debug=true \
-  my-repo/grafana-mimir
+  oci://registry-1.docker.io/bitnamicharts/grafana-mimir
 ```
 
 The above command enables the debug mode in the image.
@@ -1234,7 +1233,7 @@ The above command enables the debug mode in the image.
 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-mimir
+helm install my-release -f values.yaml oci://registry-1.docker.io/bitnamicharts/grafana-mimir
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml) as starting point.

bitnami/grafana-operator/Chart.lock

@@ -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-14T12:03:01.219615356Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:31:56.0191+02:00"

bitnami/grafana-operator/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 4.10.0
 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: grafana-operator
 sources:
   - https://github.com/grafana-operator/grafana-operator
   - https://github.com/bitnami/containers/tree/main/bitnami/grafana-operator
-version: 2.7.25
+version: 2.8.0

bitnami/grafana-operator/README.md

@@ -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/grafana-operator
+helm install my-release oci://registry-1.docker.io/bitnamicharts/grafana-operator
 ```
 
 ## Introduction
@@ -33,8 +32,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/grafana-operator
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -275,7 +273,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
   --set livenessProbe.successThreshold=5 \
-    my-repo/grafana-operator
+    oci://registry-1.docker.io/bitnamicharts/grafana-operator
 ```
 
 The above command sets the `livenessProbe.successThreshold` to `5`.
@@ -283,7 +281,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 oci://registry-1.docker.io/bitnamicharts/grafana-operator
 ```
 
 ## Configuration and installation details
@@ -313,7 +311,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 oci://registry-1.docker.io/bitnamicharts/grafana-operator
 ```
 
 ### To 2.0.0

bitnami/grafana-tempo/Chart.lock

@@ -1,9 +1,9 @@
 dependencies:
 - name: memcached
-  repository: https://charts.bitnami.com/bitnami
-  version: 6.3.13
+  repository: oci://registry-1.docker.io/bitnamicharts
+  version: 6.3.14
 - name: common
-  repository: https://charts.bitnami.com/bitnami
+  repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.2.4
-digest: sha256:523e61fd07d63703acd40c40225531815a12fce9e4f72fc7e6c0f8405db99ee4
-generated: "2023-04-01T11:11:31.584150877Z"
+digest: sha256:18b000e01ea8f56c008dcdbdae80a886136af5775a677c2a743786687bcdba21
+generated: "2023-04-20T09:32:00.546888+02:00"

bitnami/grafana-tempo/Chart.yaml

@@ -6,10 +6,10 @@ appVersion: 2.0.1
 dependencies:
   - condition: memcached.enabled
     name: memcached
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     version: 6.x.x
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -28,4 +28,4 @@ name: grafana-tempo
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/grafana-tempo
   - https://github.com/grafana/tempo/
-version: 2.1.2
+version: 2.2.0

bitnami/grafana-tempo/README.md

@@ -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/grafana-tempo
+helm install my-release oci://registry-1.docker.io/bitnamicharts/grafana-tempo
 ```
 
 ## Introduction
@@ -36,8 +35,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
 To install the chart with the release name `my-release`:
 
 ```console
-helm repo add my-repo https://charts.bitnami.com/bitnami
-helm install my-release my-repo/grafana-tempo
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -779,7 +777,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 ```console
 helm install my-release \
   --set tempo.traces.jaeger.grpc=true \
-  my-repo/grafana-tempo
+  oci://registry-1.docker.io/bitnamicharts/grafana-tempo
 ```
 
 The above command enables the Jaeger GRPC traces.
@@ -787,7 +785,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 oci://registry-1.docker.io/bitnamicharts/grafana-tempo
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)

bitnami/grafana/Chart.lock

@@ -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-18T22:11:34.949588789Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:31:35.151983+02:00"

bitnami/grafana/Chart.yaml

@@ -5,7 +5,7 @@ apiVersion: v2
 appVersion: 9.4.7
 dependencies:
   - name: common
-    repository: https://charts.bitnami.com/bitnami
+    repository: oci://registry-1.docker.io/bitnamicharts
     tags:
       - bitnami-common
     version: 2.x.x
@@ -24,4 +24,4 @@ name: grafana
 sources:
   - https://github.com/bitnami/containers/tree/main/bitnami/grafana
   - https://grafana.com/
-version: 8.2.33
+version: 8.3.0

bitnami/grafana/README.md

@@ -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/grafana
+helm install my-release oci://registry-1.docker.io/bitnamicharts/grafana
 ```
 
 ## Introduction
@@ -33,8 +32,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/grafana
+helm install my-release oci://registry-1.docker.io/bitnamicharts/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.
@@ -454,7 +452,7 @@ Specify each parameter using the `--set key=value[,key=value]` argument to `helm
 
 ```console
 helm install my-release \
-  --set admin.user=admin-user my-repo/grafana
+  --set admin.user=admin-user oci://registry-1.docker.io/bitnamicharts/grafana
 ```
 
 The above command sets the Grafana admin user to `admin-user`.
@@ -464,7 +462,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 oci://registry-1.docker.io/bitnamicharts/grafana
 ```
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
@@ -626,7 +624,7 @@ Since the volume access mode when persistence is enabled is `ReadWriteOnce` in o
 
 ```console
 kubectl delete deployment <deployment-name>
-helm upgrade <release-name> my-repo/grafana
+helm upgrade <release-name> oci://registry-1.docker.io/bitnamicharts/grafana
 ```
 
 ### To 4.1.0

bitnami/haproxy/Chart.lock

@@ -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-10T16:06:37.183254631Z"
+digest: sha256:829fc25cbbb396161e735c83d152d74a8b3a82d07f08866b885b812d30b920df
+generated: "2023-04-20T09:32:05.14817+02:00"