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

@busy-umbrella-36067 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.