https://pulumi.com logo
#general
Title
# general
c

chilly-photographer-60932

04/22/2019, 11:01 PM
We are trying to upgrade our GKE cluster and the operations keeps timing out at the pulumi end with
10
mins timeout. We are stuck and not able to proceed.
w

white-balloon-205

04/23/2019, 1:03 AM
Does re-running the
pulumi update
solve this? Or does
pulumi refresh
followed by re-running
pulumi update
work? Which change is it you are making that triggers this? Is it the addition of
networkPolicy
? Does the change eventually succeed in the GKE cluster? https://github.com/pulumi/pulumi/issues/2655 is tracking making timeouts configurable, but I would expect re-running
update
and/or
refresh
to address this if it is just a timeout issue and not a GKE issue.
g

glamorous-printer-66548

04/23/2019, 5:45 AM
@white-balloon-205 I had this issue occasionally when increasing the
version
property of a large gke nodepool. Since GKE updates each node in the pool one by one and it takes typically ~4-5 minutes per node to do so it can easily exceed the 10 minutes operation timeout. Rerunning pulumi update and refresh after the update completed solved the problem for me.
c

chilly-photographer-60932

04/23/2019, 12:43 PM
@white-balloon-205 Yes , it is working. But we would certainly like an option to override this issue. The problem is that we would like to run this from CD and we cannot have an
refresh
and
update
part of standard installation. So we end up running from our local box which is not desirable.
2 Views