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

worried-city-86458

09/10/2019, 11:37 PM
I got a timeout trying to update an eks cluster from k8s 1.13 to 1.14:
Copy code
Dev-EksPulumi-eksCluster (eks:index:Cluster$aws:eks/cluster:Cluster)
error: Plan apply failed: 1 error occurred:
	* updating urn:pulumi:dev::k8s-infra::eks:index:Cluster$aws:eks/cluster:Cluster::Dev-EksPulumi-eksCluster: error waiting for EKS Cluster (Dev-EksPulumi-eksCluster-d16ec52) version update (3222e27e-b126-4546-9e37-d6b251e4a025): timeout while waiting for state to become 'Cancelled, Failed, Successful' (last state: 'InProgress', timeout: 20m0s)
Is this configurable somewhere?
w

white-balloon-205

09/11/2019, 12:04 AM
Was it just a matter of not waiting long enough? Or did it legitimately fail to get healthy? The timeout can be configured with
customTimeouts
- but it is possible that we don't yet thread through control of the timeouts on the ASG here from the
eks.Cluster
component. We are working on a general mechanism to allow this sort of customization in https://github.com/pulumi/pulumi/issues/2068.
w

worried-city-86458

09/11/2019, 12:53 AM
Ultimately it succeeded on the AWS side, but I haven't checked what was not run after that section and if I can re-run the stack without any problems.
I love the idea of an "escape hatch" as there's always something that gets missed or dropped when layering on abstractions
👍 2