alloy update to 2.0.16-bb.1

Package Merge Request

Package Changes

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

Package MR

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

For Issue

Closes #2530 (closed)

Upgrade Notices

Important: If Alloy package is enabled (addons.alloy.enabled set to true) in Big Bang values.yaml, upgrading to Alloy to 2.0.16-bb.1 requires migrating the Alloy package from the monitoring namespace to its own alloy namespace. Due to how Flux handles HelmRelease updates, some lingering resources will not be automatically removed. These resources must be deleted manually or through automation.

The Alloy autoRollingUpgrade feature provides an automated upgrade job that deletes any resources with the helm.toolkit.fluxcd.io/name=alloy label in the monitoring namespace. This migration process completely removes Alloy from the monitoring namespace and performs a clean installation in the new alloy namespace.

The autoRollingUpgrade.enabled is set to true by default in the Alloy values.yaml in which case, no additional action is required. However, a brief outage is expected during the upgrade as the Alloy migration is applied.

If you prefer to disable the upgrade job and manually complete the pre-upgrade steps, set addons.alloy.values.autoRollingUpgrade.enabled=false in Big Bang values.yaml and follow the steps outlined below. The following commands assume that the Alloy package is deployed in the default Big Bang monitoring namespace. Verify the namespace of your Alloy deployment before proceeding.

Pre-Upgrade Steps

1. Suspend the Flux Reconciliation of Alloy Helm Release

flux -n bigbang suspend helmrelease alloy

2. Delete the resources with the helm.toolkit.fluxcd.io/name=alloy label in the monitoring namespace

kubectl api-resources --verbs=list --namespaced -o name | awk 'NF' | xargs -r -n 1 kubectl get --show-kind --ignore-not-found -l helm.toolkit.fluxcd.io/name=alloy -n monitoring 2>/dev/null | awk 'NR>1 {print $1}' | grep -E '^[^/]+/[^/]+$' | grep -v '^endpointslice.discovery.k8s.io/' | xargs -r -I {} kubectl delete {} -n monitoring

Upgrade Big Bang

1. Verify that addons.alloy.values.autoRollingUpgrade.enabled=false is set in Big Bang to prevent the Alloy upgrade job from running

2. Upgrade Big Bang and wait until packages have been upgraded and verify that Alloy Helm Release has been upgrade

3. Resume Flux reconciliation of Alloy Helm Release

flux -n bigbang resume helmrelease alloy