some more fixes

infrastructure/gitea/gitea-oauth.sealedsecret.yaml

@@ -0,0 +1,15 @@
+---
+apiVersion: bitnami.com/v1alpha1
+kind: SealedSecret
+metadata:
+  creationTimestamp: null
+  name: gitea-oauth
+  namespace: gitea
+spec:
+  encryptedData: {}
+  template:
+    metadata:
+      creationTimestamp: null
+      name: gitea-oauth
+      namespace: gitea
+    type: Opaque

infrastructure/gitea/gitea.values.yaml

@@ -118,9 +118,9 @@ gitea:
   
   additionalConfigSources:
     - secret:
-      secretName: gitea-oauth
+        secretName: gitea-oauth
   # since we want to reuse the posgres secret, we cannot directly use it here, but instead set the ENV variables
-  additionalConfugFromEnvs:
+  additionalConfigFromEnvs:
     - name: GITEA__DATABASE__DB_TYPE
       value: postgres
     - name: GITEA__DATABASE__HOST
@@ -139,12 +139,12 @@ gitea:
       valueFrom:
         secretKeyRef:
           name: postgres-password
-          key: user
+          key: username
 
 
 postgresql:
   enabled: false
-redis-cluster:
-  enabled: false
 postgresql-ha:
   enabled: false
+redis-cluster:
+  enabled: false

infrastructure/gitea/kustomization.yaml

@@ -8,6 +8,7 @@ resources:
   # gitea values
   - gitea.pvc.yaml
   - gitea.ingress.yaml
+  - gitea-oauth.sealedsecret.yaml
   - gitea.servicemonitor.yaml
   # actions runner values
   - actions.deployment.yaml

infrastructure/pg-ha/README.md

@@ -0,0 +1,3 @@
+# Rebuilding the kluster
+
+When rebuilding the kluster from scratch, the CNPG containers