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

<@U01GASVESSK> you would need to use the `.get` methods to retrieve them

Thanks for the reply <@UCWG26BH7> , you mean the static `get` method on the `Release` class or separate `get` method on each k8s object that is needed to fetch?

it would need to be on the object itself, there's an example here: <https://github.com/pulumi/examples/blob/cae7d88b705de4334afaff8eda3ee0a5c9b93ffa/kubernetes-ts-helm-release-wordpress/index.ts#L22>

great thanks!

I have this
```const grafanaSvc = k8s.core.v1.Service.get(
  "kps-grafana-svc",
  pulumi.interpolate`${kubePrometheusStack.status.namespace}/${kubePrometheusStack.status.name}-grafana`
);```
so I have to know beforehand that there will be an svc with `-grafana` postfix/suffix created?

…
```k8s.helm.v3.Release.get("test", kubePrometheusStack.id).resourceNames.apply((rn) =&gt; console.log(JSON.stringify(rn)));```
guess this can help somehow, filtering out the resources from the resourceNames object

yes you'd need to know if there was a service object. if this is unwieldy, you might consider switching to `helm.v3.Chart`

I’m actually switching from `helm.v3.Chart` causing some weird issues with deployment/update speed, CRDs and hooks hanging… trying `helm.v3.Release` for the first time, way faster for now.