Closed sboschman closed 2 years ago
@sboschman I've hit the same in another provider https://github.com/kubernetes/kubernetes/issues/97397#issuecomment-1051219217. Resource need to be renamed to something like RancherNamespace
and the problem will go away
What happened?
Created a composition with a namespace.rancher2.rancher.jet.crossplane.io resource. But I am pretty much stuck with the error:
Looking into the namespace.rancher2... resource might give a clue what is happening here:
Allright, let's see:
So... after some digging I found Kubernetes issue 97397. I suspect this is the cause for Crossplane to fail.
How can we reproduce it?
What environment did it happen in?
Crossplane version: 1.8.1 Provider version: 0.1.0