Does Pulumi currently not support StatefulSets with the OnDelete update strategy? My observations: 1. When updating a StatefulSet using the OnDelete strategy, Pulumi will (erroneously?) wait on

Waiting for StatefulSet update to roll out (0/n Pods ready)

2. If you do update the pods yourself while Pulumi is waiting, Pulumi will continue to wait on

Waiting for StatefulSet update to roll out (n/n Pods ready)

, and eventually error and time out because

.status.currentRevision

was not updated to

.status.updatedRevision

:

Diagnostics:
  kubernetes:apps/v1:StatefulSet (interactions-app):
    error: 3 errors occurred:
        * the Kubernetes API server reported that "default/interactions-app-b2ecafa3" failed to fully initialize or become live: 'interactions-app-b2ecafa3' timed out waiting to be Ready
        * 32 out of 32 replicas succeeded readiness checks
        * StatefulSet controller failed to advance from revision "interactions-app-b2ecafa3-646dcff454" to revision "interactions-app-b2ecafa3-569b7cb476"

Relevant issue? https://github.com/pulumi/pulumi-kubernetes/issues/1066

Hi- apologies for the tardy response. Unfortunately, I think the github issue you linked ☝️ details the issue you are facing. I do not know of a workaround off the top of my head, but I have asked our internal team for some additional support, including potential workarounds. Also, if you don't mind giving the github issue a 👍 , this will help our team prioritize the backlog of work. Thanks!

I see, thank you for the confirmation 👍

@bright-horse-50102 After doing some thinking/digging, I think you might be able to make use of the

skipAwait

annotation in Pulumi Kubernetes as a workaround here. https://www.pulumi.com/blog/improving-kubernetes-management-with-pulumis-await-logic/

Thanks @green-stone-37839, tested this out and it works 👍