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

deployment: <https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/kubernetes/apps/v1/#Deployment>, status: <https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/kubernetes/apps/v1/#Deployment>

Pulumi automatically waits for k8s resources to be ready, so you shouldn’t have to check the status manually.

This thread has an example of depending on resources created as part of a helm chart: <https://pulumi-community.slack.com/archives/C84L4E3N1/p1571331362260000>

<@UE1LN7A22> thanks! I give that a whirl. Also do you know is there a better way to debug things like this. Running pulumi up can take a minute or two between changes

I’m not sure I completely understand your question, but I think you might be confused about how to use Input/Output types. <https://www.pulumi.com/docs/intro/concepts/programming-model/#outputs> should help there.

In your specific example, you should be able to do something like:
```deployment.apply(k =&gt; { console.log(Object.getOwnPropertyNames(k)) })
```

The return value of an `apply` is an Output, but it’s unwrapped/resolved within the function inside of `apply()`