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

Hi, for no reason I can understand my `pulumi up`  have stopped working. Now a legitimate diff is considered as a conflict... I don’t understand why. Any guess ?

I get
```* the Kubernetes API server reported that "default/private-api" failed to fully initialize or become live: Server-Side Apply field conflict detected```
but the diff is very OK, just changing ID of image in my repo

This may help:
<https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/#handle-field-conflicts-on-existing-resources|https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/#handle-field-confl[…]existing-resources>

<@U05MAUDQPV0> a bugfix was shipped in pulumi-kubernetes 4.5.2 that may address your issue. Could you re-test and let us know?

<@U05QU9RNUN9>, to fix the issue I added in my resources that change on deploy the following annotation :

```                annotations: {
                    '<http://pulumi.com/patchForce|pulumi.com/patchForce>': 'true',
                },```
the first `up`  I did it killed almost everything in the stack using the resources, but after the second one everything was working well

<@U05QU9RNUN9> Should I remove the annotations and try again with 4.5.2 ?