From 84a95aeb049c27ce1402c22b047422c6b3fb65ce Mon Sep 17 00:00:00 2001 From: TrueCharts Bot Date: Wed, 8 May 2024 20:33:38 +0200 Subject: [PATCH] chore(deps): update container image netdata/netdata to v1.45.4@f4ee90a by renovate (#21789) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This PR contains the following updates: | Package | Update | Change | |---|---|---| | [netdata/netdata](https://netdata.cloud) ([source](https://togithub.com/netdata/netdata)) | patch | `v1.45.3` -> `v1.45.4` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes
netdata/netdata (netdata/netdata) ### [`v1.45.4`](https://togithub.com/netdata/netdata/releases/tag/v1.45.4) [Compare Source](https://togithub.com/netdata/netdata/compare/v1.45.3...v1.45.4) Netdata v1.45.4 is a patch release to address issues discovered since [v1.45.3](https://togithub.com/netdata/netdata/releases/tag/v1.45.3). This patch release provides the following bug fixes and updates: - Added missing update_every property to the health prototype JSON schema ([#​17613](https://togithub.com/netdata/netdata/pull/17613), [@​ktsaou](https://togithub.com/ktsaou)) - Fixed issue where parent alerts remained active after child disconnection, by resetting health on child disconnect ([#​17612](https://togithub.com/netdata/netdata/pull/17612), [@​ktsaou](https://togithub.com/ktsaou)) - Fixed a packaging issue that prevented ndsudo from having the setuid bit in static builds ([#​17583](https://togithub.com/netdata/netdata/pull/17583), [@​ilyam8](https://togithub.com/ilyam8)) - Increased spawn server command size and added shutdown safeguard to prevent crashes from command size limit exceeded ([#​17566](https://togithub.com/netdata/netdata/pull/17566), [@​stelfrag](https://togithub.com/stelfrag)) - Fixed error code reporting for failed data insertion in SQLite ([#​17508](https://togithub.com/netdata/netdata/pull/17508), [@​stelfrag](https://togithub.com/stelfrag)) - Fixed issue with name-only label matching ([#​17482](https://togithub.com/netdata/netdata/pull/17482), [@​stelfrag](https://togithub.com/stelfrag)) - Improved Cloud connectivity: automatically re-establish connection upon system resume from suspension by scheduling a node update ([#​17444](https://togithub.com/netdata/netdata/pull/17444), [@​stelfrag](https://togithub.com/stelfrag)) - Improved termination handling: start watcher thread post-fork, preventing main process from waiting indefinitely on TERM signal ([#​17436](https://togithub.com/netdata/netdata/pull/17436), [@​stelfrag](https://togithub.com/stelfrag)) - Fixed priority order for alarms and alarm templates: now, alarms are applied before alarm templates consistently, regardless of their order in configuration files ([#​17398](https://togithub.com/netdata/netdata/pull/17398), [@​ktsaou](https://togithub.com/ktsaou)) - Added option for health table cleanup with 'netdata -W sqlite-alert-cleanup' command ([#​17385](https://togithub.com/netdata/netdata/pull/17385), [@​stelfrag](https://togithub.com/stelfrag)) #### Support options As we grow, we stay committed to providing the best support ever seen from an open-source solution. Should you encounter an issue with any of the changes made in this release or any feature in the Netdata Agent, feel free to contact us through one of the following channels: - [Netdata Learn](https://learn.netdata.cloud): Find documentation, guides, and reference material for monitoring and troubleshooting your systems with Netdata. - [GitHub Issues](https://togithub.com/netdata/netdata/issues): Make use of the Netdata repository to report bugs or open a new feature request. - [GitHub Discussions](https://togithub.com/netdata/netdata/discussions): Join the conversation around the Netdata development process and be a part of it. - [Community Forums](https://community.netdata.cloud/): Visit the Community Forums and contribute to the collaborative knowledge base. - [Discord Server](https://discord.gg/2eduZdSeC7): Jump into the Netdata Discord and hang out with like-minded sysadmins, DevOps, SREs, and other troubleshooters. More than 2000 engineers are already using it!
--- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://togithub.com/renovatebot/renovate). --- charts/stable/netdata/Chart.yaml | 6 +++--- charts/stable/netdata/values.yaml | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/charts/stable/netdata/Chart.yaml b/charts/stable/netdata/Chart.yaml index 1b5f4144fa3..4ea03af6259 100644 --- a/charts/stable/netdata/Chart.yaml +++ b/charts/stable/netdata/Chart.yaml @@ -7,7 +7,7 @@ annotations: truecharts.org/min_helm_version: "3.11" truecharts.org/train: stable apiVersion: v2 -appVersion: 1.45.3 +appVersion: 1.45.4 dependencies: - name: common version: 23.0.0 @@ -23,7 +23,7 @@ icon: https://truecharts.org/img/hotlink-ok/chart-icons/netdata.webp keywords: - netdata - monitoring -kubeVersion: ">=1.24.0-0" +kubeVersion: '>=1.24.0-0' maintainers: - name: TrueCharts email: info@truecharts.org @@ -34,4 +34,4 @@ sources: - https://github.com/truecharts/charts/tree/master/charts/stable/netdata - https://hub.docker.com/r/netdata/netdata type: application -version: 10.0.5 +version: 10.0.6 diff --git a/charts/stable/netdata/values.yaml b/charts/stable/netdata/values.yaml index 73a98e74d45..728ff388d88 100644 --- a/charts/stable/netdata/values.yaml +++ b/charts/stable/netdata/values.yaml @@ -1,6 +1,6 @@ image: repository: netdata/netdata - tag: v1.45.3@sha256:ba6ec15dfcc32c294d749c0ed91a846ce73be41070b6ceef258d9d05308f490f + tag: v1.45.4@sha256:f4ee90aac06d641ddb999d0e6d1e78c8f2b1d18367b2db42af195d47ccbf3a32 pullPolicy: IfNotPresent # -- The service account the pods will use to interact with the Kubernetes API serviceAccount: