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

I'm a bit confused about
&gt; both, Argo and Pulumi are using the annotation `last-applied-configuration`
since <https://kubernetes.io/docs/tasks/manage-kubernetes-objects/declarative-config/#how-to-create-objects|this is something kubernetes itself adds>, not pulumi.

And `ignoreChanges` IS supposed to skip the specified fields on the update, not just the diff. I suspect that you think it's not doing this because Kubernetes changes the `last-applied-configuration` annotation