-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Feature Request: Add support for external ArgoCD Instance #191
Comments
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: