Ingress Issue with DataHub on GKE Cluster with TLS Enabled

[Squallman]

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:

1. Deploy DataHub on a GKE cluster with TLS enabled using Helm:

   helm install my-datahub datahub/datahub --version 0.4.16 --set datahub-frontend.ingress.enabled=true
   

2. Access the DataHub URL in a web browser:

   https://<datahub_frontend_url>/logIn
   

3. Observe the error indicating that the login path cannot be fetched.

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

curl -vv --cacert /tmp/ca.crt --request POST \
  --url https://<datahub-frontend-url>/logIn \
  --header 'Content-Type: application/json' \
  --header 'User-Agent: insomnia/8.1.0' \
  --data '{"username": "datahub", "password": "datahub"}'

< HTTP/2 404
< date: Wed, 03 Apr 2024 14:21:20 GMT
< content-length: 74
< content-type: text/plain; charset=utf-8
< via: 1.1 google
< alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
<
response 404 (backend NotFound), service rules for the path non-existent 

Additional context Helm Chart Version: 0.4.16 TLS Configuration: Enabled with a valid certificate. The issue appears to be related to the pathType: ImplementationSpecific setting, which may not be compatible with the way DataHub handles routing for the login path. Using pathType: Prefix or a different pathType may resolve the issue.