Closed emily-zall closed 1 year ago
If you run into this, look at the providerrevision for a useful error message.
emilyzall@Emilys-MBP ~ % kubectl get ProviderRevision
NAME HEALTHY REVISION IMAGE STATE DEP-FOUND DEP-INSTALLED AGE
crossplane-provider-jet-datadog-1f6840e67fd8 Unknown 1 crossplane/provider-jet-datadog:v0.2.0 Active 6h43m
provider-azure-7e21e3395a52 Unknown 1 xpkg.upbound.io/upbound/provider-azure:v0.32.0 Active 10h
upbound-provider-azure-f1082a73e1fb Unknown 1 xpkg.upbound.io/upbound/provider-azure:v0.30.0 Active 7h26m
emilyzall@Emilys-MBP ~ % kubectl describe ProviderRevision provider-azure-7e21e3395a52 | grep Warning
Warning ResolveDependencies 4m42s (x234 over 6h49m) packages/providerrevision.pkg.crossplane.io cannot resolve package dependencies: node already exists
This error message showed me that it was this issue: https://github.com/crossplane/crossplane/issues/3423#issuecomment-1492086179
What happened?
"error: resource mapping not found for name: "datadog-crossplane" namespace: "" from "/Users/emilyzall/repos/config/clusters/test-eu1/applications/crossplane.yaml": no matches for kind "ProviderConfig" in version "datadog.jet.crossplane.io/v1alpha1" when creating ProviderConfig
Provider was installed but healthy is Unknown.
How can we reproduce it?
kubectl apply -f crossplane-datadog-provider-config.txt crossplane-datadog-provider-config.txt
What environment did it happen in?
Crossplane version: v1.12.1 Provider version: v0.2.0 OS: Mac Monterey 12.6.6