argocd-redis secret-init initcontainer timeout about argo-cd

[otakakot]

I also encountered the same phenomenon by following stable, installed v2.11.0 and rolled back.

kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v2.11.0/manifests/install.yaml 

[liron-telemessage]

Hi,
The issue is that Argocd tries to create a secret for Redis via Kubernetes API.
the current network policy does not allow Argocd Redis sever to even contact the Kubernetes API.
as a workaround we temporarily changed the network policy for redis: argocd-redis-network-policy:
and changed to pod selector:
podSelector:
matchLabels:
app.kubernetes.io/name: argocd-redis

change the selector to something like app.kubernetes.io/name: argocd-redis-tmp

after that delete the Redis pod, it will now be able to create the secret and the system will start running.
once everything is running, revert the network policy selector (remove "-tmp").

[Tomasz-Marciniak]

Download install.yaml and add Kubernetes API port (in my case 16443) to network policy:

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: argocd-redis-network-policy
spec:
  egress:
    - ports:
        - port: 53
          protocol: UDP
        - port: 53
          protocol: TCP
        - port: 16443
          protocol: TCP

[sirTangale]

issue persist in helm install

[mkilchhofer]

issue persist in helm install

@sirTangale Can you raise an issue in argo-helm, please? 😃

Also I'd like to mention that the helm chart is handling it slightly different (via a helm hook). Before Helm will deploy the core components of Argo CD (server / repo-server / ...), Helm will wait until the Secret is generated (the Job runs to completion without errors).

I highly appreciate detailed steps to reproduce.

[otherguy]

Same here, also rolled back to 2.11.0

[NAVRockClimber]

Same here

[yyzxw]

same here, fixed by #18358

[RispyCZ]

I have same issue with argocd-redis-ha-haproxy

[ftmiro]

We faced the same problem and also patched the argocd-redis-ha-proxy-network-policy NetworkPolicy as workaround:

  - ports:
    - port: 443
      protocol: TCP

[ojasgo]

In my case I had to use v2.11.0 and also update NetworkPolicy as above mentioned.

[ngaxavi]

i had the same issue and patched the argocd-redis-network-policy Networkpolicy as @Tomasz-Marciniak suggested.

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: argocd-redis-network-policy
spec:
  egress:
    - ports:
        - port: 53
          protocol: UDP
        - port: 53
          protocol: TCP
        - port: 6443 # your kubernetes api port
          protocol: TCP
  ingress:
    - from:
        - podSelector:
            matchLabels:
              app.kubernetes.io/name: argocd-server
        - podSelector:
            matchLabels:
              app.kubernetes.io/name: argocd-repo-server
        - podSelector:
            matchLabels:
              app.kubernetes.io/name: argocd-application-controller
      ports:
        - port: 6379
          protocol: TCP
  podSelector:
    matchLabels:
      app.kubernetes.io/name: argocd-redis
  policyTypes:
    - Ingress
    - Egress
    

[sambonbonne]

I think I had the same issue on 2.11.1 (after an upgrade from 2.10) and the upgrade to 2.11.2 fixed it for me.

[pasha-codefresh]

Fixed in 2.11.2