Expose Kibana externally using NLB with AWS LoadBalancer Controller

Hi,

I am following this guide to have ECK then Elastic Search and Kibana installed on EKS.

Everything is just fine, I have Kabana up and run with port-forwarding as documented, however when I expose the service with type LoadBalancer I cannot access to my kibana. Please notice that I am using EKS and AWS LoadBalancer Controller which provisions a service typed LoadBalancer to a NLB, and an Ingress to ALB. In my case, I see a NLB provisioned on AWS but I cannot access the service via the dns name.

apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
  name: kms-dev-kibana
spec:
  version: 8.14.3
  count: 1
  elasticsearchRef:
    name: elasticsearch
  http:
    service:
      spec:
        type: LoadBalancer # default is ClusterIP
    tls:
      selfSignedCertificate:
        disabled: true

Not sure if I missed something with Kabana, it is working with port-forwarding with localhost, but it doesn't with NLB