Update Grafana Agent Operator version

[argoyle]

GRAFANA.YAML

Bump Operator module version

changes detected: path "locals.version" updated from "0.42.0" to "0.43.0" in file "locals.tf"

v0.43.0

Release published on the 2024-09-11 18:37:34 +0000 UTC at the url https://github.com/grafana/agent/releases/tag/v0.43.0

This is release `v0.43.0` 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.43/static/upgrade-guide/)
* [Static mode Kubernetes operator upgrade guide](https://grafana.com/docs/agent/v0.43/operator/upgrade-guide/)
* [Flow mode upgrade guide](https://grafana.com/docs/agent/v0.43/flow/upgrade-guide/)

### Changes:

#### Bugfixes

- Fix a memory leak which would occur any time `loki.process` had its configuration reloaded. (@ptodev)

- Fix a bug where custom components would not shadow the stdlib. If you have a module whose name conflicts with an stdlib function 
  and if you use this exact function in your config, then you will need to rename your module. (@wildum)

- Fix an issue where nested import.git config blocks could conflict if they had the same labels. (@wildum)

- Fix an issue where `loki.source.docker` stops collecting logs after a container restart. (@wildum)

#### Other changes

- Change the Docker base image for Linux containers to `ubuntu:noble`. (@amontalban)

### Installation

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

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

bump chart version

change detected: * key "$.helmCharts[0].version" updated from "'0.4.1'" to "'0.4.2'", in file "grafana/kustomization.yaml"

0.4.2

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

Helm Chart: grafana-agent-operator
A Helm chart for Grafana Agent Operator
Project Home: https://grafana.com/docs/agent/v0.43/

Version created on the 2024-09-11 19:33:44.325447884 +0000 UTC

Sources:

* https://github.com/grafana/agent/tree/v0.43.0/static/operator



URL:

* https://github.com/grafana/helm-charts/releases/download/grafana-agent-operator-0.4.2/grafana-agent-operator-0.4.2.tgz

Bump Agent image version

changes detected: path "locals.agent_version" updated from "0.42.0" to "0.43.0" in file "locals.tf"

v0.43.0

Release published on the 2024-09-11 18:37:34 +0000 UTC at the url https://github.com/grafana/agent/releases/tag/v0.43.0

This is release `v0.43.0` 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.43/static/upgrade-guide/)
* [Static mode Kubernetes operator upgrade guide](https://grafana.com/docs/agent/v0.43/operator/upgrade-guide/)
* [Flow mode upgrade guide](https://grafana.com/docs/agent/v0.43/flow/upgrade-guide/)

### Changes:

#### Bugfixes

- Fix a memory leak which would occur any time `loki.process` had its configuration reloaded. (@ptodev)

- Fix a bug where custom components would not shadow the stdlib. If you have a module whose name conflicts with an stdlib function 
  and if you use this exact function in your config, then you will need to rename your module. (@wildum)

- Fix an issue where nested import.git config blocks could conflict if they had the same labels. (@wildum)

- Fix an issue where `loki.source.docker` stops collecting logs after a container restart. (@wildum)

#### Other changes

- Change the Docker base image for Linux containers to `ubuntu:noble`. (@amontalban)

### Installation

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

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

Bump Operator image version

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

v0.43.0

Release published on the 2024-09-11 18:37:34 +0000 UTC at the url https://github.com/grafana/agent/releases/tag/v0.43.0

This is release `v0.43.0` 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.43/static/upgrade-guide/)
* [Static mode Kubernetes operator upgrade guide](https://grafana.com/docs/agent/v0.43/operator/upgrade-guide/)
* [Flow mode upgrade guide](https://grafana.com/docs/agent/v0.43/flow/upgrade-guide/)

### Changes:

#### Bugfixes

- Fix a memory leak which would occur any time `loki.process` had its configuration reloaded. (@ptodev)

- Fix a bug where custom components would not shadow the stdlib. If you have a module whose name conflicts with an stdlib function 
  and if you use this exact function in your config, then you will need to rename your module. (@wildum)

- Fix an issue where nested import.git config blocks could conflict if they had the same labels. (@wildum)

- Fix an issue where `loki.source.docker` stops collecting logs after a container restart. (@wildum)

#### Other changes

- Change the Docker base image for Linux containers to `ubuntu:noble`. (@amontalban)

### Installation

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

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

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!