The argocd-update step asks Argo CD to reconcile an Application after promotion changes reach Git. It can trigger an immediate sync and check Application health; unlike Kargo’s Git-based steps, it is specific to Argo CD. section 3.2.3 section 3.5
If a Promotion succeeds but the cluster does not change, check:
- That the Application exists and its name exactly matches the name configured in the step; a mismatch can leave Argo CD unnotified. section 3.6.3
- That Argo CD can access the GitOps repository if the Application exists but remains OutOfSync. section 3.6.3
Dev promotion
A dev Promotion clones the GitOps repository, updates the image tag, commits and pushes the change, then runs argocd-update for demo-dev. The Git commit records the desired state; the final step prompts Argo CD to reconcile it. section 3.2.3 section 3.5.7
Listing 3.16 Argo CD Applications for dev, staging, and prod
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: demo-dev
namespace: argocd # #1
annotations:
kargo.akuity.io/authorized-stage: demo:dev # #2
labels:
kargo.akuity.io/project: demo # #3
spec:
project: default
source:
repoURL: https://github.com/<your-github-username>/demo-gitops.git # #4
targetRevision: main
path: envs/dev # #5
destination:
server: https://kubernetes.default.svc
namespace: demo-dev
syncPolicy:
automated: # #6
prune: true
selfHeal: true
syncOptions:
- CreateNamespace=true
The Application manifest shows the authorized-stage annotation that permits a Stage to trigger syncs, alongside the repository path Argo CD reconciles. section 3.5.3
