Increase default readiness timeouts to 10 mins

Deployment, Pod and StatefulSet resources previously had default timeouts set to 5 minutes. Increase the timeout to 10 minutes for consistency with other resources.
pulumi · Aug 20, 2019 · b0de020 · b0de020
1 parent 3ea7823
commit b0de020
Show file tree

Hide file tree

Showing 20 changed files with 20 additions and 19 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -10,6 +10,7 @@
 
 -   Document await logic in the SDKs. (https://github.com/pulumi/pulumi-kubernetes/pull/711).
 -   Document await timeouts and how to override. (https://github.com/pulumi/pulumi-kubernetes/pull/718).
+-   Increase default readiness timeouts to 10 mins. (https://github.com/pulumi/pulumi-kubernetes/pull/721).
 
 ## 1.0.0-beta.1 (August 13, 2019)
 

diff --git a/pkg/await/apps_deployment.go b/pkg/await/apps_deployment.go
@@ -89,7 +89,7 @@ import (
 
 const (
 	revision                     = "deployment.kubernetes.io/revision"
-	DefaultDeploymentTimeoutMins = 5
+	DefaultDeploymentTimeoutMins = 10
 )
 
 type deploymentInitAwaiter struct {

diff --git a/pkg/await/apps_statefulset.go b/pkg/await/apps_statefulset.go
@@ -101,7 +101,7 @@ import (
 // ------------------------------------------------------------------------------------------------
 
 const (
-	DefaultStatefulSetTimeoutMins = 5
+	DefaultStatefulSetTimeoutMins = 10
 )
 
 type statefulsetInitAwaiter struct {

diff --git a/pkg/await/core_pod.go b/pkg/await/core_pod.go
@@ -85,7 +85,7 @@ import (
 // --------------------------------------------------------------------------
 
 const (
-	DefaultPodTimeoutMins = 5
+	DefaultPodTimeoutMins = 10
 )
 
 type podInitAwaiter struct {

diff --git a/sdk/nodejs/apps/v1/Deployment.ts b/sdk/nodejs/apps/v1/Deployment.ts
@@ -26,7 +26,7 @@ import { getVersion } from "../../version";
      *    because it doesn't do a rollout (i.e., it simply creates the Deployment and
      *    corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.
      * 
-     * If the Deployment has not reached a Ready state after 5 minutes, it will
+     * If the Deployment has not reached a Ready state after 10 minutes, it will
      * time out and mark the resource update as Failed. You can override the default timeout value
      * by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
      * This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/nodejs/apps/v1/StatefulSet.ts b/sdk/nodejs/apps/v1/StatefulSet.ts
@@ -21,7 +21,7 @@ import { getVersion } from "../../version";
      *    and '.status.readyReplicas'.
      * 2. The value of '.status.updateRevision' matches '.status.currentRevision'.
      * 
-     * If the StatefulSet has not reached a Ready state after 5 minutes, it will
+     * If the StatefulSet has not reached a Ready state after 10 minutes, it will
      * time out and mark the resource update as Failed. You can override the default timeout value
      * by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
      * This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/nodejs/apps/v1beta1/Deployment.ts b/sdk/nodejs/apps/v1beta1/Deployment.ts
@@ -28,7 +28,7 @@ import { getVersion } from "../../version";
      *    because it doesn't do a rollout (i.e., it simply creates the Deployment and
      *    corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.
      * 
-     * If the Deployment has not reached a Ready state after 5 minutes, it will
+     * If the Deployment has not reached a Ready state after 10 minutes, it will
      * time out and mark the resource update as Failed. You can override the default timeout value
      * by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
      * This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/nodejs/apps/v1beta1/StatefulSet.ts b/sdk/nodejs/apps/v1beta1/StatefulSet.ts
@@ -23,7 +23,7 @@ import { getVersion } from "../../version";
      *    and '.status.readyReplicas'.
      * 2. The value of '.status.updateRevision' matches '.status.currentRevision'.
      * 
-     * If the StatefulSet has not reached a Ready state after 5 minutes, it will
+     * If the StatefulSet has not reached a Ready state after 10 minutes, it will
      * time out and mark the resource update as Failed. You can override the default timeout value
      * by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
      * This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/nodejs/apps/v1beta2/Deployment.ts b/sdk/nodejs/apps/v1beta2/Deployment.ts
@@ -28,7 +28,7 @@ import { getVersion } from "../../version";
      *    because it doesn't do a rollout (i.e., it simply creates the Deployment and
      *    corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.
      * 
-     * If the Deployment has not reached a Ready state after 5 minutes, it will
+     * If the Deployment has not reached a Ready state after 10 minutes, it will
      * time out and mark the resource update as Failed. You can override the default timeout value
      * by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
      * This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/nodejs/apps/v1beta2/StatefulSet.ts b/sdk/nodejs/apps/v1beta2/StatefulSet.ts
@@ -23,7 +23,7 @@ import { getVersion } from "../../version";
      *    and '.status.readyReplicas'.
      * 2. The value of '.status.updateRevision' matches '.status.currentRevision'.
      * 
-     * If the StatefulSet has not reached a Ready state after 5 minutes, it will
+     * If the StatefulSet has not reached a Ready state after 10 minutes, it will
      * time out and mark the resource update as Failed. You can override the default timeout value
      * by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
      * This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/nodejs/core/v1/Pod.ts b/sdk/nodejs/core/v1/Pod.ts
@@ -20,7 +20,7 @@ import { getVersion } from "../../version";
      *    set to "Running".
      * Or (for Jobs): The Pod succeeded ('.status.phase' set to "Succeeded").
      * 
-     * If the Pod has not reached a Ready state after 5 minutes, it will
+     * If the Pod has not reached a Ready state after 10 minutes, it will
      * time out and mark the resource update as Failed. You can override the default timeout value
      * by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
      * This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/nodejs/extensions/v1beta1/Deployment.ts b/sdk/nodejs/extensions/v1beta1/Deployment.ts
@@ -28,7 +28,7 @@ import { getVersion } from "../../version";
      *    because it doesn't do a rollout (i.e., it simply creates the Deployment and
      *    corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.
      * 
-     * If the Deployment has not reached a Ready state after 5 minutes, it will
+     * If the Deployment has not reached a Ready state after 10 minutes, it will
      * time out and mark the resource update as Failed. You can override the default timeout value
      * by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
      * This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/python/pulumi_kubernetes/apps/v1/Deployment.py b/sdk/python/pulumi_kubernetes/apps/v1/Deployment.py
@@ -32,7 +32,7 @@ class Deployment(pulumi.CustomResource):
        because it doesn't do a rollout (i.e., it simply creates the Deployment and
        corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.
     
-    If the Deployment has not reached a Ready state after 5 minutes, it will
+    If the Deployment has not reached a Ready state after 10 minutes, it will
     time out and mark the resource update as Failed. You can override the default timeout value
     by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
     This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/python/pulumi_kubernetes/apps/v1/StatefulSet.py b/sdk/python/pulumi_kubernetes/apps/v1/StatefulSet.py
@@ -27,7 +27,7 @@ class StatefulSet(pulumi.CustomResource):
        and '.status.readyReplicas'.
     2. The value of '.status.updateRevision' matches '.status.currentRevision'.
     
-    If the StatefulSet has not reached a Ready state after 5 minutes, it will
+    If the StatefulSet has not reached a Ready state after 10 minutes, it will
     time out and mark the resource update as Failed. You can override the default timeout value
     by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
     This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/python/pulumi_kubernetes/apps/v1beta1/Deployment.py b/sdk/python/pulumi_kubernetes/apps/v1beta1/Deployment.py
@@ -34,7 +34,7 @@ class Deployment(pulumi.CustomResource):
        because it doesn't do a rollout (i.e., it simply creates the Deployment and
        corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.
     
-    If the Deployment has not reached a Ready state after 5 minutes, it will
+    If the Deployment has not reached a Ready state after 10 minutes, it will
     time out and mark the resource update as Failed. You can override the default timeout value
     by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
     This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/python/pulumi_kubernetes/apps/v1beta1/StatefulSet.py b/sdk/python/pulumi_kubernetes/apps/v1beta1/StatefulSet.py
@@ -29,7 +29,7 @@ class StatefulSet(pulumi.CustomResource):
        and '.status.readyReplicas'.
     2. The value of '.status.updateRevision' matches '.status.currentRevision'.
     
-    If the StatefulSet has not reached a Ready state after 5 minutes, it will
+    If the StatefulSet has not reached a Ready state after 10 minutes, it will
     time out and mark the resource update as Failed. You can override the default timeout value
     by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
     This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/python/pulumi_kubernetes/apps/v1beta2/Deployment.py b/sdk/python/pulumi_kubernetes/apps/v1beta2/Deployment.py
@@ -34,7 +34,7 @@ class Deployment(pulumi.CustomResource):
        because it doesn't do a rollout (i.e., it simply creates the Deployment and
        corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.
     
-    If the Deployment has not reached a Ready state after 5 minutes, it will
+    If the Deployment has not reached a Ready state after 10 minutes, it will
     time out and mark the resource update as Failed. You can override the default timeout value
     by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
     This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/python/pulumi_kubernetes/apps/v1beta2/StatefulSet.py b/sdk/python/pulumi_kubernetes/apps/v1beta2/StatefulSet.py
@@ -29,7 +29,7 @@ class StatefulSet(pulumi.CustomResource):
        and '.status.readyReplicas'.
     2. The value of '.status.updateRevision' matches '.status.currentRevision'.
     
-    If the StatefulSet has not reached a Ready state after 5 minutes, it will
+    If the StatefulSet has not reached a Ready state after 10 minutes, it will
     time out and mark the resource update as Failed. You can override the default timeout value
     by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
     This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/python/pulumi_kubernetes/core/v1/Pod.py b/sdk/python/pulumi_kubernetes/core/v1/Pod.py
@@ -26,7 +26,7 @@ class Pod(pulumi.CustomResource):
        set to "Running".
     Or (for Jobs): The Pod succeeded ('.status.phase' set to "Succeeded").
     
-    If the Pod has not reached a Ready state after 5 minutes, it will
+    If the Pod has not reached a Ready state after 10 minutes, it will
     time out and mark the resource update as Failed. You can override the default timeout value
     by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
     This approach will be deprecated in favor of customTimeouts. See

diff --git a/sdk/python/pulumi_kubernetes/extensions/v1beta1/Deployment.py b/sdk/python/pulumi_kubernetes/extensions/v1beta1/Deployment.py
@@ -34,7 +34,7 @@ class Deployment(pulumi.CustomResource):
        because it doesn't do a rollout (i.e., it simply creates the Deployment and
        corresponding ReplicaSet), and therefore there is no rollout to mark as 'Progressing'.
     
-    If the Deployment has not reached a Ready state after 5 minutes, it will
+    If the Deployment has not reached a Ready state after 10 minutes, it will
     time out and mark the resource update as Failed. You can override the default timeout value
     by setting 'pulumi.com/timeoutSeconds' as a '.metadata.annotation' on the resource.
     This approach will be deprecated in favor of customTimeouts. See