Content tagged with "argocd"
Git Directory Generator auto-creates dev/staging/prod Applications from directory structure. Adding an environment is just a directory push, and per-environment changes don't affect others. Watch out for the longer polling interval.
Just one IAM policy addition to the Capability Role enables CodeCommit private repo deployments. Watch out: URL typos and missing permissions produce the same error, and manual refresh is recommended after fixing permissions.
Create an ArgoCD Capability using eksctl's declarative YAML config and deploy a sample app. Covers the differences from AWS CLI and CloudFormation behavior.
Enable ArgoCD Capability on EKS via AWS CLI and deploy a sample app end-to-end. Covers real gotchas like Identity Center region mismatch and access policy setup.
Adding a new directory to a Git Directory Generator-based ApplicationSet took about 8 minutes to auto-generate the Application. Use hard refresh for existing Applications or webhooks for faster feedback.
After fixing an IAM policy, ArgoCD's error backoff delays automatic retry. The argocd.argoproj.io/refresh=hard annotation triggers an immediate retry.
When the IAM policy is scoped to a specific repository ARN, accessing a non-existent repo returns AccessDeniedException, not 'repository not found'. Compare the IAM Resource ARN with the repoURL to debug.
kubectl delete application removes the CR but leaves Pods and Services running. Add resources-finalizer.argocd.argoproj.io for cascade deletion.