Failure to init - helm chart 7.8.5 and argocd 2.14.8 #3234
Description
Describe the bug
When installing the helm chart, the init container fails to access the api
Related helm chart
argo-cd
Helm chart version
7.8.5
To Reproduce
helm install argo-cd effectively
Expected behavior
init container gets/creates the secret.
Screenshots
k logs -n argocd argo-cd-argocd-redis-secret-init-kssdg ─╯
Checking for initial Redis password in secret argocd/argocd-redis at key auth.
time="2025-04-02T12:15:57Z" level=fatal msg="Post \"https://10.43.0.1:443/api/v1/namespaces/argocd/secrets\": dial tcp 10.43.0.1:443: i/o timeout"
Name: argo-cd-argocd-redis-secret-init-kssdg
Namespace: argocd
Priority: 0
Service Account: argo-cd-argocd-redis-secret-init
Node: dpi03/172.17.2.169
Start Time: Wed, 02 Apr 2025 08:14:11 -0400
Labels: app.kubernetes.io/component=redis-secret-init
app.kubernetes.io/instance=argo-cd
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.8
batch.kubernetes.io/controller-uid=e32ca979-3122-4fcc-b06a-248d175f80eb
batch.kubernetes.io/job-name=argo-cd-argocd-redis-secret-init
controller-uid=e32ca979-3122-4fcc-b06a-248d175f80eb
helm.sh/chart=argo-cd-7.8.15
job-name=argo-cd-argocd-redis-secret-init
Annotations: <none>
Status: Running
IP: 10.42.5.3
IPs:
IP: 10.42.5.3
Controlled By: Job/argo-cd-argocd-redis-secret-init
Containers:
secret-init:
Container ID: containerd://4e6da1a69b8d2e9dae06b9db463a65fa7d5e2835b375bee77f3a436081c9efa8
Image: quay.io/argoproj/argocd:v2.14.8
Image ID: quay.io/argoproj/argocd@sha256:a5ed1e6cef908ce9f3ba45c1bd2cc68e911b5be223f480d8e20ab38fcee9b2e7
Port: <none>
Host Port: <none>
SeccompProfile: RuntimeDefault
Command:
argocd
admin
redis-initial-password
State: Running
Started: Wed, 02 Apr 2025 08:16:22 -0400
Last State: Terminated
Reason: Error
Exit Code: 20
Started: Wed, 02 Apr 2025 08:15:26 -0400
Finished: Wed, 02 Apr 2025 08:15:57 -0400
Ready: True
Restart Count: 3
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-kkb7j (ro)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
kube-api-access-kkb7j:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: kubernetes.io/os=linux
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 2m33s default-scheduler Successfully assigned argocd/argo-cd-argocd-redis-secret-init-kssdg to dpi03
Warning BackOff 38s (x3 over 91s) kubelet Back-off restarting failed container secret-init in pod argo-cd-argocd-redis-secret-init-kssdg_argocd(6bb140de-cf67-4b06-9f11-3838fdf7c332)
Normal Pulled 23s (x4 over 2m33s) kubelet Container image "quay.io/argoproj/argocd:v2.14.8" already present on machine
Normal Created 23s (x4 over 2m33s) kubelet Created container: secret-init
Normal Started 23s (x4 over 2m33s) kubelet Started container secret-initAdditional context
No response
Activity
jurlwin commentedon Apr 2, 2025
one strange note ... I ran this same set of instructions and same setup on an x86 cluster, created with the same version of k3s ... and it all worked. Only in this cluster, on arm64 it didnt.
x86: ubuntu 24.04.2 LTS, k3s 1.32.3.+k3s1
arm64: raspbian bookworm, k3s 1.32.3+k3s1
This is the first thing I'm trying to install in the clusters, post the initial setup scripts which have kube-vip and metallb, which I don't think are in the way here.
github-actions commentedon Jun 3, 2025
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.