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 agree to follow the Code of Conduct that this project adheres to.
I have searched the issue tracker for an issue that matches the one I want to file, without success.
I am not looking for support or already pursued the available support channels without success.
Chart
dex
Version
0.17.1
Expected Behavior
I expect Dex and Argo Workflows to communicate with each other within the same EKS cluster. Both services have ingress configurations set up, but Argo Workflows cannot recognize Dex through the ingress URL.
Actual Behavior
Actual Behavior:
Despite having ingress set up for both Dex and Argo Workflows, Argo Workflows is unable to communicate with Dex. It throws the following error:
time="2024-06-10T10:25:41.991Z" level=info msg="not enabling pprof debug endpoints"
time="2024-06-10T10:25:41.992Z" level=info authModes="[sso]" baseHRef=/ managedNamespace= namespace=clearing secure=false ssoNamespace=clearing
time="2024-06-10T10:25:41.992Z" level=warning msg="You are running in insecure mode. Learn how to enable transport layer security: https://argo-workflows.readthedocs.io/en/release-3.5/tls/"
Error: Get "https://dex-tester.dev/.well-known/openid-configuration": dial tcp: lookup dex.tester.dev on 172.20.0.10:53: no such host
Steps To Reproduce
Deploy Dex and Argo Workflows on an EKS cluster.
Set up ingress for both Dex and Argo Workflows.
Attempt to configure Argo Workflows to use Dex for SSO authentication with ingress URL.
Additional Information
I have verified that the DNS resolution within the cluster is working correctly for other services, but dex.tester.dev cannot be resolved. The ingress for Dex is accessible externally, but Argo Workflows cannot seem to communicate with it.
I suspect there might be an issue with the health check path or the ingress configuration that is preventing Argo Workflows from resolving Dex.
Any help or guidance on resolving this issue would be greatly appreciated.
Preflight Checklist
Chart
dex
Version
0.17.1
Expected Behavior
I expect Dex and Argo Workflows to communicate with each other within the same EKS cluster. Both services have ingress configurations set up, but Argo Workflows cannot recognize Dex through the ingress URL.
Actual Behavior
Actual Behavior:
Despite having ingress set up for both Dex and Argo Workflows, Argo Workflows is unable to communicate with Dex. It throws the following error:
Steps To Reproduce
Additional Information
I have verified that the DNS resolution within the cluster is working correctly for other services, but dex.tester.dev cannot be resolved. The ingress for Dex is accessible externally, but Argo Workflows cannot seem to communicate with it.
I suspect there might be an issue with the health check path or the ingress configuration that is preventing Argo Workflows from resolving Dex.
Any help or guidance on resolving this issue would be greatly appreciated.
Values
The text was updated successfully, but these errors were encountered: