chilly-photographer-6093204/22/2019, 11:01 PM
mins timeout. We are stuck and not able to proceed.
solve this? Or does
followed by re-running
Which change is it you are making that triggers this? Is it the addition of
? 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
to address this if it is just a timeout issue and not a GKE issue.
glamorous-printer-6654804/23/2019, 5:45 AM
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.
chilly-photographer-6093204/23/2019, 12:43 PM
part of standard installation.
So we end up running from our local box which is not desirable.