From f1f6d168a59d4f3939124ef5a7e8d6c01527d035 Mon Sep 17 00:00:00 2001 From: ralongit Date: Mon, 27 Nov 2023 16:49:20 +0200 Subject: [PATCH 1/2] Add a section regarding logzio-monitoring v3 upgrade --- docs/shipping/Containers/kubernetes.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/shipping/Containers/kubernetes.md b/docs/shipping/Containers/kubernetes.md index 1075e110..b41dfc0f 100644 --- a/docs/shipping/Containers/kubernetes.md +++ b/docs/shipping/Containers/kubernetes.md @@ -249,3 +249,13 @@ To address this issue, you can use the `--set` commands provided below in order --set logzio-fluentd.daemonset.init.containerImage=public.ecr.aws/docker/library/busybox --set logzio-trivy.image=public.ecr.aws/logzio/trivy-to-logzio ``` + +## Upgrade logzio-monitoring to v3.0.0 + +The logzio-monitoring chart was upgraded with breaking changes on version 3.0.0, upon trying to upgrade the chart using `helm upgrade -n monitoring --version 3.0.0 logzio-monitoring logzio-helm/logzio-monitoring`, an error occurs that correlates with the version upgrade of the sub charts of logzio-telemetry chart. + +There are 2 possible approachs for the upgrade you can choose from: + +- Before running the `helm upgrade` command, delete the old sub charts resources: `logzio-monitoring-prometheus-pushgateway` deployment and the `logzio-monitoring-prometheus-node-exporter` daemonset. + +- Re-install the chart. From 67d7be0c27cc5555558e24adf1a0bffe767d8d7a Mon Sep 17 00:00:00 2001 From: Nico <86240618+nico-shishkin@users.noreply.github.com> Date: Tue, 28 Nov 2023 10:03:45 +0100 Subject: [PATCH 2/2] Update kubernetes.md --- docs/shipping/Containers/kubernetes.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/shipping/Containers/kubernetes.md b/docs/shipping/Containers/kubernetes.md index b41dfc0f..08d07969 100644 --- a/docs/shipping/Containers/kubernetes.md +++ b/docs/shipping/Containers/kubernetes.md @@ -252,10 +252,10 @@ To address this issue, you can use the `--set` commands provided below in order ## Upgrade logzio-monitoring to v3.0.0 -The logzio-monitoring chart was upgraded with breaking changes on version 3.0.0, upon trying to upgrade the chart using `helm upgrade -n monitoring --version 3.0.0 logzio-monitoring logzio-helm/logzio-monitoring`, an error occurs that correlates with the version upgrade of the sub charts of logzio-telemetry chart. +The logzio-monitoring chart was upgraded with breaking changes in version 3.0.0. Upon attempting to upgrade the chart using `helm upgrade -n monitoring --version 3.0.0 logzio-monitoring logzio-helm/logzio-monitoring`, an error occurs that correlates with the version upgrade of the subcharts in the logzio-telemetry chart. -There are 2 possible approachs for the upgrade you can choose from: +There are two possible approaches to the upgrade you can choose from: -- Before running the `helm upgrade` command, delete the old sub charts resources: `logzio-monitoring-prometheus-pushgateway` deployment and the `logzio-monitoring-prometheus-node-exporter` daemonset. +- Before running the `helm upgrade` command, delete the old subcharts resources: `logzio-monitoring-prometheus-pushgateway` deployment and the `logzio-monitoring-prometheus-node-exporter` daemonset. -- Re-install the chart. +- Reinstall the chart.