in messing with the new helm release functionality i would l

Question

in messing with the new helm release functionality i would like to know if there is a way to get the rendered yaml before it is deployed like a noop run to debug issues like ```Previewing update ipd eks use1 sfx Type Name Plan Info + pulumi pulumi Stack pulumi test ipd eks use1 sfx create 1 message + pulumi providers kubernetes k8s provider create kubernetes signalfx agent 1 error Diagnostics kubernetes signalfx agent error Object Kind is missing in null ```

purple-plumber-90981 · Answer

the associated code simplified for readability ```helm signalfx = k8s helm v3 Release signalfx agent args=k8s helm v3 ReleaseArgs chart= signalfx agent repository opts=k8s helm v3 RepositoryOptsArgs repo= <https dl signalfx com helm repo> name= signalfx agent namespace= observability values= clusterName pulumi stack info name timeout=600 version= 1 9 2 opts=pulumi ResourceOptions provider=k8s provider ```

prehistoric-translator-89978 · Answer

I don t think you can do that <https github com pulumi pulumi kubernetes issues 1327>

purple-plumber-90981 · Answer

yeah so trying to leverage the `enable dry run` or the `render yaml to directory` on the provider seems ineffectual

purple-plumber-90981 · Answer

`<https www pulumi com docs reference pkg kubernetes provider >` describes both of these features as `BETA FEATURE` do i need to do something at a config level to ensure beta features are used

prehistoric-translator-89978 · Answer

The issue is that render to yaml is a provider itself so you would have to do `provider = Provider yaml render yaml to directory = yaml ` so that will delete your existing stack but you ll get yaml files slightly smiling face

purple-plumber-90981 · Answer

ok ill give that a go

purple-plumber-90981 · Answer

doesnt seem to do anything

purple-plumber-90981 · Answer

im using ```render provider = k8s Provider render provider render yaml to directory= yaml ```

purple-plumber-90981 · Answer

same code i show above but pointing to render provider

purple-plumber-90981 · Answer

ie ```opts=pulumi ResourceOptions provider=render provider ```

prehistoric-translator-89978 · Answer

Yeah that s what I do So it didn t create a directory called `yaml`and rendered the files in there

prehistoric-translator-89978 · Answer

Oh you need to replace ` render provider ` with ` yaml `

purple-plumber-90981 · Answer

its not a label

purple-plumber-90981 · Answer

we are seeing ```I0917 13 25 01 428923 33851 provider plugin go 569 Provider kubernetes 0xc000b24120 Check urn pulumi ipd eks use1 sfx pulumi test kubernetes he <http lm sh v3 Release signalfx agent|lm sh v3 Release signalfx agent> failed err=Object Kind is missing in null ```

purple-plumber-90981 · Answer

in the debug logging

purple-plumber-90981 · Answer

ok im trying ```render provider = k8s Provider yaml render yaml to directory= yaml ```

purple-plumber-90981 · Answer

it is not creating a directory or populating said rectory with any yaml

sparse-park-68967 · Answer

So this is the same issue as <https github com pulumi pulumi kubernetes issues 1715> I have a fix which should release tomorrow

sparse-park-68967 · Answer

for debugging yes we aren t yet supporting the render to yaml directory flag yet for helm release Cut <https github com pulumi pulumi kubernetes issues 1716> to track that

sparse-park-68967 · Answer

To debug you could also just run `helm template` on the CLI with the provided values In this case you will find there are some empty templates being rendered which the provider doesn t handle well will be fixed tomorrow

sparse-park-68967 · Answer

Thanks for your patience

purple-plumber-90981 · Answer

thanks < sparse park 68967> we will try again on our Monday and see if problem is gone

sparse-park-68967 · Answer

please do I will update this thread when the release is cut tomorrow

sparse-park-68967 · Answer

< purple plumber 90981> v3 7 2 has just been cut and should fix this and another couple of problems with the helm release resource

purple-plumber-90981 · Answer

hey so one other thing I noticed < sparse park 68967> namespace=mynamespace id is not lifting properly is that fixed also

sparse-park-68967 · Answer

You mean setting the namespace of the release

purple-plumber-90981 · Answer

else implicitly dependency on namespace is broken

purple-plumber-90981 · Answer

referencing namespace object by id

sparse-park-68967 · Answer

it should work do you have some code to point me at

purple-plumber-90981 · Answer

not currently on chairlift at snow will drop you some code Monday but easy to replicate make a namespace and then a release in your release reference namespace=newnamespace id

purple-plumber-90981 · Answer

it should lift and create a dependency it fails with must be a string

purple-plumber-90981 · Answer

IE does not allow pulumi namespace resource output as the release namespace parameter input

sparse-park-68967 · Answer

Pretty sure that works Will point you at an example

sparse-park-68967 · Answer

We can sync up monday if I am mistaken

sparse-park-68967 · Answer

Enjoy the snow

sparse-park-68967 · Answer

Sorry to ping again but this is the example we covered in the blog post <https www pulumi com blog full access to helm features through new helm release resource for kubernetes how do i use it> which definitely works as expected Lets sync up monday if you are seeing issues still