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

part of it is generated automatically, but this is a bug in the fields that we check to see if a resource needs to be replaced.

<https://github.com/pulumi/pulumi-kubernetes/issues/330>

<@UEFNNMQ2Y> we’ll fix it soon for sure. I’m technically on vacation, usually we try to turn this sort of bug around in a couple hours.

Sorry, i thought change detection was from the Terraform Kubernetes provider or something like that.

Our k8s provider is 100%, artisanal, hand-written kubernetes/client-go code. :slightly_smiling_face:

Great to know! Now i understand why it’s so good :slightly_smiling_face:
Can you help me to figure out where the change detection source code lives in?

<@UEFNNMQ2Y> <https://github.com/pulumi/pulumi-kubernetes/blob/master/pkg/provider/diff.go#L108>

add the missing field there using jsonpath syntax

That’s beatiful. I’m going to create a PR right now :slightly_smiling_face:

Looks like not only `name` and `image` fields are immutable, but any `containers[*]` field. Should i add every single field or the whole `spec.template.spec.containers[*]` rule?`

If every field is immutable, then it seems like the second one should work.

we don’t actually use the wildcard pattern anywhere.

so this is kind of unprecedented. :slightly_smiling_face:

that said, we tend to enumerate every field elsewhere…

I forget the precisely how this works in jsonpath.

Hm, i thought the expression was `[*]` because it’s used here: <https://github.com/pulumi/pulumi-kubernetes/blob/master/pkg/provider/diff.go#L87>

Yep! Looks like it is:
<https://goessner.net/articles/JsonPath/>

Done.
<https://github.com/pulumi/pulumi-kubernetes/pull/331>