From 54a5cc9fce3f57ec2366fe8a76393c580ac9455a Mon Sep 17 00:00:00 2001 From: Peter Brachwitz Date: Wed, 20 Aug 2025 14:54:54 +0200 Subject: [PATCH 1/3] Note that upgrades to ECK 3.1 cause a restart --- deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md b/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md index ab52a7c661..f3acfa899c 100644 --- a/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md +++ b/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md @@ -101,7 +101,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 +1.6, 1.9, 2.0, 2.1, 2.2, 2.4, 2.5, 2.6, 2.7, 2.8, 2.14, 3.1 ``` ::::{note} Stepping over one of these versions, for example, upgrading ECK from 2.6 to 2.9, still triggers a rolling restart. From 0ea7bf258a4334f6c153911cf28943aa184b3421 Mon Sep 17 00:00:00 2001 From: Peter Brachwitz Date: Wed, 20 Aug 2025 18:36:06 +0200 Subject: [PATCH 2/3] Add callout to qualify restart statement --- deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md b/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md index f3acfa899c..99c6695e9a 100644 --- a/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md +++ b/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md @@ -101,8 +101,11 @@ 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.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> The restart when upgrading to version 3.1 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 483b348bc793fd3233468b48f1f624778e783ffa Mon Sep 17 00:00:00 2001 From: Peter Brachwitz Date: Thu, 21 Aug 2025 08:43:43 +0200 Subject: [PATCH 3/3] Update deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> --- deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md b/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md index 99c6695e9a..e80f5fb11e 100644 --- a/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md +++ b/deploy-manage/upgrade/orchestrator/upgrade-cloud-on-k8s.md @@ -104,7 +104,7 @@ Upgrading the operator results in a one-time update to existing managed resource 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> 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 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.