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 think this turned out to still happen when pulumi was “removing” the replica count from the deployment. Further deployments with the replica count removed doesn’t cause this.

you can set ignoreChanges in the pulumi customresourceoptions

```new x(name, { opts }, { ignoreChanges: 'spec.template.replicas' });```

yeah, it’s just strange that this happens in the first place. it’s like pulumi completely takes over the replica sets to do it’s own thing. When applying raw yaml with this field set to `1`, this behavior isn’t experienced.