2

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.

askedApr 5, 2020 at 6:56
Edcel Cabrera Vista's user avatar

3 Answers3

2

This happened with me too that after all the setup, I was not able to see the ingress address. The best way to debug this issue is to check the logs for the ingress controller. You can do this by:

  1. Get the Ingress controller po name by using: kubectl get po -n kube-system
  2. Check logs for the po using: kubectl logs <po_name> -n kube-system

This will point you to the exact issue as to why you are not seeing the address.

answeredMar 18, 2021 at 11:29
Gautam Rajotya's user avatar
Sign up to request clarification or add additional context in comments.

Comments

2

solution fitted my case is adding ingressClassName in ingress.yaml or configure default ingressClass.

add ingressClassName in ingress.yaml

#ingress.yamlmetadata:  name: ingress-nginx...spec:  ingressClassName: nginx       <-- add this  rules:...

or

edit ingressClass yaml

$ kubectl edit ingressclass <ingressClass Name> -n <ingressClass namespace>#ingressClass.yamlapiVersion: networking.k8s.io/v1kind: IngressClassmetadata:  annotations:    ingressclass.kubernetes.io/is-default-class: "true"   <-- add this....

link

answeredOct 7, 2022 at 3:45
thor son's user avatar

Comments

0

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

answeredApr 15, 2020 at 10:37
Bryan Calvo Benoit's user avatar

1 Comment

Hi I am getting the below error for the same case where I see no address for the host of ingress. Desperately looking for a solution. {"level":"error","ts":1643650856.9675832,"logger":"controller-runtime.manager.controller.ingress","msg":"Reconciler error","name":"app-ingress","namespace":"backend","error":"WebIdentityErr: failed to retrieve credentials\ncaused by: RequestError: send request failed\ncaused by: Post \"sts.us-east-1.amazonaws.com\": dial tcp: i/o timeout"}

Your Answer

Sign up orlog in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

By clicking “Post Your Answer”, you agree to ourterms of service and acknowledge you have read ourprivacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.