Elgato_dark/argo-cd
1
0
Fork 0
mirror of https://github.com/argoproj/argo-cd synced 2026-05-24 09:50:08 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3
argo-cd/manifests
History
Alexander Matyushentsev 02624bf3a6
fix: redis timeout should be more than client timeout (#3505)
2020-04-29 08:49:10 +02:00
..
base feat: downgrade dex to 2.22.0 and revert bug workaround (#3468) 2020-04-22 17:34:58 -07:00
cluster-install Switch to kustomize2 as default. Add argocd-ha install manifests (#1169) 2019-02-25 15:25:57 -08:00
cluster-rbac Fix isssue where argocd app set -p required repo privileges. (#1280) 2019-03-18 14:39:32 -07:00
crds feat: support separate Kustomize version per application (#3414) 2020-04-15 12:04:31 -07:00
ha fix: redis timeout should be more than client timeout (#3505) 2020-04-29 08:49:10 +02:00
namespace-install Switch to kustomize2 as default. Add argocd-ha install manifests (#1169) 2019-02-25 15:25:57 -08:00
install.yaml feat: downgrade dex to 2.22.0 and revert bug workaround (#3468) 2020-04-22 17:34:58 -07:00
namespace-install.yaml feat: downgrade dex to 2.22.0 and revert bug workaround (#3468) 2020-04-22 17:34:58 -07:00
README.md Update README.md (#3470) 2020-04-23 07:49:01 -07:00

README.md

Argo CD Installation Manifests

Four sets of installation manifests are provided:

Normal Installation:

  • install.yaml - Standard Argo CD installation with cluster-admin access. Use this manifest set if you plan to use Argo CD to deploy applications in the same cluster that Argo CD runs in (i.e. kubernetes.svc.default). Will still be able to deploy to external clusters with inputted credentials.

  • namespace-install.yaml - Installation of Argo CD which requires only namespace level privileges (does not need cluster roles). Use this manifest set if you do not need Argo CD to deploy applications in the same cluster that Argo CD runs in, and will rely solely on inputted cluster credentials. An example of using this set of manifests is if you run several Argo CD instances for different teams, where each instance will be deploying applications to external clusters. Will still be possible to deploy to the same cluster (kubernetes.svc.default) with inputted credentials (i.e. argocd cluster add <CONTEXT> --in-cluster).

High Availability:

  • ha/install.yaml - the same as install.yaml but with multiple replicas for supported components.

  • ha/namespace-install.yaml - the same as namespace-install.yaml but with multiple replicas for supported components.