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

You should be able to (1) comment out the resource (2) run pulumi up (3) uncomment (4) and deploy the updated yaml as a workaround

That sounds like a bug in the k8s provider. Can you file an issue with repro steps if possible?

Generally, changes to the YAML file should work as you were expecting.

<@UQMKVR8NP> Thanks mate, that worked. I'll keep that kind of workaround in my head.

<@UE1LN7A22> Sure, I'll try to create a minimal repro th next days and file an issue then. Is this the correct repo to create the issue?<https://github.com/pulumi/pulumi-kubernetes>

<@UE1LN7A22> I tried to create a minimal repro today, but I fail to reproduce the issue. I tried with a simple nginx deployment, but changing the specs there works as expected. Since cert-manager uses its own CRDs, it may be related to those. I will see if I can create a repro for that in the next days. Will let you know then.

Hello <@UE1LN7A22>, was there any fix for this? I’m having the same issue with many Custom Resources. I start seeing it after upgrading my EKS clusters to k8s 1.15.

No, not to my knowledge. I don’t think we ever had a repro case to investigate

Does it help if I send you a verbose log of the issue happening?