update chart dependencies

Author: monotek

zammad/Chart.yaml

@@ -1,6 +1,6 @@
 apiVersion: v2
 name: zammad
-version: 15.2.3
+version: 16.0.0
 appVersion: 6.5.2
 description: Zammad is a web based open source helpdesk/customer support system with many features to manage customer communication via several channels like telephone, facebook, twitter, chat and e-mails.
 home: https://zammad.org
@@ -15,22 +15,22 @@ maintainers:
     email: enjoy@zammad.com
 dependencies:
   - name: elasticsearch
-    repository: https://charts.bitnami.com/bitnami
-    version: 21.6.3
+    repository: oci://registry-1.docker.io/bitnamicharts
+    version: 22.1.6
     condition: zammadConfig.elasticsearch.enabled
   - name: minio
-    version: 14.10.5
-    repository: https://charts.bitnami.com/bitnami
+    version: 17.0.21
+    repository: oci://registry-1.docker.io/bitnamicharts
     condition: zammadConfig.minio.enabled
   - name: memcached
-    version: 7.9.3
-    repository: https://charts.bitnami.com/bitnami
+    version: 8.0.4
+    repository: oci://registry-1.docker.io/bitnamicharts
     condition: zammadConfig.memcached.enabled
   - name: postgresql
-    version: 16.7.21
-    repository: https://charts.bitnami.com/bitnami
+    version: 18.0.8
+    repository: oci://registry-1.docker.io/bitnamicharts
     condition: zammadConfig.postgresql.enabled
   - name: redis
-    version: 20.13.4
-    repository: https://charts.bitnami.com/bitnami
+    version: 23.1.1
+    repository: oci://registry-1.docker.io/bitnamicharts
     condition: zammadConfig.redis.enabled

zammad/ci/full-values.yaml

@@ -688,7 +688,9 @@ elasticsearch:
 memcached:
   # Workaround: switch to bitnami legacy image repository (https://github.com/bitnami/containers/issues/83267)
   image:
-    repository: bitnamilegacy/memcached
+    repository: bitnamisecure/memcached
+    # version: 1.6.39
+    tag: latest@sha256:0eeb6604ad4258924850a38dfcd56697351086ede82e9c7668451c50569548b2
   global:
     security:
       allowInsecureImages: true
@@ -729,7 +731,9 @@ minio:
 postgresql:
   # Workaround: switch to bitnami legacy image repository (https://github.com/bitnami/containers/issues/83267)
   image:
-    repository: bitnamilegacy/postgresql
+    repository: bitnamisecure/postgresql
+    # version: 18.0
+    tag: latest@sha256:e419a8dc57d7e455e181682a51337cef6f828754656ea1d5cebaf8a225f15b55
   global:
     security:
       allowInsecureImages: true
@@ -767,7 +771,9 @@ postgresql:
 redis:
   # Workaround: switch to bitnami legacy image repository (https://github.com/bitnami/containers/issues/83267)
   image:
-    repository: bitnamilegacy/redis
+    repository: bitnamisecure/redis
+    # version: 8.2.2
+    tag: latest@sha256:9a5f3428a3bfcd97eb8647af7f4d0e4c6179f6f9decbd13ed66df832a72233f5
   global:
     security:
       allowInsecureImages: true