From 1059ef549d7d11c953842bc54f2b68244b0f4f0f Mon Sep 17 00:00:00 2001 From: Istvan Nagy Date: Mon, 27 Oct 2025 19:05:45 +0100 Subject: [PATCH 1/3] ECK 3.2 will restart when stack monitoring is used --- deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md b/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md index e80f5fb11e..de267a9b0a 100644 --- a/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md +++ b/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md @@ -101,10 +101,10 @@ This will update the ECK installation to the latest binary and update the CRDs a Upgrading the operator results in a one-time update to existing managed resources in the cluster. This potentially triggers a rolling restart of pods by Kubernetes to apply those changes. The following list contains the ECK operator versions that would cause a rolling restart after they have been installed. ``` -1.6, 1.9, 2.0, 2.1, 2.2, 2.4, 2.5, 2.6, 2.7, 2.8, 2.14, 3.1 <1> +1.6, 1.9, 2.0, 2.1, 2.2, 2.4, 2.5, 2.6, 2.7, 2.8, 2.14, 3.1 <1>, 3.2 <1> ``` -1. The restart when upgrading to version 3.1 happens only for applications using [stack monitoring](/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md). +1. The restart when upgrading to version 3.1 and 3.2 happens only for applications using [stack monitoring](/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md). ::::{note} Stepping over one of these versions, for example, upgrading ECK from 2.6 to 2.9, still triggers a rolling restart. From 760bf1cb44fceb4313718113b6c786eeacdfd0c2 Mon Sep 17 00:00:00 2001 From: Istvan Nagy Date: Tue, 28 Oct 2025 10:06:11 +0100 Subject: [PATCH 2/3] use footnote for restart explanation --- deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md b/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md index de267a9b0a..0c746fbe25 100644 --- a/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md +++ b/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md @@ -101,10 +101,10 @@ This will update the ECK installation to the latest binary and update the CRDs a Upgrading the operator results in a one-time update to existing managed resources in the cluster. This potentially triggers a rolling restart of pods by Kubernetes to apply those changes. The following list contains the ECK operator versions that would cause a rolling restart after they have been installed. ``` -1.6, 1.9, 2.0, 2.1, 2.2, 2.4, 2.5, 2.6, 2.7, 2.8, 2.14, 3.1 <1>, 3.2 <1> +1.6, 1.9, 2.0, 2.1, 2.2, 2.4, 2.5, 2.6, 2.7, 2.8, 2.14, 3.1^1^, 3.2^1^ ``` -1. The restart when upgrading to version 3.1 and 3.2 happens only for applications using [stack monitoring](/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md). +^1^ The restart when upgrading to version 3.1 and 3.2 happens only for applications using [stack monitoring](/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md). ::::{note} Stepping over one of these versions, for example, upgrading ECK from 2.6 to 2.9, still triggers a rolling restart. From 0abc7bcdd471df9014d1d552f629900425c3734a Mon Sep 17 00:00:00 2001 From: Istvan Nagy Date: Tue, 28 Oct 2025 18:08:53 +0100 Subject: [PATCH 3/3] removed code fences --- deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md b/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md index 0c746fbe25..893bfbe982 100644 --- a/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md +++ b/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md @@ -100,9 +100,7 @@ This will update the ECK installation to the latest binary and update the CRDs a Upgrading the operator results in a one-time update to existing managed resources in the cluster. This potentially triggers a rolling restart of pods by Kubernetes to apply those changes. The following list contains the ECK operator versions that would cause a rolling restart after they have been installed. -``` 1.6, 1.9, 2.0, 2.1, 2.2, 2.4, 2.5, 2.6, 2.7, 2.8, 2.14, 3.1^1^, 3.2^1^ -``` ^1^ The restart when upgrading to version 3.1 and 3.2 happens only for applications using [stack monitoring](/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md).