Fix Redis service hostname after redis-bb subchart upgrade
General MR
Summary
Fix release cluster testing issue: tcp: lookup argocd-argocd-redis-bb-headless.argocd.svc.cluster.local on 10.100.0.10:53: no such host
- Corrects the Redis headless service hostname in ArgoCD configuration following the breaking change introduced in Redis subchart upgrade from
21.2.9-bb.0to22.0.4-bb.1 - Updates
upstream.externalRedis.hostfromargocd-argocd-redis-bb-headless.argocd.svc.cluster.localtoredis-bb-headless.argocd.svc.cluster.local
Problem
The Redis BigBang wrapper chart version 22.0.4-bb.1 introduced explicit name overrides (fullnameOverride: "redis-bb"), which changed the generated service name from argocd-argocd-redis-bb-headless to
redis-bb-headless. The ArgoCD configuration was still pointing to the old service name, causing connection failures.
Changes
-
chart/values.yaml: Updatedupstream.externalRedis.hostto use the correct service name -
chart/Chart.yaml: Bumped version to8.3.4-bb.1
Testing
-
Verified Redis service is accessible at the new hostname -
Confirmed ArgoCD can connect to Redis -
Tested upgrade path from previous version
Impact
This is a required fix for anyone using the BigBang ArgoCD package with the embedded Redis subchart. Without this change, ArgoCD cannot connect to its Redis backend.
Relevant logs/screenshots
Confirmed working by release team:
Linked Issue
Upgrade Notices
N/A
Edited by Matt Vasquez
