fix(nextcloud): Use bitnami legacy as temporary workaround for removal of free images #763

Signed-off-by: Ruben van Dijk <[email protected]>

Author: RubenNL

charts/nextcloud/Chart.yaml

@@ -1,6 +1,6 @@
 apiVersion: v2
 name: nextcloud
-version: 8.0.2
+version: 8.0.3
 # renovate: image=docker.io/library/nextcloud
 appVersion: 31.0.9
 description: A file sharing server that puts the control and security of your own data back into your hands.

charts/nextcloud/values.yaml

@@ -411,6 +411,11 @@ externalDatabase:
     # hostKey: db-hostname-or-ip
     # databaseKey: db-name
 
+global:
+  security:
+    # required for bitnamilegacy repos
+    allowInsecureImages: true
+
 ##
 ## MariaDB chart configuration
 ## ref: https://github.com/bitnami/charts/tree/main/bitnami/mariadb
@@ -421,6 +426,9 @@ mariadb:
   # To use an ALREADY DEPLOYED mariadb database, set this to false and configure the externalDatabase parameters
   enabled: false
 
+  image:
+    repository: bitnamilegacy/mariadb
+
   # see: https://github.com/bitnami/charts/tree/main/bitnami/mariadb#global-parameters
   global:
     # overwrites the primary.persistence.storageClass value
@@ -454,6 +462,8 @@ mariadb:
 ##
 postgresql:
   enabled: false
+  image:
+    repository: bitnamilegacy/postgresql
   global:
     postgresql:
       # global.postgresql.auth overrides postgresql.auth
@@ -506,6 +516,8 @@ externalRedis:
 
 redis:
   enabled: false
+  image:
+    repository: bitnamilegacy/redis
   auth:
     enabled: true
     password: "changeme"