GitOps map
App-of-apps hierarchy (from infrastructure Git)
How it is wired
Argo CD uses an app-of-apps pattern: root-app syncs the argocd/ folder; site-apps-manager and lbc-apps-manager deploy leaf Application resources. The diagram is regenerated when the blog image is built from the same Git state as the cluster manifests.
Hierarchy (always up to date with data file)
- root-app (argocd)
- site-apps-manager (sites)
- steba-blog
sites/steba-blogns: steba-blog
- lbc-apps-manager (lbc)
- vault
charts/vaultns: vault
- longhorn
helm chart: longhornns: longhorn-system
- gitlab-runner
helm chart: gitlab-runnerns: gitlab-runner
- it-tools
lbc/it-toolsns: it-tools
- sonarqube
helm chart: sonarqubens: sonarqube
graph TD
argocd_root("root-app / argocd")
argocd_root --> site_apps_manager("site-apps-manager")
site_apps_manager --> steba_blog("steba-blog")
argocd_root --> lbc_apps_manager("lbc-apps-manager")
lbc_apps_manager --> vault("vault")
lbc_apps_manager --> longhorn("longhorn")
lbc_apps_manager --> gitlab_runner("gitlab-runner")
lbc_apps_manager --> it_tools("it-tools")
lbc_apps_manager --> sonarqube("sonarqube")
Could not render the diagram (the list above is still valid). Check the browser console if you need details.
Manifest snapshot 2026-04-27T05:42:25Z — GitOps data from the infrastructure repo at image build time.