Jared Watts
Jared Watts
That's a great improvement to the experience and error message @n3wscott, nice work!
From what @haarchri has described so far here, this looks fairly concerning and worth more investigation and a potential fix to backport to a patch release for v1.14.
Were you able to look at the deployments and pods for these providers in the `crossplane-system` namespace? e.g. `kubectl -n crossplane-system describe deployment ` etc.? Curious what could be preventing...
@bobh66 also mentioned in slack that this issue is seen even as far back as v1.16: > We have seen the spinning problem in some of our older 1.16 deployments...
@erhancagirici I think we can call this one done 😉 Major providers have shipped with support for Crossplane v2 and namespaced MRs ✅
I was hoping that the https://github.com/crossplane/crossplane/tree/main/internal/xresource directory could simply be moved to crossplane-runtime by itself, without also having to remove external secret stores at the same time. Is that not...
The desire to execute Function logic during deletion is reasonable, so the custom logic can get a chance to perform clean-up that it may need to do beyond typical k8s...
Just out of curiosity, can you share your use case here for needing the connection details via extra resources? The way I've imagined extra resources so far is as a...