You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an weird issue where redis-secret-init keeps looping.
I installed ArgoCD using the helm chart "7.8.2", app version "2.14.2+" including a values file. redis-secret-init runs once succeeds and is later removed. Everything is working as expected.
I then applied an app-of-apps that watches a dir with an ApplicationSet configured with platform services helm charts, including Argo CD. After this, the redis-secret-init runs, succeeds, and runs again and again preventing Argo CD from completing a successful sync upon itself.
I uninstalled Argo CD and reinstalled with Helm Chart version "7.7.5" app version "2.13.1" and Argo CD synced itself as expected, however, after reading this I don't know whether this broke in 2.14.x or if I just happened to win the race condition when installing "2.13.1". Here is another potentially related issue.
This issue was reported last week by Rune on Slack. The information below is from that post. It reflects what we are seeing:
The job, argocd-redis-secret-init itself exits "ok":
Checking for initial Redis password in secret argocd/argocd-redis at key auth.
Argo CD Redis secret state confirmed: secret name argocd-redis.
Password secret is configured properly.
kubectl describe jobs argocd-redis-secret-init -n argocd returns:
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal SuccessfulCreate 3s job-controller Created pod: argocd-redis-secret-init-67n49
Normal Completed 0s job-controller Job completed
Complete output of above command:
Name: argocd-redis-secret-init
Namespace: argocd
Selector: batch.kubernetes.io/controller-uid=19b7598c-c830-4c0b-a5c4-c955f97e42e9
Labels: app.kubernetes.io/component=redis-secret-init
app.kubernetes.io/instance=argocd
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=argocd-redis-secret-init
app.kubernetes.io/part-of=argocd
app.kubernetes.io/version=v2.14.2
argocd.argoproj.io/instance=argocd
helm.sh/chart=argo-cd-7.8.2
Annotations: argocd.argoproj.io/tracking-id: argocd:batch/Job:argocd/argocd-redis-secret-init
helm.sh/hook: pre-install,pre-upgrade
helm.sh/hook-delete-policy: before-hook-creation
Parallelism: 1
Completions: 1
Completion Mode: NonIndexed
Suspend: false
Backoff Limit: 6
TTL Seconds After Finished: 60
Start Time: Tue, 25 Feb 2025 15:22:47 +0100
Completed At: Tue, 25 Feb 2025 15:22:50 +0100
Duration: 3s
Pods Statuses: 0 Active (0 Ready) / 1 Succeeded / 0 Failed
Pod Template:
Labels: app.kubernetes.io/component=redis-secret-init
app.kubernetes.io/instance=argocd
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=argocd-redis-secret-init
app.kubernetes.io/part-of=argocd
app.kubernetes.io/version=v2.14.2
batch.kubernetes.io/controller-uid=19b7598c-c830-4c0b-a5c4-c955f97e42e9
batch.kubernetes.io/job-name=argocd-redis-secret-init
controller-uid=19b7598c-c830-4c0b-a5c4-c955f97e42e9
helm.sh/chart=argo-cd-7.8.2
job-name=argocd-redis-secret-init
Service Account: argocd-redis-secret-init
Containers:
secret-init:
Image: quay.io/argoproj/argocd:v2.14.2
Port: <none>
Host Port: <none>
SeccompProfile: RuntimeDefault
Command:
argocd
admin
redis-initial-password
Environment: <none>
Mounts: <none>
Volumes: <none>
Node-Selectors: kubernetes.io/os=linux
Tolerations: <none>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal SuccessfulCreate 4s job-controller Created pod: argocd-redis-secret-init-4w4bk
Normal Completed 1s job-controller Job completed
To Reproduce
See description above
Expected behavior
Able to create an Application/ApplicationSet that configures Argo CD to enforce GitOps upon itself.
Version
helm chart "7.8.2", app version "2.14.2+"
Logs
See above.
The text was updated successfully, but these errors were encountered:
Checklist:
argocd version
.Describe the bug
I have an weird issue where redis-secret-init keeps looping.
I installed ArgoCD using the helm chart "7.8.2", app version "2.14.2+" including a values file. redis-secret-init runs once succeeds and is later removed. Everything is working as expected.
I then applied an app-of-apps that watches a dir with an ApplicationSet configured with platform services helm charts, including Argo CD. After this, the redis-secret-init runs, succeeds, and runs again and again preventing Argo CD from completing a successful sync upon itself.
I uninstalled Argo CD and reinstalled with Helm Chart version "7.7.5" app version "2.13.1" and Argo CD synced itself as expected, however, after reading this I don't know whether this broke in 2.14.x or if I just happened to win the race condition when installing "2.13.1". Here is another potentially related issue.
This issue was reported last week by Rune on Slack. The information below is from that post. It reflects what we are seeing:
The job, argocd-redis-secret-init itself exits "ok":
Checking for initial Redis password in secret argocd/argocd-redis at key auth.
Argo CD Redis secret state confirmed: secret name argocd-redis.
Password secret is configured properly.
kubectl describe jobs argocd-redis-secret-init -n argocd
returns:To Reproduce
See description above
Expected behavior
Able to create an Application/ApplicationSet that configures Argo CD to enforce GitOps upon itself.
Version
helm chart "7.8.2", app version "2.14.2+"
Logs
See above.
The text was updated successfully, but these errors were encountered: