Nic Cope

I like this idea in principle, but it might be a a little difficult to implement. Presumably we do get some benefits from the managed reconciler logic assuming it's reconciling...

iirc ClientApplicator is a struct that embeds the Client and Applicator interfaces, so I usually just write something like: ```go ca := resource.ClientApplicator{ Client: &test.MockClient{ MockGetFn: func(...) error { return...

A related issue: https://github.com/kubernetes-sigs/service-catalog/issues/1411. I strongly recommend clicking through for context - @deads2k (SIG API Machinery chair) explains in more detail how and why ObjectReference is inappropriate.

It seems reasonable to send a Kubernetes event when a resource is ready. I'll see if anyone has bandwidth to take a look at your PR. Thanks!

Thanks for raising this! While I agree it would be technically straightforward to support namespaced managed resources, I'm quite wary to do so primarily out of concern about the cognitive...

> I am on the infrastructure team at my company and we want to offer Azure (AKS in particular) as a service for engineers via crossplane controller. We want to...

I mostly agree with your points. Some notes: > The conversion methods from Crossplane struct to provider API struct. This has to be done in either case. I don't think...

@hasheddan Yeah, I had meant to cross link this issue with Crisscross the other day but couldn't find it. From what I understand Crisscross basically solves this issue.

Related to https://github.com/crossplane/crossplane-runtime/issues/49.

I think in the jet providers this could be in part because we're missing a layer of rate limiting. Most Crossplane providers use a rate limiter that applies exponential backoff...