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
We have deployed ArgoCD on several AKS clusters using Helm and are currently migrating from Azure SSO to GitHub SSO. We have it working for one instance but after replicating the config for another argo instance we get an error when logging in Failed to query provider "https://argocd.argo.<domain>.com/api/dex": Get "https://argocd-dex-server:5556/api/dex/.well-known/openid-configuration": EOF. After checking the logs for the dex-server pod I saw that it was throwing some errors about failing to list some secrets in the same argo namespace because the connection was refused 1 reflector.go:424] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:169: failed to list *v1.Secret: Get "https://172.25.0.1:443/api/v1/namespaces/argocd/secrets?limit=500&resourceVersion=0": dial tcp 172.25.0.1:443: connect: connection refused
We're stuck trying to figure out where the disconnect could possibly be since our clusters are built through terraform and should be configured exactly the same except for some naming conventions. Just wondering if anyone else has seen anything similar.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We have deployed ArgoCD on several AKS clusters using Helm and are currently migrating from Azure SSO to GitHub SSO. We have it working for one instance but after replicating the config for another argo instance we get an error when logging in
Failed to query provider "https://argocd.argo.<domain>.com/api/dex": Get "https://argocd-dex-server:5556/api/dex/.well-known/openid-configuration": EOF
. After checking the logs for the dex-server pod I saw that it was throwing some errors about failing to list some secrets in the same argo namespace because the connection was refused1 reflector.go:424] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:169: failed to list *v1.Secret: Get "https://172.25.0.1:443/api/v1/namespaces/argocd/secrets?limit=500&resourceVersion=0": dial tcp 172.25.0.1:443: connect: connection refused
We're stuck trying to figure out where the disconnect could possibly be since our clusters are built through terraform and should be configured exactly the same except for some naming conventions. Just wondering if anyone else has seen anything similar.
Beta Was this translation helpful? Give feedback.
All reactions