From 7bba357f60f93bdfda0c69a367fcb141bc14553c Mon Sep 17 00:00:00 2001 From: Aleksandr Rybolovlev Date: Wed, 18 Dec 2024 13:10:40 +0100 Subject: [PATCH] Update max_unavailable and max_surge validate functions (#2653) --- .changelog/2653.txt | 3 ++ .../resource_kubernetes_daemon_set_v1.go | 4 +-- .../resource_kubernetes_daemon_set_v1_test.go | 32 +++++++++++++++++-- 3 files changed, 35 insertions(+), 4 deletions(-) create mode 100644 .changelog/2653.txt diff --git a/.changelog/2653.txt b/.changelog/2653.txt new file mode 100644 index 0000000000..5ebcd83126 --- /dev/null +++ b/.changelog/2653.txt @@ -0,0 +1,3 @@ +```release-note:bug +`kubernetes_daemon_set_v1`: fix issue where fields `spec.strategy.rolling_update.max_surge` and `spec.strategy.rolling_update.max_unavailable` were not being validated correctly. +``` diff --git a/kubernetes/resource_kubernetes_daemon_set_v1.go b/kubernetes/resource_kubernetes_daemon_set_v1.go index 00ffa40b3a..3774cff40e 100644 --- a/kubernetes/resource_kubernetes_daemon_set_v1.go +++ b/kubernetes/resource_kubernetes_daemon_set_v1.go @@ -109,14 +109,14 @@ func resourceKubernetesDaemonSetSchemaV1() map[string]*schema.Schema { Description: "The maximum number of nodes with an existing available DaemonSet pod that can have an updated DaemonSet pod during during an update. 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 to a minimum of 1. Default value is 0. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their a new pod created before the old pod is marked as deleted. The update starts by launching new pods on 30% of nodes. Once an updated pod is available (Ready for at least minReadySeconds) the old DaemonSet pod on that node is marked deleted. If the old pod becomes unavailable for any reason Ready transitions to false, is evicted, or is drained) an updated pod is immediatedly created on that node without considering surge limits. Allowing surge implies the possibility that the resources consumed by the daemonset on any given node can double if the readiness check fails, and so resource intensive daemonsets should take into account that they may cause evictionsduring disruption.", Optional: true, Default: 0, - ValidateFunc: validation.StringMatch(regexp.MustCompile(`^(0|[1-9][0-9]*|[1-9][0-9]%|100%)$`), ""), + ValidateFunc: validation.StringMatch(regexp.MustCompile(`^(0|[1-9][0-9]*|[1-9][0-9]?%|100%)$`), ""), }, "max_unavailable": { Type: schema.TypeString, Description: "The maximum number of DaemonSet pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total number of DaemonSet pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0 if MaxSurge is 0 Default value is 1. Example: when this is set to 30%, at most 30% of the total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their pods stopped for an update at any given time. The update starts by stopping at most 30% of those DaemonSet pods and then brings up new DaemonSet pods in their place. Once the new pods are available, it then proceeds onto other DaemonSet pods, thus ensuring that at least 70% of original number of DaemonSet pods are available at all times during the update.", Optional: true, Default: 1, - ValidateFunc: validation.StringMatch(regexp.MustCompile(`^(0|[1-9][0-9]*|[1-9][0-9]%|100%)$`), ""), + ValidateFunc: validation.StringMatch(regexp.MustCompile(`^(0|[1-9][0-9]*|[1-9][0-9]?%|100%)$`), ""), }, }, }, diff --git a/kubernetes/resource_kubernetes_daemon_set_v1_test.go b/kubernetes/resource_kubernetes_daemon_set_v1_test.go index d166670b2c..5baf1f5a57 100644 --- a/kubernetes/resource_kubernetes_daemon_set_v1_test.go +++ b/kubernetes/resource_kubernetes_daemon_set_v1_test.go @@ -453,10 +453,31 @@ func TestAccKubernetesDaemonSetV1_MaxSurge(t *testing.T) { ), }, { - Config: testAccKubernetesDaemonSetV1ConfigWithMaxSurge(name, imageName, "2"), + Config: testAccKubernetesDaemonSetV1ConfigWithMaxSurge(name, imageName, "5"), Check: resource.ComposeAggregateTestCheckFunc( testAccCheckKubernetesDaemonSetV1Exists(resourceName, &conf), - resource.TestCheckResourceAttr(resourceName, "spec.0.strategy.0.rolling_update.0.max_surge", "2"), + resource.TestCheckResourceAttr(resourceName, "spec.0.strategy.0.rolling_update.0.max_surge", "5"), + ), + }, + { + Config: testAccKubernetesDaemonSetV1ConfigWithMaxSurge(name, imageName, "10"), + Check: resource.ComposeAggregateTestCheckFunc( + testAccCheckKubernetesDaemonSetV1Exists(resourceName, &conf), + resource.TestCheckResourceAttr(resourceName, "spec.0.strategy.0.rolling_update.0.max_surge", "10"), + ), + }, + { + Config: testAccKubernetesDaemonSetV1ConfigWithMaxSurge(name, imageName, "100"), + Check: resource.ComposeAggregateTestCheckFunc( + testAccCheckKubernetesDaemonSetV1Exists(resourceName, &conf), + resource.TestCheckResourceAttr(resourceName, "spec.0.strategy.0.rolling_update.0.max_surge", "100"), + ), + }, + { + Config: testAccKubernetesDaemonSetV1ConfigWithMaxSurge(name, imageName, "5%"), + Check: resource.ComposeAggregateTestCheckFunc( + testAccCheckKubernetesDaemonSetV1Exists(resourceName, &conf), + resource.TestCheckResourceAttr(resourceName, "spec.0.strategy.0.rolling_update.0.max_surge", "5%"), ), }, { @@ -466,6 +487,13 @@ func TestAccKubernetesDaemonSetV1_MaxSurge(t *testing.T) { resource.TestCheckResourceAttr(resourceName, "spec.0.strategy.0.rolling_update.0.max_surge", "10%"), ), }, + { + Config: testAccKubernetesDaemonSetV1ConfigWithMaxSurge(name, imageName, "100%"), + Check: resource.ComposeAggregateTestCheckFunc( + testAccCheckKubernetesDaemonSetV1Exists(resourceName, &conf), + resource.TestCheckResourceAttr(resourceName, "spec.0.strategy.0.rolling_update.0.max_surge", "100%"), + ), + }, }, }) }