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

Can someone help me understand how k8s managed or k8s injected properties into a deployment or cronjob are handled?

I'm importing some deployments and crojobs and I'm getting diffs on various values that aren't in my source manifest YAML (which I converted to pulumi python).  Some of these are likely the result of manual changes, but some of them are on properties that we for sure wouldn't specify or set, such as restartedAt annotations, dnsPolicy, schedulerName, terminationMessagePath, etc.

Is this only an import issue and if I ignore these during the import, it'll be fine?

Or do I need to do ignore_changes on all of these fields?

sorry if this has been covered before

In my experience you can `ignore_changes` during the import for fields, and then remove the ignore and manage them normally after that.

Just to sure to test the state w/ previews before relying on it :smiley:

That was kind of what I was thinking/hoping was the case.   Thanks

I'm expecting that the pulumi update won't actually remove those fields, its just the preview diff is kind of dumb (in many ways)