Note that applications must be in a single namespace

argoproj / argo-cd

Declarative Continuous Deployment for Kubernetes

https://argo-cd.readthedocs.io

Apache License 2.0

17.78k stars 5.43k forks source link

Note that applications must be in a single namespace #4988

Open jsoref opened 3 years ago

jsoref commented 3 years ago

Checklist:

[x] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
[x] I've included steps to reproduce the bug.
[ ] I've pasted the output of argocd version.

Describe the bug

Multiple users have asked whether it's possible to have argocd applications in other namespaces.

To Reproduce

Watch people ask on Slack
Read https://argoproj.github.io/argo-cd/operator-manual/declarative-setup/#applications

Expected behavior

The declarative setup paragraph should indicate that they're only allowed in a single namespace.
There should be a docs page that talks about applications which points to the config setting to specify which namespace is used by argocd for checking applications.

Screenshots

Version

Logs

jsoref commented 3 years ago

Fwiw, Application is also present here: https://argoproj.github.io/argo-cd/core_concepts/

iam-veeramalla commented 3 years ago

@jsoref Do you think it is a better option to completely rule out argocd watch multiple namespaces. What about a scenario where a cluster-admin wants to manage all the applications in the cluster using a single argocd in the admin namespace(may be argocd namespace).

IMO, if not the whole cluster, many customers might need to monitor couple of namespaces using a single argocd deployment.

What do you think ?

jsoref commented 3 years ago

I think it's important to document applications as they work today.

I use Argo CD to manage a bunch of namespaces and a bunch of things that live in those namespaces. The only things that need to live in one specific namespace are the ArgoCD CRDs.

jessesuen commented 3 years ago

I think it's important to document applications as they work today.

Yes we should document how it works right now.

There is a separate request to watch Applications outside the namespace, but we haven't decided to do that at the moment.

markthebault commented 3 years ago

Hi there is would also be interested in this usecase. We manage customer and it will be nice if they could define their own applications that can be picked up directly with argocd

jsoref commented 3 years ago

@markthebault: this isn't the use droid or use case you're looking for. This is purely a docs bug. If you want to actually change the behavior, that's a bigger feature thing that you should file separately.

blakepettersson commented 1 year ago

This is no longer the case since Apps In Any Namespace