317d2a8aa8
* Issue #536 - Declarative setup and configuration of ArgoCD * Add missing rules to application-controller role * Fix broken test; update install manifests |
||
|---|---|---|
| .argo-ci | ||
| cmd | ||
| common | ||
| controller | ||
| docs | ||
| errors | ||
| examples/guestbook | ||
| hack | ||
| manifests | ||
| pkg | ||
| reposerver | ||
| server | ||
| test | ||
| util | ||
| workflows | ||
| .codecov.yml | ||
| .dockerignore | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| gometalinter.json | ||
| Gopkg.lock | ||
| Gopkg.toml | ||
| LICENSE | ||
| Makefile | ||
| OWNERS | ||
| Procfile | ||
| README.md | ||
| VERSION | ||
| version.go | ||
Argo CD - Declarative Continuous Delivery for Kubernetes
What is Argo CD?
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes.
Why Argo CD?
Application definitions, configurations, and environments should be declarative and version controlled. Application deployment and lifecycle management should be automated, auditable, and easy to understand.
Getting Started
Follow our getting started guide. Further documentation is provided for additional features.
How it works
Argo CD follows the GitOps pattern of using git repositories as the source of truth for defining the desired application state. Kubernetes manifests can be specified in several ways:
Argo CD automates the deployment of the desired application states in the specified target environments. Application deployments can track updates to branches, tags, or pinned to a specific version of manifests at a git commit. See tracking strategies for additional details about the different tracking strategies available.
For a quick 10 minute overview of Argo CD, check out the demo presented to the Sig Apps community
meeting:
Architecture
Argo CD is implemented as a kubernetes controller which continuously monitors running applications
and compares the current, live state against the desired target state (as specified in the git repo).
A deployed application whose live state deviates from the target state is considered OutOfSync.
Argo CD reports & visualizes the differences, while providing facilities to automatically or
manually sync the live state back to the desired target state. Any modifications made to the desired
target state in the git repo can be automatically applied and reflected in the specified target
environments.
For additional details, see architecture overview.
Features
- Automated deployment of applications to specified target environments
- Flexibility in support for multiple config management tools (Ksonnet, Kustomize, Helm, plain-YAML)
- Continuous monitoring of deployed applications
- Automated or manual syncing of applications to its desired state
- Web and CLI based visualization of applications and differences between live vs. desired state
- Rollback/Roll-anywhere to any application state committed in the git repository
- Health assessment statuses on all components of the application
- SSO Integration (OIDC, OAuth2, LDAP, SAML 2.0, GitLab, Microsoft, LinkedIn)
- Webhook Integration (GitHub, BitBucket, GitLab)
- PreSync, Sync, PostSync hooks to support complex application rollouts (e.g.blue/green & canary upgrades)
- Audit trails for application events and API calls
- Parameter overrides for overriding ksonnet/helm parameters in git
- Service account/access key management for CI pipelines
Development Status
- Argo CD is being used in production to deploy SaaS services at Intuit
Roadmap
- Revamped UI, and feature parity with CLI
- Customizable application actions