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

Hi, any suggestion on this issue? This is a blocker for our EKS deployment: <https://pulumi-community.slack.com/archives/C84L4E3N1/p1564047953142800>

what version of the kubernetes package are you using <@UK987TZEH>

This is a known error in helm that doesn't play well with Pulumi: <https://github.com/helm/charts/tree/master/stable/nginx-ingress#helm-error-when-upgrading-specclusterip-invalid-value->

No matter the value of the defaultBackend or controller service ClusterIp omission value for the chart this doesn't play well with updates 

I hit this the other day and could not get the chart to work

<@UEE5CDE2D> you mean, even Helm errors out in this case?

I switched to a Pulumi nginx to get around this but I couldn't get the chart to work 

<@UEE5CDE2D> I think you mean :facepalmtree:

I've tried playing with the above supposed fix but it doesn't seem to make any difference.

does someone have a good workaround option

it seems like Helm is simply asking for the wrong thing. You can change this field with the `transformations` API that’s in the `ChartOpts`.

but beyond that it’s hard for us to do much better than that, I think

Oh yes, I didn’t think about transformations. I’ll give that a go. Thanks