If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.

Checklist:

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

Describe the bug

AppProject.spec.destinations has the type []ApplicationDestination (https://github.dev/argoproj/argo-cd/blob/49378a95c400a9e535a7178a2a77ba2022a5e084/pkg/apis/application/v1alpha1/types.go#L1639). Aside from declarative configuration there is no other way to use the cluster's name to define an allowed destination in a project. Using the name of the cluster creates a destination with an empty URL, thus not allowing an application to be deployed.

To Reproduce

1. Have an external cluster;
2. Add an AppProject manifest with the cluster's name in destinations;
3. Add an Application manifest in this project with the cluster's name in destination .

Expected behavior

The application should be deployed.

Version

argocd: v2.1.0+d0b2d55
BuildDate: 2021-08-20T05:30:54Z
GitCommit: d0b2d55
GitTreeState: clean
GoVersion: go1.16.5
Compiler: gc
Platform: linux/amd64
argocd-server: v2.1.1+aab9542
BuildDate: 2021-08-25T15:12:04Z
GitCommit: aab9542
GitTreeState: clean
GoVersion: go1.16.5
Compiler: gc
Platform: linux/amd64
Ksonnet Version: v0.13.1
Kustomize Version: v4.2.0 2021-06-30T22:49:26Z
Helm Version: v3.6.0+g7f2df64
Kubectl Version: v0.21.0
Jsonnet Version: v0.17.0