feat(helm): update chart loki to 6.24.0

[renovate]

This PR contains the following updates:

Package	Update	Change
loki (source)	minor	6.12.0 -> 6.24.0

---

Release Notes

grafana/helm-charts (loki)

v6.24.0

The leading tool for querying and visualizing time series and metrics.

v6.23.0

The leading tool for querying and visualizing time series and metrics.

v6.22.0

The leading tool for querying and visualizing time series and metrics.

v6.21.0

The leading tool for querying and visualizing time series and metrics.

v6.20.0

The leading tool for querying and visualizing time series and metrics.

v6.19.0

The leading tool for querying and visualizing time series and metrics.

v6.18.0

The leading tool for querying and visualizing time series and metrics.

v6.16.0

Promtail is an agent which ships the contents of local logs to a Loki instance

What's Changed

• [promtail] update to 3.0.0 by @​mjnagel in https://github.com/grafana/helm-charts/pull/3083

New Contributors

• @​mjnagel made their first contribution in https://github.com/grafana/helm-charts/pull/3083

Full Changelog: grafana/helm-charts@grafana-agent-operator-0.4.0...promtail-6.16.0

v6.15.0

Helm chart for Grafana Loki and Grafana Enterprise Logs supporting both simple, scalable and distributed modes

Source commit: grafana/loki@03a1eba

Tag on source: https://github.com/grafana/loki/releases/tag/helm-loki-6.15.0

---

Configuration

📅 Schedule: Branch creation - "on saturday" (UTC), Automerge - At any time (no schedule defined).

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

♻ 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 was generated by Mend Renovate. View the repository job log.

[jsaveker]

Here is an automated review from ChatGPT of this pull request.

Based on the provided git diff, there are no direct security issues that can be identified solely from the version change in a Helm chart for Loki from version 6.12.0 to version 6.15.0.

However, when updating the version of a software component, you should ensure that:

1. The new version does not contain any known vulnerabilities. This requires checking the release notes and possibly vulnerability databases for any security advisories related to loki version 6.15.0.
2. The update is compatible with your existing deployments and will not unintentionally expose any sensitive data or increase the attack surface area of your infrastructure.

Suggested Checks:

1. Review Release Notes: Before updating, review the release notes of Loki version 6.15.0 for any security-related fixes or known vulnerabilities. This will help in understanding the impact of the update.

2. Vulnerability Scan: Use vulnerability scanning tools to check if the new version introduces any known vulnerabilities.

3. Test in a Controlled Environment: Deploy the updated version in a test environment first to identify potential issues, ensuring that the upgrade will not adversely affect your monitoring infrastructure.

No Specific Fixes Required: As the diff does not contain directly executable code or configuration parameters that could be evaluated for security best practices, there are no specific security fixes to suggest based on the provided context.

Just ensure to follow general best practices as outlined when updating software versions in production environments.