Update Helm release sealed-secrets to v2.19.3

README.md

@@ -48,6 +48,12 @@ Retrieve public/private keys (*store these on a **secure** location!*):
 kubectl get secret -n kube-system -l sealedsecrets.bitnami.com/sealed-secrets-key -o yaml > BitnamiSealedSecrets.masterkey.yml
 ```
 
+Restoring public/private keys:
+```shell
+kubectl apply -f BitnamiSealedSecrets.masterkey.yml
+kubectl rollout restart deployment -n kube-system sealed-secrets-controller
+```
+
 ### 5) Services
 ##### 5.1) [Gitea](https://gitea.io/)    <small>(git repository)</small>
 *Required for all other workloads*  

services/Vaultwarden/deployment-vaultwarden.yaml

@@ -18,8 +18,7 @@ spec:
       serviceAccountName: vaultwarden
       containers:
       - name: vaultwarden
-        # image: vaultwarden/server:1.34.3
-        image: vaultwarden/server:1.36.0
+        image: vaultwarden/server:1.37.0
         env:
         - name: ENABLE_DB_WAL
           value: "false"

system/SealedSecrets/application-sealed-secrets-controller.yaml

@@ -11,9 +11,9 @@ spec:
   syncPolicy:
     automated: {}
   sources:
-  - repoURL: https://bitnami-labs.github.io/sealed-secrets
+  - repoURL: https://bitnami.github.io/sealed-secrets
     chart: sealed-secrets
-    targetRevision: 2.17.7
+    targetRevision: 2.19.3
     helm:
       valueFiles:
       - $values/system/SealedSecrets/values.yaml