-
Notifications
You must be signed in to change notification settings - Fork 32
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
Connect or register Civo created cluster in ArgoCD #18
Comments
First you would create a cluster in Then you'd create a project, for example: https://github.com/crossplane-contrib/provider-argocd/blob/main/examples/projects/project.yaml. Within the From what I understand |
@janwillies sorry to pick your time. I found your repo https://github.com/janwillies/crossargo-sync and wanna know, if this repo could be modified in a way, that other providers can use them (eg. civo-provider) (https://github.com/crossplane-contrib/provider-civo) ? Filling this gap would be a big value for the crossplane/argocd community, because we can practice a more complete and automated Gitops. |
I think it would be better to support this in Closing this as duplicate |
Thank you guys for getting me on the right track! If anybody is wondering, what @janwillies meant with #18 (comment), I wrote a comprehensive answer on stackoverflow about the concrete steps to connect ArgoCD with Crossplane created clusters. Just a side note: you only need the argocd-provider |
I have a cluster which is created by Crossplane through the Civo provider.
That process created a secret containing the
kubeconfig
.Normally, I manually add the IP address to the ArgoCD
AppProject
if the cluster creation process has finished. Then I manually change all manifests which are using this server address. In an issue I raised here: argoproj/argo-cd#8107 (comment) they mentioned, that I can use a "string reference" of my cluster, (they pointed me there: https://doc.crds.dev/github.com/crossplane-contrib/provider-argocd/projects.argocd.crossplane.io/Project/v1alpha1@v0.1.0#spec-forProvider-destinations )but I have no idea to do that. I simply didn't get it,...
That is my current state:
appProject
How can I bridge the gap between my Crossplane created cluster and ArgoCD
Application
deployments without manual intervention? Isn't your repo's intention to exactly do that? I didn't found any example which makes sense for me to get that working.What I found is, that I can create a
secret
to register my cluster (if I am not completely misunderstand):Am I right, that my demands are not possible to achieve automatically at the moment? If not, who is "responsible" to create that? CivoProvider? provider-argocd? argocd itself?
It would be awesome if someone can get me out of that configuration hell 😈
The text was updated successfully, but these errors were encountered: