argo-cd/manifests
34FathomBelow 2260c79d8f
feat: refactor redis-ha NetworkPolicy to include egress rules (#10226)
Signed-off-by: Justin Marquis <34fathombelow@protonmail.com>
2022-08-08 15:04:47 -04:00
..
addons feat: Merge applicationset into argocd (#8864) 2022-03-29 15:11:02 -07:00
base feat: restrict egress onredis (#10227) 2022-08-08 15:03:15 -04:00
cluster-install chore: remove Argo CD CRDs from namespaced install (#6022) 2021-04-13 11:41:44 -07:00
cluster-rbac chore: exclude argocd-server rbac for core-install (#8234) 2022-01-20 16:29:19 -08:00
core-install feat: Merge applicationset into argocd (#8864) 2022-03-29 15:11:02 -07:00
crds feat: ApplicationSet Go template (#10026) 2022-08-08 11:50:53 -04:00
ha feat: refactor redis-ha NetworkPolicy to include egress rules (#10226) 2022-08-08 15:04:47 -04:00
namespace-install chore: remove Argo CD CRDs from namespaced install (#6022) 2021-04-13 11:41:44 -07:00
.gitignore chore: automate bundling argocd addons during release process (#8336) 2022-02-01 17:06:53 -08:00
core-install.yaml feat: restrict egress onredis (#10227) 2022-08-08 15:03:15 -04:00
install.yaml feat: restrict egress onredis (#10227) 2022-08-08 15:03:15 -04:00
namespace-install.yaml feat: restrict egress onredis (#10227) 2022-08-08 15:03:15 -04:00
README.md docs: fix local apiserver host name (#9313) 2022-05-07 21:06:03 +02:00

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.default.svc). 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.default.svc) with inputted credentials (i.e. argocd cluster add <CONTEXT> --in-cluster --namespace <YOUR NAMESPACE>).

    Note: Argo CD CRDs are not included into namespace-install.yaml. and have to be installed separately. The CRD manifests are located in manifests/crds directory. Use the following command to install them:

    kubectl apply -k https://github.com/argoproj/argo-cd/manifests/crds\?ref\=stable
    

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.