Hello, I'm trying to deploy a datahub via EKS. The...
# troubleshoot
n
Hello, I'm trying to deploy a datahub via EKS. The deployment was successful, but I am having difficulties using the load balancer. I followed this link(https://datahubproject.io/docs/deploy/aws#expose-endpoints-using-a-load-balancer) as-is and succeeded in deploying aws-load-balancer-controller. However, when creating an ELB, a classic load balancer, not an ALB, is created. I'm not sure what the problem is. I need help.
kubectl get deployment -n kube-system aws-load-balancer-controller
Copy code
NAME                           READY   UP-TO-DATE   AVAILABLE   AGE
aws-load-balancer-controller   2/2     2            2           26h
kubectl get ingress
Copy code
NAME                       CLASS    HOSTS                               ADDRESS   PORTS   AGE
datahub-datahub-frontend   <none>   <http://datahub-eks.example.com|datahub-eks.example.com>                       80      39m
values.yaml
Copy code
datahub-frontend:
  enabled: true
  image:
    repository: linkedin/datahub-frontend-react
    tag: "v0.8.41"
  # Set up ingress to expose react front-end
  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>: <<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: <http://datahub-eks.example.com|datahub-eks.example.com>
        redirectPaths:
          - path: /*
            name: ssl-redirect
            port: use-annotation
        paths:
          - /*
i
Hello Seongtae, Please refrain from multiple questions across channels and posting stack traces directly. Instead post the stack traces in the thread. It keeps channels cleaner and easier for the core team to help out. Thanks
Can you do a
kubectl get ingress datahub-datahub-frontend -o yaml
and share the output? obfuscate sensitive data as needed
The ingress does not seem well created as it has no address
b
Bump!