late-xylophone-8172707/25/2022, 11:26 AM
. 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
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.
steep-toddler-9409507/25/2022, 10:38 PM
both, Argo and Pulumi are using the annotationsince this is something kubernetes itself adds, not pulumi. And
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