Hey, following guide about deploying on eks: https://datahubproject.io/docs/deploy/aws/ I added my subdomain and replaced values for

datahub-frontend

datahub-frontend:
  enabled: true
  image:
    repository: linkedin/datahub-frontend-react
    tag: "latest"
  ingress:
    enabled: true
    annotations:
      <http://kubernetes.io/ingress.class|kubernetes.io/ingress.class>: alb
      <http://alb.ingress.kubernetes.io/scheme|alb.ingress.kubernetes.io/scheme>: internet-facing
      <http://alb.ingress.kubernetes.io/target-type|alb.ingress.kubernetes.io/target-type>: instance
      <http://alb.ingress.kubernetes.io/certificate-arn|alb.ingress.kubernetes.io/certificate-arn>: <<my-certificate-arn>>
      <http://alb.ingress.kubernetes.io/inbound-cidrs|alb.ingress.kubernetes.io/inbound-cidrs>: 0.0.0.0/0
      <http://alb.ingress.kubernetes.io/listen-ports|alb.ingress.kubernetes.io/listen-ports>: '[{"HTTP": 80}, {"HTTPS":443}]'
      <http://alb.ingress.kubernetes.io/actions.ssl-redirect|alb.ingress.kubernetes.io/actions.ssl-redirect>: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "StatusCode": "HTTP_301"}}'
    hosts:
      - host: <<my-ost-name>>
        redirectPaths:
          - path: /*
            name: ssl-redirect
            port: use-annotation
        paths:
          - /*

Ofc, I replaced my arn and host. When I added this config and I tried to reach through my subdomain, I get blank page after providing credentials. Subdomain is loading fine which means that traffic is correctly routed. But for some reason I see blank page. Did you experience a similar issue? If not, are these values ones that should be used when exposing frontend on EKS?

Cc @orange-night-91387 . I feel like we've seen this before on AWS but I cannot quite recall why

Hmm so this config looks pretty much the same as our working examples, only thing different are annotations for setting external dns routing. What's going on in the network logs in your browser? Can you see what requests are going out and where they're routed to? Most of the time this was happening it was people deploying with an old version

*[master][~/Desktop/dev]$ kubectl get ingress
NAME                       CLASS    HOSTS                 ADDRESS                                                                 PORTS   AGE
datahub-datahub-frontend   <none>   <my domain>           <my address>                                                            80      26m

Seems that it's configured to hit port 80. Do you know how can I change to 9002?

same issue here, same config. Any idea on this?

Hey there! 👋 Make sure your message includes the following information if relevant, so we can help more effectively! 1. Which DataHub version are you using? (e.g. 0.12.0) 2. Please post any relevant error logs on the thread!