Creating a new DOKubernetesCluster ObserveExternalResource is in endless warning state, and never reports ready

[Nopzen]

Prefacing my bug with, I'm quite new to crossplane, and can only reply back what i experience by running the given examples, as I'm in a discovery face if this tool could fit my needs.

What happened?

After creating a brand new cluster given the examples/kubernetes/k8s-cluster.yaml, the following error keeps persisting even tho there have been no changes to the DOKubernetesCluster resource.

Warning CannotObserveExternalResource 9m6s managed/dokubernetescluster cannot update managed DOKubernetesCluster resource: Operation cannot be fulfilled on dokubernetesclusters.kubernetes.do.crossplane.io "crossplane-managed": the object has been modified; please apply your changes to the latest version and try again

The cluster resources are created in DO and is reachable via kubectl.

How can we reproduce it?

kubectl apply -f https://raw.githubusercontent.com/crossplane-contrib/provider-digitalocean/main/examples/kubernetes/k8s-cluster.yaml

Expected result

No warnings in events when running:

k describe dokubernetesclusters.kubernetes.do.crossplane.io crossplane-managed

Also expected cluster would report READY

$ k get dokubernetesclusters.kubernetes.do.crossplane.io
NAME                 READY   SYNCED
crossplane-managed           True

What environment did it happen in?

Crossplane version: 1.10.1 (latest as of writing)
Kubectl client version: 1.26.0
Kube server version: 1.25.3+k3s1 (crossplane control plane)
Kubernetes distrobution: Rancher k3s

[Nopzen]

To add to this bug I'm seeing that the provider is also hanging i assume in finalizer on deletion of the cluster again, getting the following recurring event:

Normal DeletedExternalResource 23s (x17 over 6m) managed/dokubernetescluster Successfully requested deletion of external resource

I assume this happens because it can't observe the resource in DigitalOcean and then keeps trying to delete something? Not sure if this is related?

The resource is never deleted, and was manually deleted, and the dokubernetescluster resource forcefully removed.

[irizzant]

Hitting the same here

[ADustyOldMuffin]

Can you please also list the version of the provider that you're using?

[irizzant]

I've used this:
kubectl apply -f https://raw.githubusercontent.com/crossplane-contrib/provider-digitalocean/main/examples/provider/install.yaml

which installs 0.1.0, maybe the time has come to update the examples ;)

[mawi001]

I was hitting the same when using the image crossplane/provider-digitalocean:v0.1.0.

Then I tried the latest available pkg image crossplane/provider-digitalocean:v0.2.0-rc.0.44.ga4257b6-main which does seem to update the state.

k get dokubernetesclusters.kubernetes.do.crossplane.io    
NAME      READY   SYNCED
k8s   True    True