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

This should be resolved with the v4.5.4 release of pulumi kubernetes, can you check your version please

```❯ go list -m all | grep pulumi-kubernetes/sdk
<http://github.com/pulumi/pulumi-kubernetes/sdk/v3|github.com/pulumi/pulumi-kubernetes/sdk/v3> v3.30.2
<http://github.com/pulumi/pulumi-kubernetes/sdk/v4|github.com/pulumi/pulumi-kubernetes/sdk/v4> v4.5.5```
I updated the pulumi-kubernetes package to 4.5.5 but it seems `<http://github.com/pulumi/pulumi-kubernetes-cert-manager|github.com/pulumi/pulumi-kubernetes-cert-manager> v0.0.5` is using 3.30.2

That's odd. The error you're seeing is a regression in 4.5.0.
I'm not familiar enough with the golang systems to help on that. 

I've always implemented cert-manager without the provided component resource, you could take a look at the code for how to do it yourself. It should just be the helm release + YamlFile resources

I might end up doing just that. Thanks for responding on this though :slightly_smiling_face:

I had this issue a couple weeks ago and a pulumi upgrade fixed it

Already using latest version for that though: `<http://github.com/pulumi/pulumi/sdk/v3|github.com/pulumi/pulumi/sdk/v3> v3.94.2`

Is there a difference between NewChart and NewRelease, or do we need to use them together in some way?

<https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/release/>
<https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/chart/>

To me it looks like both installs a helm chart, or am I wrong?

Release will use `helm install` internally, so everything is managed by helm.
Chart will use `helm template`, then pulumi will load the resources into the stack.

Worth reading this:
<https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/choosing-the-right-helm-resource-for-your-use-case/|https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/choosing-the-right-helm-resource-for-your-use-case/>

For now we did yaml.NewConfigFile and fetch the crd and put a pulumi.DependsOn on the configfile at the end of the call to NewChart. Seems to work.

Yep this is the recommended way for cert-manager. It's a relatively simple chart, so Chart and Release can be used interchangeably here.

is that better to use then this? `k8s.yaml.ConfigFile`

<@U060XTPL0RH> it's the same thing, just named differently in the go-sdk

<@U04D2DBKUF9> thank you for the link to the article above.