diff --git a/docs/src/concepts/gitops.md b/docs/src/concepts/gitops.md
index 992f8e4a1d09e24068e35601ae6253ca675f73da..ef0f6eb2b42a903049dea2ad12db4dcb732a8eb7 100644
--- a/docs/src/concepts/gitops.md
+++ b/docs/src/concepts/gitops.md
@@ -4,6 +4,8 @@ The Shivering-Isles Infrastructure uses GitOps as central concept to maintain th
 
 The current tool of choice to implement GitOps in the Shivering-Isles Infrastructure is [FluxCD](https://fluxcd.io/) in combination with a monorepo.
 
+<iframe width="100%" height="480" src="https://www.youtube-nocookie.com/embed/lI03nh0EmaQ" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
+
 ## GitOps Security
 
 To secure GitOps based deployments and reduce the risks of compromise, the GitOps deployment in the Shivering-Isles Infrastructure only accepts signed commits. This prevents a deployment of workload if an attackers mananges to push a commit onto the GitOps repository. The git forge itself is in charge of preventing rollbacks in the commit history. Rollbacks could be prevented by using git tags instead of git branches as reference, but are less practical.