Hi guys Currently we use Pulumi for the deployment directly to the K8S clusters. But we need a more regulated flow and condsider to use the yaml output and decouple the "generate" process (pulumi up) and the deployment itself completly. That would mean that we would use i.e. ArgoCD as the deployment agent on the clusters, triggerd by the changes from the Pulumi Yaml Output. But I think we found there an issue, both, Argo and Pulumi are using the annotation

last-applied-configuration

. So Pulumi will see for every up changes which does not exist. Is it possible to not produce this field at all? I know about the

ignoreChanges

property (https://www.pulumi.com/docs/intro/concepts/resources/options/ignorechanges/) but this produces/writes the field anyway, just skips the diff. Any ideas? Or did I missed something in the docs? Thank you.

I'm a bit confused about

both, Argo and Pulumi are using the annotation

last-applied-configuration

since 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