feat: Add minio and postgres config for Creance

Author: SteffenRathAA

helm/qs-minio/values.yaml

@@ -85,4 +85,22 @@ minio-pharia-finetuning:
     ## @param auth.existingSecretUserKey Key in existing secret containing username
     existingSecretUserKey: "user"
     ## @param auth.existingSecretPasswordKey Key in existing secret containing password
-    existingSecretPasswordKey: "password"
+    existingSecretPasswordKey: "password"
+
+minio-creance:
+  enabled: false
+  fullnameOverride: qs-minio-creance
+  ## @section Bucket provisioning
+  ## @param defaultBuckets Comma, semi-colon or space separated list of buckets to create at initialization
+  ## Format: "bucket-name" or "bucket-name:policy" where policy can be: none, download, upload, or public
+  ## e.g: "my-bucket, my-second-bucket:download, my-public-bucket:public"
+  defaultBuckets: "creance"
+  auth:
+    ## @param auth.existingSecret Name of existing secret containing MinIO credentials
+    existingSecret: "qs-minio-access-creance"
+    ## @param auth.username Username put in existing secret
+    user: "creance"
+    ## @param auth.existingSecretUserKey Key in existing secret containing username
+    existingSecretUserKey: "user"
+    ## @param auth.existingSecretPasswordKey Key in existing secret containing password
+    existingSecretPasswordKey: "password"

helm/qs-postgresql-cluster/values.yaml

@@ -242,6 +242,16 @@ clusterPharia:
         login: true
         superuser: false
         replication: false
+      - name: "creance"
+        connectionLimit: -1
+        ensure: present
+        inherit: true
+        # `password` and `username` key should exist in secret. username key should be the name of the user (mlflow)
+        passwordSecret:
+          name: "qs-postgresql-cluster-access-creance"
+        login: true
+        superuser: false
+        replication: false
   backups:
     # -- You need to configure backups manually, so backups are disabled by default.
     enabled: false
@@ -251,26 +261,26 @@ clusterPharia:
     # If empty or not set, unmapped roles use direct cluster connection
     # If set, unmapped roles will use this pooler
     defaultPooler: "transaction"  # All Pharia roles use transaction pooler by default
-    
+
     # Role-specific pooler mappings (overrides defaultPooler)
     # Maps each role to a specific pooler (optional)
     # Empty means all roles use the default pooler above
     rolePoolerMappings: {}
       # Examples of role-specific overrides:
-      
+
       # Override to use direct connection (bypass pooler)
       # Useful for: admin users, long-running jobs, debugging
       # admin_user: ""
-      
+
       # Override to use a different pooler (if you have multiple)
       # pharia_os: "session"  # Would need session pooler defined
-      
+
       # Real-world example: Admin needs direct access for maintenance
       # pharia_admin: ""
-      
+
       # Real-world example: Background jobs that hold long transactions
       # background_worker: ""
-      
+
       # Note: Most applications should use the default pooler
       # Only override when you have specific requirements
   # -- List of PgBouncer poolers
@@ -369,7 +379,7 @@ clusterTemporal:
     # If empty or not set, unmapped roles use direct cluster connection
     # If set, unmapped roles will use this pooler
     defaultPooler: "session"  # All temporal roles use session pooler by default
-    
+
     # Role-specific pooler mappings (overrides defaultPooler)
     # Maps each role to a specific pooler (optional)
     rolePoolerMappings:

helm/qs-postgresql-db/values.yaml

@@ -375,3 +375,15 @@ databases:
       - pg_stat_statements
       - pg_trgm
       - btree_gin
+
+  - name: "creance"
+    enabled: false
+    cluster: "qs-postgresql-cluster-pharia"
+    owner: "creance"
+    connectionLimit: 50
+    extensions:
+      - uuid-ossp
+      - pgcrypto
+      - pg_stat_statements
+      - pg_trgm
+      - btree_gin