No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Greetings. Is there a way to wait for `k8s.helm.v3.Release` to fully install all its resources to get a reference to a resource created by the helm release?
What I’m trying to achieve is install an `istio/gateway` helm release and get the k8s Service it creates, to get the Service’s external IP.
I’m getting the resource like this: `const gatewayService = k8s.core.v1.Service.get("istio-gateway-service", pulumi.interpolate`${gateway.namespace}/${gateway.name}`, { dependsOn: [gateway] });`
but it fails with `error: Preview failed: resource 'istio-system/istio-ingressgateway' does not exist` and that’s pretty obvious, why would it exist during the preview, when the release is not installed at all?

this should not fail, can you share your whole code?

see this example:
<https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/release/#query-kubernetes-resource-installed-by-helm-chart>

The thing is that code works perfectly fine if I comment out the `Service.get` , run `pulumi up` , then return the `Service.get`  and run `pulumi up` again. But I’d like not to do that for every stack.

Sure, here is the code:
```const gateway = new k8s.helm.v3.Release('istio-gateway', {
    name: 'istio-ingressgateway',
    chart: 'gateway',
    createNamespace: true,
    namespace: 'istio-system',
    forceUpdate: true,
    repositoryOpts: {
      repo: '<https://istio-release.storage.googleapis.com/charts>',
    },
    values: {
      labels: {
        app: 'istio-ingressgateway',
        istio: 'ingressgateway',
      },
    },
  }, {
    provider,
    dependsOn: [istiod],
  });

  const gatewayService = k8s.core.v1.Service.get("istio-gateway-service", pulumi.interpolate`${gateway.namespace}/${gateway.name}`, { dependsOn: [gateway] });
  const clusterIp = gatewayService.status.loadBalancer.ingress[0].ip;```

looks pretty similar to the example you’ve mentioned

if you do `kubectl get svc` on the `istio-system` namespace, what is returned?

ohh, i see. the trick is it should be  `pulumi.interpolate`${gateway.status.namespace}/${gateway.status.name}`

ah yeah that’ll do it, the outputs don’t resolve until status is there