An Argo CD app of apps, before and after

Before and after

Before: an Argo CD Application

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: apptique-prod
  namespace: argocd
  labels:
    app.kubernetes.io/name: apptique
    app.kubernetes.io/instance: apptique-prod
    environment: prod
  finalizers:
    - resources-finalizer.argocd.argoproj.io
spec:
  project: default
  source:
    repoURL: https://github.com/confighub/examples.git
    targetRevision: main
    path: gitops/argo/beginner-app-of-apps/manifests/apptique/prod
  destination:
    server: https://kubernetes.default.svc
    namespace: apptique-prod
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
      - CreateNamespace=true

apps/apptique-prod.yaml. You read files like this to work out what each environment runs.

ConfigHub showing the apptique-prod base with its in-cluster variant, and the prod Deployment's settings — After: in ConfigHub

Each app becomes a base and a variant for the cluster it runs on, released and ready.
You can read what prod runs in ConfigHub, here 3 replicas of the frontend.
Argo CD keeps syncing Git until you choose to hand over.

What you work out today, and what happens here instead

Today	Here instead
A root Application makes other Applications, and each one points at a folder in Git.	The root and its Applications stay with Argo CD as the control tree. What each Application deploys is a base in ConfigHub, with a variant for its cluster.
Argo CD syncs whatever is in Git.	Argo CD keeps syncing Git until you run handover.sh, which points each Application at ConfigHub's releases.

ConfigHub keeps configuration as plain objects, with a history of every change. A base holds what every environment shares, and a variant is one environment's copy that stays linked to its base and lists what it changes.

Load it into your ConfigHub

Sign in, then paste the rest. It fetches the example, works out what each environment runs, and saves it in your organization. It touches no cluster, and Argo CD keeps syncing Git until you run handover.sh, the step that moves each Application onto ConfigHub's releases.

$ cub auth login

$ git clone https://github.com/confighub/examples.git && git -C examples checkout 7f1b8f2fc849bb6488bc2c58f1469172018fc9dd

$ cd examples/gitops/argo/beginner-app-of-apps

$ cub argo apply . --out onboard

$ bash onboard/apply.sh

You need a ConfigHub account and cub with the argo plugin and kustomize.

Try it on your laptop

No account needed. This fetches the example and shows what each environment runs. In your own Argo CD repository, run the last line from its root.

$ git clone https://github.com/confighub/examples.git && git -C examples checkout 7f1b8f2fc849bb6488bc2c58f1469172018fc9dd

$ cd examples/gitops/argo/beginner-app-of-apps

$ cub argo plan .

You need cub with the argo plugin and kustomize.

Show me the details (for experienced users)