Skip to content

Commit

Permalink
Add a section regarding logzio-monitoring v3 upgrade
Browse files Browse the repository at this point in the history
  • Loading branch information
ralongit committed Nov 27, 2023
1 parent 902d520 commit f1f6d16
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions docs/shipping/Containers/kubernetes.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

0 comments on commit f1f6d16

Please sign in to comment.