init k8s guide

content/posts/13-build-your-own-kubernetes-cluster-part-4/index.md

@@ -771,12 +771,20 @@ resource "kubernetes_manifest" "longhorn_jobs" {
       task        = "backup"
     }
   }
+
+  depends_on = [
+    helm_release.longhorn
+  ]
 }
 
 ```
 
 {{< /highlight >}}
 
+{{< alert >}}
+`depends_on` is required to ensure that Longhorn CRDs is correctly installed before creating jobs when relaunching all terraform project from start.
+{{< /alert >}}
+
 Bam it's done ! After apply, check trough UI under **Recurring Job** menu if backup jobs are created. The `default` group is the default one, which backup all volumes. You can of course set custom groups to specific volumes, allowing very flexible backup strategies.
 
 Thanks to GitOps, the default backup strategy described by `job_backups` is marbled and self-explanatory:
@@ -787,6 +795,16 @@ Thanks to GitOps, the default backup strategy described by `job_backups` is marb
 
 Configure this variable according to your needs.
 
+### DB dumps
+
+If you need some regular dump of your database without requiring Kubernetes `CronJob`, you can simply use following crontab line on control plane node:
+
+```sh
+0 */8   * * *   root    /usr/local/bin/k3s kubectl exec sts/postgresql-primary -n postgres -- /bin/sh -c 'PGUSER="okami" PGPASSWORD="$POSTGRES_PASSWORD" pg_dumpall -c | gzip > /bitnami/postgresql/dump_$(date "+\%H")h.sql.gz'
+```
+
+It will generate 3 daily dumps, one every 8 hours, on the same primary db volume, allowing easy `psql` restore from the same container.
+
 ## 3th check ✅
 
 Persistence is now insured by Longhorn as main resilient storage. And we have production grade DB replicated cluster. It's finally now time to play with all of this by testing some [real world apps]({{< ref "/posts/13-build-your-own-kubernetes-cluster-part-4" >}}) with a proper CD solution.