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 keep seeing this during rolling updates of statefulSets, it’s either picking up old data or something else entirely because the containers don’t actually exit with that status code.


```
 ~  kubernetes:apps:StatefulSet XXXXX-01310 updating [diff: ~spec]; warning: 1 Pods failed to run because: [Error] Container completed with exit code 143
```

The pod in question is actually just waiting to pass its `readinessCheck`

<@UD2HJDBCL> Sounds like it could be a bug. Would you mind opening an issue <https://github.com/pulumi/pulumi-kubernetes/issues/new> with more details? It would be helpful to see the full `pulumi up` output, and the relevant code if possible.