argo-cd/manifests
May Zhang 0c6644bf8e
fix(notifications): Allow notifications controller to notify on all namespaces (#15702)
* Allow notifications controller to notify on all namespaces

This adds functionality to the notifications controller to be notified
of and send notifications for applications in any namespace. The
namespaces to watch are controlled by the same --application-namespaces
and ARGOCD_APPLICATION_NAMESPACES variables as in the application
controller.

Signed-off-by: Nikolas Skoufis <nskoufis@seek.com.au>

* Add SEEK to users.md

Signed-off-by: Nikolas Skoufis <nskoufis@seek.com.au>

* Remove unused fields

Signed-off-by: Nikolas Skoufis <nskoufis@seek.com.au>

* Revert changes to Procfile

Signed-off-by: Nik Skoufis <n.skoufis@gmail.com>

* Fix unit tests

Signed-off-by: Nikolas Skoufis <nskoufis@seek.com.au>

* - add argocd namespaces environment variable to notifications controller

Signed-off-by: Stewart Thomson <sthomson@wynshop.com>

* - add example cluster role rbac

Signed-off-by: Stewart Thomson <sthomson@wynshop.com>

* - only look for projects in the controller's namespace (argocd by default)

Signed-off-by: Stewart Thomson <sthomson@wynshop.com>

* - update base manifest

Signed-off-by: Stewart Thomson <sthomson@wynshop.com>

* - skip app processing in notification controller

Signed-off-by: Stewart Thomson <sthomson@wynshop.com>

* added unit test and updated doc

Signed-off-by: May Zhang <may_zhang@intuit.com>

* added unit test and updated doc

Signed-off-by: May Zhang <may_zhang@intuit.com>

* updated examples/k8s-rbac/argocd-server-applications/kustomization.yaml's resources

Signed-off-by: May Zhang <may_zhang@intuit.com>

---------

Signed-off-by: Nikolas Skoufis <nskoufis@seek.com.au>
Signed-off-by: Nik Skoufis <n.skoufis@gmail.com>
Signed-off-by: Stewart Thomson <sthomson@wynshop.com>
Signed-off-by: May Zhang <may_zhang@intuit.com>
Co-authored-by: Nikolas Skoufis <nskoufis@seek.com.au>
Co-authored-by: Nik Skoufis <n.skoufis@gmail.com>
Co-authored-by: Stewart Thomson <sthomson@wynshop.com>
2023-10-06 20:25:38 +00:00
..
addons feat: Merge applicationset into argocd (#8864) 2022-03-29 15:11:02 -07:00
base fix(notifications): Allow notifications controller to notify on all namespaces (#15702) 2023-10-06 20:25:38 +00:00
cluster-install chore: remove Argo CD CRDs from namespaced install (#6022) 2021-04-13 11:41:44 -07:00
cluster-rbac fix: extends CR to allow cronjob/workflow triggers (#15300) 2023-09-13 12:01:45 -04:00
core-install feat: Merge applicationset into argocd (#8864) 2022-03-29 15:11:02 -07:00
crds feat(appset): ignoreApplicationDifferences (#9101) (#14743) 2023-09-25 18:45:26 -04:00
ha fix(notifications): Allow notifications controller to notify on all namespaces (#15702) 2023-10-06 20:25:38 +00: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 fix(appset): add option to disable SCM providers entirely (#14246) (#15248) 2023-10-03 22:11:40 +00:00
install.yaml fix(notifications): Allow notifications controller to notify on all namespaces (#15702) 2023-10-06 20:25:38 +00:00
namespace-install.yaml fix(notifications): Allow notifications controller to notify on all namespaces (#15702) 2023-10-06 20:25:38 +00: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.