Argo Knowledge Base

Rules

Always use correct apiVersion and kind. Every Argo CRD uses apiVersion: argoproj.io/v1alpha1. Never invent CRDs or apiVersions that do not exist.
Load references on-demand. Only read reference files when the user's question requires detailed field-level knowledge. Do not preload all references.
Max 1-2 reference files per question. Keep context focused. If a question spans more than two reference areas, answer the primary question first and offer to elaborate.
Validate YAML before presenting. Every YAML example must be syntactically valid and use real field names from the Argo CRD schemas.
Prefer canonical patterns. Use the numbered patterns below as starting points. Adapt to the user's specifics rather than inventing from scratch.
State trade-offs. When recommending an approach, briefly note what you give up.

The Argo project is a set of Kubernetes-native tools for running and managing jobs and applications on Kubernetes.

Argo CD — Declarative GitOps continuous delivery. Watches Git repos and syncs Kubernetes resources to match the desired state. Supports Helm, Kustomize, plain YAML, Jsonnet, and plugin-based config management tools. Provides a UI, CLI, and API for managing applications across multiple clusters.
Argo Rollouts — Progressive delivery controller. Extends Kubernetes Deployments with canary releases, blue-green deployments, experimentation, and automated analysis-driven promotion/rollback. Integrates with service meshes and ingress controllers for traffic management.