As an alternative to the ArgoCD UI, applications also can be deployed via the argocd-cli This folder contains the app-definitions, that are equal to the UI-based creation described in the main-documentation.
Following steps are required to apply them:
argocd login --sso $(kubectl get routes -n argocd -o json | jq -r '.items[0].spec.host')
To have everything running smooth, you should create the applications in the same order as described by the UI-based installation. Use the files in the current folder for that.
argocd app create -f <APPLICATION_YAML>
After all apps are deployed, check there state via:
argocd app list --grpc-web
#expected output:
NAME CLUSTER NAMESPACE PROJECT STATUS HEALTH SYNCPOLICY CONDITIONS REPO PATH TARGET
fiware-mongo-db https://api.fiware-dev-aws.fiware.dev:6443 fiware default Synced Healthy Auto-Prune <none> https://github.com/FIWARE-Ops/fiware-gitops aws/fiware/mongodb HEAD
fiware-orion-ld https://api.fiware-dev-aws.fiware.dev:6443 fiware default Synced Healthy Auto-Prune <none> https://github.com/FIWARE-Ops/fiware-gitops aws/fiware/orion-ld HEAD
fiware-secrets https://api.fiware-dev-aws.fiware.dev:6443 fiware default Synced Healthy Auto-Prune <none> https://github.com/FIWARE-Ops/fiware-gitops aws/fiware/secrets HEAD
namespaces https://api.fiware-dev-aws.fiware.dev:6443 default Synced Healthy Auto <none> https://github.com/FIWARE-Ops/fiware-gitops aws/namespaces HEAD
sealed-secrets https://api.fiware-dev-aws.fiware.dev:6443 sealed-secrets default Synced Healthy Auto-Prune <none> https://github.com/FIWARE-Ops/fiware-gitops aws/sealed-secrets HEAD