Unable to install pull integration for pre-existing ArgoCD installation #125
Description
Describe the bug
The current helm chart will always attempt to install a namespace for ArgoCD, and then use a CR to install ArgoCD itself. This does not support using the integration with a pre-existing ArgoCD, such as the one we use in our environment which is installed by Terraform.
To Reproduce
Steps to reproduce the behavior:
- Install ArgoCD
- Run
helm install argocd-agent-addon ocm/argocd-agent-addon(or do helm install by Terraform, in our case) - Receive errors that the namespace resource already exists, and that helm does not own it.
Working-around the helm ownership error by adding labels/annotations to the argocd namespace allows installation to complete, but with newly-installed argocd components which are not desired.
Expected behavior
We wish to be able to install this integration and have it work against ArgoCD which has already been installed on the hub, and already installed spokes. The integration (or its helm chart) should not expect to own/managed ArgoCD itself.
Environment ie: Kubernetes version:
In our case, k8s 1.23 on EKS. This should apply to any k8s version.
Additional context
As discussed with @mikeshng on Slack.