SKIP UPDATE CHECK Update Ironbank

This MR contains the following updates:

Package	Update	Change
gluon	patch	0.5.18 -> 0.6.2
k8s-monitoring	minor	2.0.27 -> 2.1.4
registry1.dso.mil/ironbank/opensource/prometheus-operator/prometheus-config-reloader (source)	patch	v0.82.1 -> v0.82.2

Umbrella Branch

alloy-renovate-test-20250624

Complete MR checklist

Assignee

• Followed upgrade instructions outlined in docs/DEVELOPMENT_MAINTENANCE.md
• Update Docs with new/updated steps as needed
• Tested and Validated Changes made with supporting info like logs or screenshots from test pipelines

Add supporting info below

Reviewer only

• Tested and Validated changes

❗ Important

Release Notes retrieval for this MR were skipped because no github.com credentials were available. If you are self-hosted, please see this instruction.

---

Configuration

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

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

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This MR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this MR, check this box

---

This MR was automatically generated by Renovate Bot.

Upgrade Notices

Alloy Operator

v3 introduces the use of the Alloy Operator to manage the creation and lifecycle of Alloy instances. When upgrading from v2.0 to v3.0 or later, you may need to install the Alloy CRD.

To do this, run the following command:

kubectl apply -f https://github.com/grafana/alloy-operator/releases/latest/download/collectors.grafana.com_alloy.yaml

Pod Logs

v3 also moves the pod and k8s.pod.name fields from labels to structured metadata in the pod logs feature. If your logs destination does not support structured metadata, you may not see these labels on your logs.

(Note: we have overridden these changes to keep the pod and k8s.pod.name labels available as they are currently required for the Big Bang Loki Grafana dashboards)

Service Monitors

Due to an inability to use post-renderers on resources managed by the new Alloy Operator, Service Monitors are now defined at the root level in chart/values.yaml and managed by the chart/templates/bigbang/servicemonitor.yaml template.