This message was deleted.
# kubernetes
s
This message was deleted.
g
It is of course not expected, but state files can get corrupted. This can happen if there are multiple
pulumi up
operations happening on the same state at the same time (the S3 backend currently cannot protect against this). This can also happen if something interrupts the
pulumi up
such as CTRL+C'ing to cancel it or a network interruption. It can also happen because of a bug in pulumi, but I've not heard of recent cases of this.
If you can share the output of
pulumi preview --diff
and
pulumi refresh
, we might be able to help troubleshoot why this is occurring.