Redis issues with IPV6 disabled cluster

[MikeK184]

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.
• I've pasted the output of argocd version.

Describe the bug

After upgrading to v2.0.3 the deployment.apps/argocd-redis was failing to successfully create the redis pod because it wasn't able to bind the socket. A similar issue for the HA version was raised in this #5957

To Reproduce

Deploy non-ha ArgoCD v2.0.3 to a Kubernetes cluster (TKGI) with IPv6 disabled.

Expected behavior

Redis pod to successfully bind the socket.

Logs

# Could not create server TCP listening socket ::*:6379: unable to bind socket, errno: 97

Workaround

I had to manually add --bind 0.0.0.0 to the args of the argocd-redis deployment
https://github.com/argoproj/argo-cd/blob/master/manifests/install.yaml#L3099-L3105

[jkleinlercher]

Found lots of issues regarding redis and binding issues with IPv6 disabled. Last one was redis/docker-library-redis#273

maybe redis solves this issue with 6.2.2 as also mentioned in argoproj/argo-helm#700
and redis/redis#8655

When will argocd switch to redis 6.2.2 officially?

[jannfis]

Thanks for the heads up regarding the bug being fixed in a more recent version. It seems to be indeed true, from the Changelog:

• Fix not starting on alpine/libmusl without IPv6 (Add snyk container test check to CI #8655)

Looking further at the Changelog, Redis reached 6.2.4 meanwhile with some important fixes. So probably worthwhile to include an update to 6.2.4 in the next patch release of Argo CD v2.0 branch.