diff --git a/docs/content/guides/kamaji-gitops-flux.md b/docs/content/guides/kamaji-gitops-flux.md
new file mode 100644
index 0000000..1a39100
--- /dev/null
+++ b/docs/content/guides/kamaji-gitops-flux.md
@@ -0,0 +1,73 @@
+# Manage tenant resources GitOps-way from the admin cluster
+
+In this guide we're going to illustrate how to apply applications and resources in general, the GitOps-way, to tenant clusters.
+
+An admin may need to apply specific workload into tenant clusters and ensure is constantly reconciled, no matter what the tenants will do in their clusters.
+
+Example include installing monitoring agents, ensuring specific policies, installing infrastructure operators like Cert Manager and so on.
+
+## Flux as the GitOps operator
+
+As GitOps ensures a constant reconciliation to a Git-versioned desired state, Flux can satisfy the requirement of those scenarios.
+
+In particular, the controllers that reconcile [resources](https://fluxcd.io/flux/concepts/#reconciliation) support communicating to external clusters.
+
+In our scenario the Flux toolkit would run in the *admin cluster*, with reconcile controllers reconciling resources into *tenant clusters*.
+
+<img src="../images/kamaji-flux.png" alt="kamaji-flux" width="720"/>
+
+This is something possible as the Flux reconciliation Custom Resources specifications provide ability to specify `Secret` which contain a `kubeconfig` - here you can find the related documentation for both [`Kustomization`](https://fluxcd.io/flux/components/kustomize/kustomization/#remote-clusters--cluster-api) and [`HelmRelease`](https://fluxcd.io/flux/components/helm/helmreleases/#remote-clusters--cluster-api) CRs.
+
+## Quickstart
+
+As we already know - if not I recommend [this guide](https://kamaji.clastix.io/getting-started/#deploy-tenant-control-plane) - once we deploy a `TenantControlPlane` and it will be ready, we can find the kubeconfig for the admin user in a `Secret` named as *<tenant name>-admin-kubeconfig*, in the same `Namespace` where the resource has been created.
+
+Let's suppose we deploy a `TenantControlPlane` named *tenant1* in the *tenants* `Namespace`, we'd find a `Secret` named *tenant1-admin-kubeconfig* in the *tenants* `Namespace`.
+
+
+```shell
+$ kubectl get tenantcontrolplanes.kamaji.clastix.io -n tenants
+NAME      VERSION   STATUS   CONTROL-PLANE-ENDPOINT   KUBECONFIG                 AGE
+tenant1   v1.25.1   Ready    172.18.0.2:31443         tenant1-admin-kubeconfig   108s
+```
+
+> As the *admin* user has *cluster-admin* `ClusterRole` it will have the necessary privileges to operate on Custom Resources too.
+
+Once we have installed Flux in the *admin cluster* - guide [here](https://fluxcd.io/flux/installation/) - we're ready to ensure resources for specifics tenant clusters.
+
+How to do that? It's simple. We only need to fill the Flux reconciliation resource's `spec.kubeConfig` field.
+
+For example, we might need to ensure [cert-manager](https://cert-manager.io/) is installed into our *tenant1* cluster with Helm. We can do it by declaring an `HelmRelease` as follows:
+
+```yaml
+apiVersion: helm.toolkit.fluxcd.io/v2beta1
+kind: HelmRelease
+metadata:
+  name: tenant1-cert-manager
+  namespace: tenants
+spec:
+  interval: 5m
+  chart:
+    spec:
+      kubeConfig: tenant1-admin-kubeconfig
+      chart: jetstack/cert-manager 
+      version: '4.0.x'
+      sourceRef:
+        kind: HelmRepository
+        name: jetstack
+        namespace: flux-system
+      interval: 1m
+  values:
+    replicaCount: 2
+```
+
+and applying it in the *admin cluster*, alongside the related *jetstack* `HelmRepository`, in the *tenants* `Namespace`.
+
+## Conclusion
+
+This way we can manage all the tenant resources that we want to ensure as admin user from a central pane of glass, from the *admin cluster*.
+
+No matter what the tenant users will do on the *tenant cluster*, the Flux reconciliation controllers wirunning in the *admin cluster* will ensure the desired state declared by the reconciliation resources applied existing in the *admin cluster*, will be reconciled in the *tenant cluster*.
+
+Furthermore, this approach does not need to have in each tenant cluster nor Flux neither applied the related reconciliation Custom Resorces.
+
diff --git a/docs/content/images/kamaji-flux.png b/docs/content/images/kamaji-flux.png
new file mode 100644
index 0000000..d47aa93
Binary files /dev/null and b/docs/content/images/kamaji-flux.png differ