From 9435c3558c98e2eed2b024adb5055dd7b2d31008 Mon Sep 17 00:00:00 2001 From: David Calvert Date: Thu, 29 Feb 2024 10:19:30 +0100 Subject: [PATCH] [kube-state-metrics] updateStrategy doc to fix #4095 (#4318) Signed-off-by: David Calvert --- charts/kube-state-metrics/Chart.yaml | 2 +- charts/kube-state-metrics/values.yaml | 5 ++++- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/charts/kube-state-metrics/Chart.yaml b/charts/kube-state-metrics/Chart.yaml index c420b344b4ba..fa3d7dcc0f86 100644 --- a/charts/kube-state-metrics/Chart.yaml +++ b/charts/kube-state-metrics/Chart.yaml @@ -7,7 +7,7 @@ keywords: - prometheus - kubernetes type: application -version: 5.16.1 +version: 5.16.2 appVersion: 2.10.1 home: https://github.com/kubernetes/kube-state-metrics/ sources: diff --git a/charts/kube-state-metrics/values.yaml b/charts/kube-state-metrics/values.yaml index 7f312961d38d..95e09a3b9bc2 100644 --- a/charts/kube-state-metrics/values.yaml +++ b/charts/kube-state-metrics/values.yaml @@ -37,7 +37,10 @@ autosharding: replicas: 1 -# Change the deployment strategy when autosharding is disabled +# Change the deployment strategy when autosharding is disabled. +# ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy +# The default is "RollingUpdate" as per Kubernetes defaults. +# During a release, 'RollingUpdate' can lead to two running instances for a short period of time while 'Recreate' can create a small gap in data. # updateStrategy: Recreate # Number of old history to retain to allow rollback