Update Helm release netdata to v3.7.168

[renovate]

This PR contains the following updates:

Package	Update	Change	Pending
netdata (source)	patch	3.7.166 → 3.7.168	3.7.170 (+1)

---

Release Notes

netdata/helmchart (netdata)

v3.7.168

Compare Source

Real-time performance monitoring, done right!

v3.7.167

Compare Source

Real-time performance monitoring, done right!

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • "after 12am and before 2am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[github-actions]

netdata (helm) 3.7.166 -> 3.7.168

Risk: 🟢 Safe

The Deep Dive

Update Scope

#2530 updates the Netdata Helm chart from 3.7.166 to 3.7.168; its committed render changes only chart metadata labels. Netdata Agent remains at v2.10.3 and the bundled OpenTelemetry Collector chart remains at 0.144.0; container images, pod templates, and configured application settings are unchanged (3.7.166 package, 3.7.168 package).

Hazards & Risks

None identified. The committed manifest diff changes only top-level chart metadata labels and does not modify an image or pod template, so no configured runtime path, migration, or compatibility boundary changes.

Sources

• Infrastructure PR #2530 files
• Netdata chart 3.7.167 release
• Netdata chart 3.7.168 release
• Netdata chart 3.7.166 to 3.7.168 comparison
• OpenTelemetry signal-viewer fix
• OpenTelemetry absolute-path fix
• Netdata chart 3.7.169 release
• Netdata chart 3.7.168 to 3.7.169 comparison
• Netdata Helm chart security advisories
• Netdata Agent security advisories
• NVD Netdata CVE search

---

🟢 Verdict: Safe

renovate:safe: the committed manifest diff is metadata-only, leaving runtime images, pod templates, and configured application settings unchanged. It introduces no deployment-relevant hazard or targeted validation need beyond the repository's normal workflow.