You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 29, 2021. It is now read-only.
I think this is a good idea, but there's the chicken and egg problem. The app-of-apps deploys apps in the argocd-apps repo, but if those are apps are in the argocd-apps repo, then what deploys those apps? an app-of-app-of-apps? I think I would like to avoid that. If the problem is needing to touch too many repos, what we can instead do is:
create a new directory at root called app-of-apps so it would look like:
argocd-apps/
- docs/
- envs/
- app-of-apps/ # new dir
|- kustomization.yaml
Now we just put all our app-of-apps in this dir and add it to app-of-apps/kustomization.yaml and remote reference this from the continuous-deployment repo? wdyt?
I wonder, can we move the app of apps to the
argocd-apps
repo? So adding a cluster would be only PRs against 2 repos, instead of 3?Originally posted by @tumido in operate-first/apps#419 (comment)
Right now it's not that straightforward to add a new cluster to ArgoCD. 3 PRs are minimal. If we can remove once step, it would be a huge improvement.
The text was updated successfully, but these errors were encountered: