Change default timeouts back to previous values

Pulling behavior changes into a separate PR, so this change is just docs now
pulumi · Aug 20, 2019 · 3ea7823 · 3ea7823
1 parent ee263be
commit 3ea7823
Show file tree

Hide file tree

Showing 20 changed files with 23 additions and 23 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -19,6 +19,10 @@
 - v1.14.x
 - v1.13.x
 
+### Improvements
+
+-   Add .get() to Python SDK. (https://github.com/pulumi/pulumi-kubernetes/pull/435).
+
 ## 0.25.6 (August 7, 2019)
 
 ### Supported Kubernetes versions
@@ -27,10 +31,6 @@
 - v1.14.x
 - v1.13.x
 
-### Improvements
-
--   Add .get() to Python SDK. (https://github.com/pulumi/pulumi-kubernetes/pull/435).
-
 ### Bug fixes
 
 -   Align YAML parsing with core Kubernetes supported YAML subset. (https://github.com/pulumi/pulumi-kubernetes/pull/690).

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 = 10
+	DefaultDeploymentTimeoutMins = 5
 )
 
 type deploymentInitAwaiter struct {

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

diff --git a/pkg/await/core_pod.go b/pkg/await/core_pod.go
@@ -85,7 +85,7 @@ import (
 // --------------------------------------------------------------------------
 
 const (
-	DefaultPodTimeoutMins = 10
+	DefaultPodTimeoutMins = 5
 )
 
 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 10 minutes, it will
+     * If the Deployment has not reached a Ready state after 5 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 10 minutes, it will
+     * If the StatefulSet has not reached a Ready state after 5 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 10 minutes, it will
+     * If the Deployment has not reached a Ready state after 5 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 10 minutes, it will
+     * If the StatefulSet has not reached a Ready state after 5 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 10 minutes, it will
+     * If the Deployment has not reached a Ready state after 5 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 10 minutes, it will
+     * If the StatefulSet has not reached a Ready state after 5 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 10 minutes, it will
+     * If the Pod has not reached a Ready state after 5 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 10 minutes, it will
+     * If the Deployment has not reached a Ready state after 5 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 10 minutes, it will
+    If the Deployment has not reached a Ready state after 5 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 10 minutes, it will
+    If the StatefulSet has not reached a Ready state after 5 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 10 minutes, it will
+    If the Deployment has not reached a Ready state after 5 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 10 minutes, it will
+    If the StatefulSet has not reached a Ready state after 5 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 10 minutes, it will
+    If the Deployment has not reached a Ready state after 5 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 10 minutes, it will
+    If the StatefulSet has not reached a Ready state after 5 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 10 minutes, it will
+    If the Pod has not reached a Ready state after 5 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 10 minutes, it will
+    If the Deployment has not reached a Ready state after 5 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