## Bug Description The BigBang Loki package `6.55.0-bb.1` appears to have an image version mismatch. While testing a BigBang `3.24.0` upgrade in an air-gapped/Zarf-based environment, Loki failed to start with `ImagePullBackOff` because the rendered Loki workload used image tag `3.6.7`, while the package metadata advertises Loki `3.7.1`. Evidence from the chart artifact: ```yaml # Chart.yaml appVersion: 3.7.1 annotations: bigbang.dev/applicationVersions: - Loki: 3.7.1 bigbang.dev/images: - image: registry1.dso.mil/ironbank/opensource/grafana/loki:3.7.1 ``` ```yaml # values.yaml loki: image: registry: registry1.dso.mil repository: ironbank/opensource/grafana/loki tag: 3.6.7 ``` In our air-gapped deployment, this caused the Zarf bundle/package process to include `loki:3.7.1`, while Helm rendered the workload with `loki:3.6.7`. The pod then attempted to pull `3.6.7` from the local registry, where only `3.7.1` existed. Observed pod error: ```text Failed to pull image "127.0.0.1:31999/ironbank/opensource/grafana/loki:3.6.7-zarf-...": not found ``` We worked around this locally by explicitly overriding: ```yaml loki: image: tag: 3.7.1 ``` ## Steps to Reproduce 1. Deploy BigBang `3.24.0` with Loki package `6.55.0-bb.1`. 2. Do not explicitly override `loki.image.tag`. 3. Inspect the rendered Loki pod or StatefulSet. 4. Observe that the main Loki container uses `loki:3.6.7` even though the chart metadata advertises `3.7.1`. Example check: ```bash kubectl -n logging describe pod logging-loki-0 ``` Observed: ```text zarf.dev/original-image-loki: registry1.dso.mil/ironbank/opensource/grafana/loki:3.6.7 Image: 127.0.0.1:31999/ironbank/opensource/grafana/loki:3.6.7-zarf-... ``` ## BigBang Version BigBang version: ```text 3.24.0 ``` Loki package version: ```text 6.55.0-bb.1 ``` From the deployed cluster: ```text bigbang/loki GitRepository revision: 6.55.0-bb.1@sha1:03718f1e0ebd9c1eda2fabada68e196c94193f30 ```