From 299be24a9a94d833767c41aadf0abc1011ad970c Mon Sep 17 00:00:00 2001 From: aimuz Date: Mon, 10 Aug 2020 17:33:47 +0800 Subject: [PATCH] =?UTF-8?q?tosca.policies.wise2c.UpgradeStrategy=20?= =?UTF-8?q?=E5=AE=9A=E4=B9=89?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../extensions/wse/TOSCA_wse_definition_1_0_0.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/toscaparser/extensions/wse/TOSCA_wse_definition_1_0_0.yaml b/toscaparser/extensions/wse/TOSCA_wse_definition_1_0_0.yaml index 68142b7..b8d71d0 100644 --- a/toscaparser/extensions/wse/TOSCA_wse_definition_1_0_0.yaml +++ b/toscaparser/extensions/wse/TOSCA_wse_definition_1_0_0.yaml @@ -854,6 +854,18 @@ policy_types: start_first: type: boolean description: Rancher only + maxUnavailable: + type: string + 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 down. This + can not be 0 if MaxSurge is 0. Defaults to 25%. Example: when this is set + to 30%, the old ReplicaSet can be scaled down to 70% of desired pods + immediately when the rolling update starts. Once new pods are ready, old + ReplicaSet can be scaled down further, followed by scaling up the new + ReplicaSet, ensuring that the total number of pods available at all times + during the update is at least 70% of desired pods. tosca.policies.wise2c.Wildcard: derived_from: tosca.policies.Roo properties: -- Gitee