chore(deps): update Grafana Agent Operator version

[argoyle]

GRAFANA.YAML

bump chart version

change detected: * key "$.helmCharts[0].version" updated from "'5.28.0'" to "'5.28.1'", in file "ksm/kustomization.yaml"

5.28.1

Remark: We couldn't identify a way to automatically retrieve changelog information.
Please use following information to take informed decision

Helm Chart: kube-state-metrics
Install kube-state-metrics to generate and expose cluster-level metrics
Project Home: https://github.com/kubernetes/kube-state-metrics/

Version created on the 2025-01-29 18:45:17.41271504 +0000 UTC

Sources:

* https://github.com/kubernetes/kube-state-metrics/



URL:

* https://github.com/prometheus-community/helm-charts/releases/download/kube-state-metrics-5.28.1/kube-state-metrics-5.28.1.tgz

Bump Agent image version

changes detected: path "locals.agent_version" updated from "0.43.4" to "0.44.2" in file "locals.tf"

v0.44.2

Release published on the 2025-01-29 17:15:37 +0000 UTC at the url https://github.com/grafana/agent/releases/tag/v0.44.2

This is release `v0.44.2` of Grafana Agent.

### Upgrading

Read the relevant upgrade guides for specific instructions on upgrading from older versions:

* [Static mode upgrade guide](https://grafana.com/docs/agent/v0.44/static/upgrade-guide/)
* [Static mode Kubernetes operator upgrade guide](https://grafana.com/docs/agent/v0.44/operator/upgrade-guide/)
* [Flow mode upgrade guide](https://grafana.com/docs/agent/v0.44/flow/upgrade-guide/)

### Changes:

#### Bugfixes

- `loki.source.podlogs`: Fixed a bug which prevented clustering from working and caused duplicate logs to be sent.
  The bug only happened when no `selector` or `namespace_selector` blocks were specified in the Agent configuration. (@ptodev)

- `pyroscope.scrape` no longer tries to scrape endpoints which are not active targets anymore. (@wildum @mattdurham @dehaansa @ptodev)

#### Enhancements

- Upgrade `github.com/goccy/go-json` to v0.10.4, which reduces the memory consumption of an Agent instance by 20MB.
  If Agent is running certain otelcol components, this reduction will not apply. (@ptodev)
  
#### Other changes

- Remove setcap for `cap_net_bind_service` to allow Agent to run in restricted environments.
  Modern container runtimes allow binding to unprivileged ports as non-root. (@ptodev)

- Update to go 1.22.11 (@wildum)

### Installation

Note that Grafana Agent has been deprecated and is in Long-Term Support (LTS) through October 31, 2025. Grafana Agent will reach an End-of-Life (EOL) on November 1, 2025. Read more about why we recommend migrating to [Grafana Alloy](https://grafana.com/blog/2024/04/09/grafana-alloy-opentelemetry-collector-with-prometheus-pipelines/).

Refer to our installation guides for how to install the variants of Grafana Agent:

* [Install static mode](https://grafana.com/docs/agent/v0.44/static/set-up/install/)
* [Install the static mode Kubernetes operator](https://grafana.com/docs/agent/v0.44/operator/helm-getting-started/)
* [Install flow mode](https://grafana.com/docs/agent/v0.44/flow/setup/install/)

Bump Operator image version

change detected: * key "$.image.tag" updated from "v0.43.4" to "v0.44.2", in file "grafana/operator-values.yaml"

v0.44.2

Release published on the 2025-01-29 17:15:37 +0000 UTC at the url https://github.com/grafana/agent/releases/tag/v0.44.2

This is release `v0.44.2` of Grafana Agent.

### Upgrading

Read the relevant upgrade guides for specific instructions on upgrading from older versions:

* [Static mode upgrade guide](https://grafana.com/docs/agent/v0.44/static/upgrade-guide/)
* [Static mode Kubernetes operator upgrade guide](https://grafana.com/docs/agent/v0.44/operator/upgrade-guide/)
* [Flow mode upgrade guide](https://grafana.com/docs/agent/v0.44/flow/upgrade-guide/)

### Changes:

#### Bugfixes

- `loki.source.podlogs`: Fixed a bug which prevented clustering from working and caused duplicate logs to be sent.
  The bug only happened when no `selector` or `namespace_selector` blocks were specified in the Agent configuration. (@ptodev)

- `pyroscope.scrape` no longer tries to scrape endpoints which are not active targets anymore. (@wildum @mattdurham @dehaansa @ptodev)

#### Enhancements

- Upgrade `github.com/goccy/go-json` to v0.10.4, which reduces the memory consumption of an Agent instance by 20MB.
  If Agent is running certain otelcol components, this reduction will not apply. (@ptodev)
  
#### Other changes

- Remove setcap for `cap_net_bind_service` to allow Agent to run in restricted environments.
  Modern container runtimes allow binding to unprivileged ports as non-root. (@ptodev)

- Update to go 1.22.11 (@wildum)

### Installation

Note that Grafana Agent has been deprecated and is in Long-Term Support (LTS) through October 31, 2025. Grafana Agent will reach an End-of-Life (EOL) on November 1, 2025. Read more about why we recommend migrating to [Grafana Alloy](https://grafana.com/blog/2024/04/09/grafana-alloy-opentelemetry-collector-with-prometheus-pipelines/).

Refer to our installation guides for how to install the variants of Grafana Agent:

* [Install static mode](https://grafana.com/docs/agent/v0.44/static/set-up/install/)
* [Install the static mode Kubernetes operator](https://grafana.com/docs/agent/v0.44/operator/helm-getting-started/)
* [Install flow mode](https://grafana.com/docs/agent/v0.44/flow/setup/install/)

Bump Operator module version

changes detected: path "locals.version" updated from "0.43.4" to "0.44.2" in file "locals.tf"

v0.44.2

Release published on the 2025-01-29 17:15:37 +0000 UTC at the url https://github.com/grafana/agent/releases/tag/v0.44.2

This is release `v0.44.2` of Grafana Agent.

### Upgrading

Read the relevant upgrade guides for specific instructions on upgrading from older versions:

* [Static mode upgrade guide](https://grafana.com/docs/agent/v0.44/static/upgrade-guide/)
* [Static mode Kubernetes operator upgrade guide](https://grafana.com/docs/agent/v0.44/operator/upgrade-guide/)
* [Flow mode upgrade guide](https://grafana.com/docs/agent/v0.44/flow/upgrade-guide/)

### Changes:

#### Bugfixes

- `loki.source.podlogs`: Fixed a bug which prevented clustering from working and caused duplicate logs to be sent.
  The bug only happened when no `selector` or `namespace_selector` blocks were specified in the Agent configuration. (@ptodev)

- `pyroscope.scrape` no longer tries to scrape endpoints which are not active targets anymore. (@wildum @mattdurham @dehaansa @ptodev)

#### Enhancements

- Upgrade `github.com/goccy/go-json` to v0.10.4, which reduces the memory consumption of an Agent instance by 20MB.
  If Agent is running certain otelcol components, this reduction will not apply. (@ptodev)
  
#### Other changes

- Remove setcap for `cap_net_bind_service` to allow Agent to run in restricted environments.
  Modern container runtimes allow binding to unprivileged ports as non-root. (@ptodev)

- Update to go 1.22.11 (@wildum)

### Installation

Note that Grafana Agent has been deprecated and is in Long-Term Support (LTS) through October 31, 2025. Grafana Agent will reach an End-of-Life (EOL) on November 1, 2025. Read more about why we recommend migrating to [Grafana Alloy](https://grafana.com/blog/2024/04/09/grafana-alloy-opentelemetry-collector-with-prometheus-pipelines/).

Refer to our installation guides for how to install the variants of Grafana Agent:

* [Install static mode](https://grafana.com/docs/agent/v0.44/static/set-up/install/)
* [Install the static mode Kubernetes operator](https://grafana.com/docs/agent/v0.44/operator/helm-getting-started/)
* [Install flow mode](https://grafana.com/docs/agent/v0.44/flow/setup/install/)

run kubectl when chart changed

ran shell command "rm -rf grafana/charts ksm/charts && kubectl kustomize . -o grafana-agent.yaml --enable-helm"

GitHub Action workflow link

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!