alloy update to 4.0.1-bb.0

Package Merge Request

Package Changes

https://repo1.dso.mil/big-bang/product/packages/alloy/-/blob/4.0.1-bb.0/CHANGELOG.md

Package MR

big-bang/product/packages/alloy!154 (merged)

For Issue

Closes big-bang/product/packages/alloy#134

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.

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/