chore: MinIO legacy charts and updated version

Author: dervoeti

docs/modules/trino/pages/usage-guide/fault-tolerant-execution.adoc

@@ -204,7 +204,7 @@ Here's an example of a Trino cluster with fault-tolerant execution enabled using
 [source,bash]
 ----
 stackablectl operator install commons secret listener trino
-helm install minio minio --repo https://charts.bitnami.com/bitnami --version 15.0.7 --set auth.rootUser=minio-access-key --set auth.rootPassword=minio-secret-key --set tls.enabled=true --set tls.existingSecret=minio-tls-certificates --set provisioning.enabled=true --set provisioning.buckets[0].name=trino-exchange-bucket
+helm install minio oci://registry-1.docker.io/bitnamicharts/minio --version 17.0.19 --set auth.rootUser=minio-access-key --set auth.rootPassword=minio-secret-key --set tls.enabled=true --set tls.server.existingSecret=minio-tls-certificates --set tls.existingSecret=minio-tls-certificates --set tls.existingCASecret=minio-tls-certificates --set tls.autoGenerated.enabled=false --set provisioning.enabled=true --set provisioning.buckets[0].name=trino-exchange-bucket --set global.security.allowInsecureImages=true --set image.repository=bitnamilegacy/minio --set clientImage.repository=bitnamilegacy/minio-client --set defaultInitContainers.volumePermissions.image.repository=bitnamilegacy/os-shell --set console.image.repository=bitnamilegacy/minio-object-browser
 ----
 
 [source,yaml]

tests/templates/kuttl/fault-tolerant-execution/01-install-minio.yaml

@@ -5,7 +5,7 @@ commands:
   - script: >-
       helm install minio
       --namespace $NAMESPACE
-      --version 15.0.7
+      --version 17.0.19
       -f 01_helm-bitnami-minio-values.yaml
       oci://registry-1.docker.io/bitnamicharts/minio
     timeout: 240

tests/templates/kuttl/fault-tolerant-execution/01_helm-bitnami-minio-values.yaml

@@ -1,4 +1,21 @@
 ---
+global:
+  security:
+    allowInsecureImages: true
+
+image:
+  repository: bitnamilegacy/minio
+clientImage:
+  repository: bitnamilegacy/minio-client
+defaultInitContainers:
+  volumePermissions: # volumePermissions moved under defaultInitContainers starting with Chart version 17.0.0
+    enabled: false
+    image:
+      repository: bitnamilegacy/os-shell
+console:
+  image:
+    repository: bitnamilegacy/minio-object-browser
+
 mode: standalone
 disableWebUI: false
 extraEnvVars:
@@ -23,8 +40,11 @@ provisioning:
   containerSecurityContext:
     enabled: false
 
+# volumePermissions can be removed starting with Chart version 17.0.0, moved under defaultInitContainers
 volumePermissions:
   enabled: false
+  image:
+    repository: bitnamilegacy/os-shell
 
 podSecurityContext:
   enabled: false
@@ -51,4 +71,9 @@ service:
 
 tls:
   enabled: true
+  autoGenerated:
+    enabled: false
+  existingCASecret: minio-tls-certificates
   existingSecret: minio-tls-certificates
+  server:
+    existingSecret: minio-tls-certificates

tests/templates/kuttl/fault-tolerant-execution/05-run-tests.yaml

@@ -7,7 +7,8 @@ commands:
   # Verify that the exchange bucket contains data
   - script: |
       sleep 10
-      count=$(kubectl exec -n $NAMESPACE deployment/minio -- mc stat local/exchange-bucket | awk '/Objects count:/ {print $3}')
+      kubectl exec -n $NAMESPACE deployment/minio -- mc alias set local https://localhost:9000 minioAccessKey minioSecretKey --api S3v4
+      count=$(kubectl exec -n $NAMESPACE deployment/minio -- mc stat --insecure local/exchange-bucket | awk '/Objects count:/ {print $3}')
       if [ "$count" -gt 0 ]; then
         echo "Objects count is $count (> 0)"
       else