Ability to wait for ready state of operator related resources.

[dereulenspiegel]

I currently try to deploy istio with the help of istio operator in one of our pulumi stacks. Using pure helm for this is currently in alpha state (from istio side), so not an option for us.
Deploying the operator itself works of course as expected. But when I create the actual istio installation configuration via

const operatorConfig = new k8s.yaml.ConfigGroup('istio-operator-config', {
      yaml: `
      apiVersion: install.istio.io/v1alpha1
      kind: IstioOperator
      metadata:
        namespace: istio-system
        name: istio-controlplane
      spec:
        profile: minimal
  `
    });

I can access the created custom resource via operatorConfig.getCustomResource('install.istio.io/v1alpha1/IstioOperator', 'istio-system/istio-controlplane');, but it seems that pulumi doesn't wait until this resource is in a ready state.
The installation of our ingress solution depends on this service mesh, but is unfortunately executed before istio operator has finished creating the mutating webhook etc. So no sidecars are injected into our nginx pods.
I would like to depend on the custom resource of type install.istio.io/v1alpha1/IstioOperator so that things, that depend on this only get created when the istio installation is finished.
I guess this problem relates to all operator based workflows which seem to become more popular. I am not sure what the optimal or even an acceptable solution from pulumis perspective would be, but since I saw no other issues related to operator based workflows I wanted to raise this.
In the meantime, is there a workaround for this?

Thanks in advance.

[lblackstone]

This is the same underlying issue as #1260