I d like to +1 to this issue it s now blocking a lot of our

Question

I d like to +1 to this issue it s now blocking a lot of our infrastructure creation with EKS <https github com pulumi pulumi kubernetes issues 456>

creamy-potato-29402 · Answer

< early musician 41645> I thought we fixed this let me see what s up

creamy-potato-29402 · Answer

< early musician 41645> This seems like it should be fixed with

creamy-potato-29402 · Answer

What version are you running

damp-book-35965 · Answer

Yeah I think we are running 0 21

creamy-potato-29402 · Answer

< damp book 35965> < early musician 41645> I ll try to reproduce the issue and the get something working

gorgeous-egg-16927 · Answer

< early musician 41645> < damp book 35965> I updated the issue It looks like the issue was due to helm configuration and not on our end Let me know if you re still having problems

damp-book-35965 · Answer

Got it thanks That solves the issue at hand but we need the CRD s for the helm chart to operate properly

damp-book-35965 · Answer

Thanks anyway < gorgeous egg 16927>

gorgeous-egg-16927 · Answer

< damp book 35965> IIUC the operator will create the CRDs the problem is that helm was also trying to create them

gorgeous-egg-16927 · Answer

i e pulumi was failing because the prometheus operator was creating the CRDs out of band

damp-book-35965 · Answer

Yup I understood that I think we will have to turn the option of here and use another chart to create the CRDs with dependsOn in pulumi

damp-book-35965 · Answer

Thanks for looking into it

creamy-potato-29402 · Answer

I don t think I understand it should all just work if you turn the option off no

damp-book-35965 · Answer

Nope this will work but then CRD s need to be present in the cluster beforehand somehow

creamy-potato-29402 · Answer

The operator creates them no

damp-book-35965 · Answer

If I set createCustomResource to false then no

creamy-potato-29402 · Answer

I could be misunderstanding but isn t that instructing the Helm Chart to not create them

creamy-potato-29402 · Answer

The operator still should right

creamy-potato-29402 · Answer

oh perhaps you are right

creamy-potato-29402 · Answer

YOu don t need a chart right Just use `k8s yaml ConfigFile` pointed at these URLs ``` ```

damp-book-35965 · Answer

So as part of the helm chart it does the crd installs also which is breaking

creamy-potato-29402 · Answer

I m not sure what you mean But < gorgeous egg 16927> tells me that I was right `createCustomResource` only stops the Chart from creating the CRDs The operator will still do it

creamy-potato-29402 · Answer

Is that right < gorgeous egg 16927>

gorgeous-egg-16927 · Answer

Yes just confirmed You can check the prometheus operator pod logs to confirm

damp-book-35965 · Answer

Not sure how the operator creates the CRDs

damp-book-35965 · Answer

Then why does the option even exist it s redundant

gorgeous-egg-16927 · Answer

the helm chart creates the operator deployment which creates a pod which creates the 4 CRDs

creamy-potato-29402 · Answer

<https github com helm charts tree master stable prometheus operator helm fails to create crds> this explains it

creamy-potato-29402 · Answer

but this is kind of what operators do so it s not super surprising to me

gorgeous-egg-16927 · Answer

note also that deleting the helm chart leaves the CRDs around it seems pretty backwards to me

damp-book-35965 · Answer

Yes

damp-book-35965 · Answer

It s not a pulumi problem for sure

creamy-potato-29402 · Answer

Helm does not really have a robust notion of lifecycles That s not surprising either

gorgeous-egg-16927 · Answer

this is why we only recommend using helm as a migration path not as the end goal

damp-book-35965 · Answer

Alright

silly-solstice-73282 · Answer

< early musician 41645> is always causing problems hi there smile