Closed Squallman closed 2 weeks ago
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io
This issue was closed because it has been inactive for 30 days since being marked as stale.
Describe the bug After installing DataHub using Helm on a GKE cluster with TLS enabled, attempting to log in through the
<datahub_frontend_url>/logIn
path results in an error. The Ingress resource with pathType:ImplementationSpecific
does not correctly route to the/logIn
endpoint, causing the login page to be inaccessible.To Reproduce Steps to reproduce the behavior:
Expected behavior Upon navigating to
<datahub_url>/logIn
, the DataHub login page should be accessible, and users should be able to log in without encountering any routing issues.Screenshots
Additional context Helm Chart Version:
0.4.16
TLS Configuration: Enabled with a valid certificate. The issue appears to be related to thepathType
:ImplementationSpecific
setting, which may not be compatible with the way DataHub handles routing for the login path. UsingpathType
:Prefix
or a different pathType may resolve the issue.