I have a kubernetes application using AWS EKS. With the below details:
Cluster: + Kubernetes version: 1.15 + Platform version: eks.1
Node Groups: + Instance Type: t3.medium + 2(Minimum) - 2(Maximum) - 2(Desired) configuration
[Pods] + 2 active pods
[Service] + Configured Type: ClusterIP + metadata.name: k8s-eks-api-service
[rbac-role.yaml] https://pastebin.com/Ksapy7vK
[alb-ingress-controller.yaml] https://pastebin.com/95CwMtg0
[ingress.yaml] https://pastebin.com/S3gbEzez
When I tried to pull the ingress details. Below are the values (NO ADDRESS)
Host: *
ADDRESS:
My goal is to know why the address has no value. I expect to have private or public address to be used by other service on my application.
In order for your kubernetes cluster to be able to get an address you will need to be able to manage route53 from withtin the cluster, for this task I would recommend to use externalDns.
In a broader sense, ExternalDNS allows you to control DNS records dynamically via Kubernetes resources in a DNS provider-agnostic way.
source: ExternalDNS