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
When installing Flamingo using Helm (either by manually installing the Helm chart or running flamingo install --mode=helmrelease), the argocd-redis secret does not get created, leading to various pods not starting up with the following error:
Warning Failed 2s (x11 over 2m2s) kubelet Error: secret "argocd-redis" not found
Looking at the logs of the job that is supposed to create this secret, it seems like the command passed to the container doesn't actually exist.
Pod definition for argocd-redis-secret-init:
Logs of said pod:
I've tried with an image one version older, but this leads to the same result. Only way the install works is by running flamingo install without any arguments, but it would be nice if the Helm release option worked too so we can manage it as a Flux resource.
The text was updated successfully, but these errors were encountered:
the argocd cli seems to be older and not able to run command argocd admin redis-initial-password , i replaced the image in the job with one that has latest argocd cli, then the secret got created. Then i restarted all the pods in argocd namespace.
When installing Flamingo using Helm (either by manually installing the Helm chart or running flamingo install --mode=helmrelease), the argocd-redis secret does not get created, leading to various pods not starting up with the following error:
Looking at the logs of the job that is supposed to create this secret, it seems like the command passed to the container doesn't actually exist.
Pod definition for argocd-redis-secret-init:
Logs of said pod:
I've tried with an image one version older, but this leads to the same result. Only way the install works is by running
flamingo install
without any arguments, but it would be nice if the Helm release option worked too so we can manage it as a Flux resource.The text was updated successfully, but these errors were encountered: