5dbbd0a76f
* Add kubeconfig string to ClusterCreateRequest * Update generated files * Copy and adapt cluster management logic into db * Add service account deletion to db * Return errors from new DB methods * Adapt InstallClusterManagerRBAC for db * Update errors in db * Return error if it occurs from db * Integrate code to (un)install cluster manager * Use invalid argument instead of failed precondition * Set bearer token if error is nil * Rm cluster RBAC install from CLI * Rm cluster mgmt install from e2e * Rm common/install.go * Move install components into server/cluster, thanks @jessesuen * Rm unneeded ctx arg * Restore common/installer.go * Replace all quoted percent-s with percent-q * Refactor common/installer.go with error returns * Return errors rather than exiting fatally * Return proper number of args * Slim down cluster methods again * Simplify, simplify, simplify * Return gRPC error if RBAC could not be installed * Issue log entries, not print statements * Fix log import * Update generated files * Refactor * Major cleanup * Unmarshal context now * Put claims check after bearer token insertion * Initial work to use Kubernetes manifest to create a cluster * Pass context name now * Wire up prototype * Add missing parameter for e2e test * Just read file directly * Change how we read cluster server * Support more attributes from localconfig * Update generated files * Support incluster flag * Comment out unused field for now * Rm previous NewCluster function * Unmarshal kube config successfully * Handle insecure clusters, too * Use existing logic to get config, thanks @jessesuen * Revert cluster.go to master version * Update invocations of RBAC installation * Fix e2e invocation * Don't remove management account, thanks @jessesuen * Fix missing error check in e2e test * Fix missing clientset arg in e2e fixture * Create kubeclientset for kubeconfig, thanks @jessesuen |
||
|---|---|---|
| .argo-ci | ||
| cmd | ||
| common | ||
| controller | ||
| docs | ||
| errors | ||
| examples/guestbook | ||
| hack | ||
| manifests | ||
| pkg | ||
| reposerver | ||
| server | ||
| test | ||
| util | ||
| workflows | ||
| .dockerignore | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| Dockerfile-argocd | ||
| Dockerfile-ci-builder | ||
| 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.
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
- 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
Development Status
- Argo CD is being used in production to deploy SaaS services at Intuit
Roadmap
- Auto-sync toggle to directly apply git state changes to live state
- Service account/access key management for CI pipelines
- Support for additional config management tools (Kustomize?)
- Revamped UI, and feature parity with CLI
- Customizable application actions