Hide
Currently there is a known issue where upgrading the operator from versions prior to 1.17.z, the redis-ha-haproxy deployment does not automatically scale to 3 replicas after the upgrade. This occurs specifically when HA mode was enabled before upgrading to version 1.17.z.
Workaround: Manually scale the redis-ha-haproxy deployment to match the replica count
oc scale deployment <argocd instance>-redis-ha-haproxy -n <argocd namespace> --replicas=3
Show
Currently there is a known issue where upgrading the operator from versions prior to 1.17.z, the redis-ha-haproxy deployment does not automatically scale to 3 replicas after the upgrade. This occurs specifically when HA mode was enabled before upgrading to version 1.17.z.
Workaround: Manually scale the redis-ha-haproxy deployment to match the replica count
oc scale deployment <argocd instance>-redis-ha-haproxy -n <argocd namespace> --replicas=3