Issue connection to provider

crossplane-contrib / provider-civo

Apache License 2.0

22 stars 22 forks source link

Issue connection to provider #18

Open Igor992 opened 2 years ago

Igor992 commented 2 years ago

What happened?

After Nodepools can't created anymore fixed I arrived at a new problem which I start to describe there. So as we agree I moved new topic about this here.

How can we reproduce it?

In my case, I'm using ArgoCD which has deployed Crossplane CRDs and other components via the app of apps scenario (but this can be manual as described here https://www.civo.com/learn/civo-crossplane-provider). I have tested this also manual without using ArgoCD, as described in the content link above.

What environment did it happen in?

Crossplane version: v1.6.1 This provider has tested at local Kind k8s v0.11.1 and k8s server version: v1.21.2

Thanks for check this.

Igor992 commented 2 years ago

Just to ask, does Civo has an API definitions like other providers here - https://doc.crds.dev/ ?

RealHarshThakur commented 2 years ago

Can you perhaps ask for help on Crossplane Slack too? From our side, we satisfy the interface so could be a bug in crossplane runtime(since you've verified it's not a misconfiguration issue). For API definition: seems like the repo isn't indexed yet. We do have the types defined, I am not sure if something needs to be done from our side to let the website pick it up.

Igor992 commented 2 years ago

Hey @RealHarshThakur, I have managed to test this from local Kind custer and it works perfectly. I suppose that my custom XRD and XR was defined wrongly, even if the secret API key was on the cluster. I will dig into this further to understand.

Regarding API definition more can be found here - https://github.com/crossplane/crossplane/blob/master/docs/api-docs/overview.md and this is the main repo - https://github.com/crdsdev/doc

If you want you can close this issue as this is no problem on the Civo side.