doc: add links to reference material

docs/index.md

@@ -27,4 +27,12 @@ The first are used for the control plane, the other fours are used as worker
 nodes. Some of them are powered with PoE hats. The faster external drives are
 used for longhorn.
 
+## GitOps
+
+Inspired from
+* https://github.com/onedr0p/home-ops
+* https://github.com/bjw-s/home-ops
+* https://github.com/dirtycajunrice/gitops
+* 
+
 --8<-- "includes/abbreviations.md"

docs/monitoring.md

@@ -160,6 +160,13 @@ You can add as a bonus the geoip.
 
 https://www.mostlychris.com/keeping-tabs-on-your-network/
 
+## Loki k8s events
+
+* https://medium.com/@lysetskyyv/collecting-and-visualizing-kubernetes-events-with-loki-and-kubernetes-event-exporter-8f764b78185c
+* https://github.com/resmoio/kubernetes-event-exporter
+* https://grafana.com/docs/agent/latest/flow/reference/components/loki.source.kubernetes_events/
+* 
+
 ## References
 
 [1]: https://medium.com/aeturnuminc/monitoring-stack-deployment-to-a-kubernetes-cluster-prometheus-grafana-alertmanager-loki-dcc7339d4f19

docs/rails-app.md

@@ -5,4 +5,5 @@
 
 some was copied from https://kubernetes-rails.com
 
+https://fly.io/ruby-dispatch/rails-on-docker/
 

docs/vault.md

@@ -124,3 +124,9 @@ type: Opaque
 Instead of environment variables or secrets you can use the vault key reference
 anywhere in resources and the webhook will replace it with the secret.
 
+
+## Monitoring
+
+* https://github.com/hashicorp/vault/issues/13978
+* https://developer.hashicorp.com/vault/tutorials/monitoring/monitor-telemetry-grafana-prometheus
+* https://developer.hashicorp.com/vault/tutorials/monitoring/usage-metrics