Update Ironbank

This MR contains the following updates:

Package	Update	Change
bb-common	patch	0.14.1 -> 0.14.2
gluon	major	0.9.8 -> 1.0.0
k8s-monitoring	major	3.8.4 -> 4.0.1
registry1.dso.mil/ironbank/opensource/grafana/alloy (source)	minor	v1.14.0 -> v1.15.0
registry1.dso.mil/ironbank/opensource/grafana/alloy (source)	minor	1.14.0 -> 1.15.0
registry1.dso.mil/ironbank/opensource/prometheus-operator/prometheus-config-reloader (source)	minor	v0.89.0 -> v0.90.1

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

Umbrella branch

alloy-134/renovate

Add supporting info below

issue

Reviewer only

• Tested and Validated changes

---

Release Notes

grafana/helm-charts (k8s-monitoring)

v4.0.1

Compare Source

Capture all telemetry data from your Kubernetes cluster.

Source commit: https://github.com/grafana/k8s-monitoring-helm/commit/8ee0514fc8f68ec431d014d93b6355c610f3899b

Tag on source: https://github.com/grafana/k8s-monitoring-helm/releases/tag/k8s-monitoring-4.0.1

v4.0.0

Compare Source

Capture all telemetry data from your Kubernetes cluster.

Source commit: https://github.com/grafana/k8s-monitoring-helm/commit/975f474ea6cae5b65d5545fe18e16acc53dec168

Tag on source: https://github.com/grafana/k8s-monitoring-helm/releases/tag/k8s-monitoring-4.0.0

v3.8.6

Compare Source

Capture all telemetry data from your Kubernetes cluster.

Source commit: https://github.com/grafana/k8s-monitoring-helm/commit/8467687f85a9de8cf3ae6c30eeb97bee7f11fd2c

Tag on source: https://github.com/grafana/k8s-monitoring-helm/releases/tag/k8s-monitoring-3.8.6

v3.8.5

Compare Source

Capture all telemetry data from your Kubernetes cluster.

Source commit: https://github.com/grafana/k8s-monitoring-helm/commit/a8c345db687911f19769f7bc801e21eac1c19c19

Tag on source: https://github.com/grafana/k8s-monitoring-helm/releases/tag/k8s-monitoring-3.8.5

---

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

The Alloy package has been upgraded from upstream k8s-monitoring 3.8.4 to 4.0.1. This release includes breaking upstream values changes for log collection and destinations.

If you provide custom alloy.values.upstream overrides, review and update them before upgrading:

• upstream.podLogs has been replaced by upstream.podLogsViaLoki for Loki-format pod log collection.
• upstream.destinations now uses a map/object keyed by destination name instead of a list of destination objects.
• Collector definitions now belong under upstream.collectors. In k8s-monitoring 4.x, collectors are explicitly configured and paired with presets such as deployment, singleton, daemonset, and filesystem-log-reader.
• Features that use more than one collector should explicitly set collector, for example clusterEvents.collector: alloy-singleton, podLogsViaLoki.collector: alloy-logs, and applicationObservability.collector: alloy-receiver

Examples:

• Old:

    alloy:
      values:
        upstream:
          destinations:
            - name: loki
              type: loki
              url: http://logging-loki-write.logging.svc.cluster.local:3100/loki/api/v1/push
          podLogs:
            enabled: true
            destinations:
              - loki
            collector: alloy-logs

• New:

    alloy:
      values:
        upstream:
          destinations:
            loki:
              type: loki
              url: http://logging-loki-write.logging.svc.cluster.local:3100/loki/api/v1/push
          podLogsViaLoki:
            enabled: true
            destinations:
              - loki
            collector: alloy-logs

Upstream 4.0 also removed the old labelsToKeep-based pod log behavior as part of its log feature refactor. Review any custom pod log processing overrides for compatibility with k8s-monitoring 4.0.x.

Upgrade tool

Grafana has published a values conversion tool to use to update your values to the newest version: https://grafana.github.io/k8s-monitoring-helm-migrator/