bright-horse-50102
08/25/2022, 1:54 AMWaiting 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/1066green-stone-37839
08/26/2022, 7:05 PMbright-horse-50102
08/26/2022, 7:12 PMgreen-stone-37839
08/30/2022, 4:13 PMskipAwait
annotation in Pulumi Kubernetes as a workaround here.
https://www.pulumi.com/blog/improving-kubernetes-management-with-pulumis-await-logic/bright-horse-50102
08/30/2022, 11:41 PM