capi2argo-cluster-operator
capi2argo-cluster-operator copied to clipboard
New Feature Request: Add support for external ArgoCD Instance
Currently the ArgoCD secrets are created in the same cluster in argocd-Namespace. If ArgoCD is running in a different environment, supporting API-Calls for cluster register/delete would provide much more flexibility. Configuration could be done via simple configmap for ArgoCD-Endpoint and Secret for credentials.
Added to the roadmap, yet not sure if I would have the time for the next 1-2 months to implement it.
Any chance you would like to contribute to that? :)
If have created a fork and fully switched to external endpoint. But only a basic implementation as reconciling is a bit more difficult.