Latest changes

library/k8s_v1beta1_deployment.py

@@ -128,6 +128,32 @@ options:
     aliases:
     - selector_match_labels
     type: dict
+  spec_strategy_rolling_update_max_surge:
+    description:
+    - 'The maximum number of pods that can be scheduled above the desired number of
+      pods. Value can be an absolute number (ex: 5) or a percentage of desired pods
+      (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated
+      from percentage by rounding up. By default, a value of 1 is used. Example: when
+      this is set to 30%, the new RC can be scaled up immediately when the rolling
+      update starts, such that the total number of old and new pods do not exceed
+      130% of desired pods. Once old pods have been killed, new RC can be scaled up
+      further, ensuring that total number of pods running at any time during the update
+      is atmost 130% of desired pods.'
+    aliases:
+    - strategy_rolling_update_max_surge
+  spec_strategy_rolling_update_max_unavailable:
+    description:
+    - 'The maximum number of pods that can be unavailable during the update. Value
+      can be an absolute number (ex: 5) or a percentage of desired pods (ex: 10%).
+      Absolute number is calculated from percentage by rounding up. This can not be
+      0 if MaxSurge is 0. By default, a fixed value of 1 is used. Example: when this
+      is set to 30%, the old RC can be scaled down to 70% of desired pods immediately
+      when the rolling update starts. Once new pods are ready, old RC can be scaled
+      down further, followed by scaling up the new RC, ensuring that the total number
+      of pods available at all times during the update is at least 70% of desired
+      pods.'
+    aliases:
+    - strategy_rolling_update_max_unavailable
   spec_strategy_type:
     description:
     - Type of deployment. Can be "Recreate" or "RollingUpdate". Default is RollingUpdate.