No ingress IP address

[fengyd2018]

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):

What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

NGINX Ingress controller version:
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.10.2

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T10:09:24Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T09:42:01Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}

Environment:

• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):
  NAME="CentOS Linux"
  VERSION="7 (Core)"
• Kernel (e.g. uname -a):
  Linux master 3.10.0-693.el7.x86_64 Basic structure  #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
• Install tools:
• Others:

What happened:
Kubernetes cluser: One master and one node.

1. Install ingress-nginx-controller accordign to the page https://github.com/kubernetes/ingress-nginx/tree/master/deploy
   kubectl apply -f namespace.yaml -f default-backend.yaml -f configmap.yaml -f tcp-services-configmap.yaml -f udp-services-configmap.yaml
   kubectl apply -f rbac.yaml
   kubectl apply -f with-rbac.yaml
   kubectl apply -f provider/baremetal/service-nodeport.yaml

2. Install jenkins ingress with the following configuration:
   apiVersion: extensions/v1beta1
   kind: Ingress
   metadata:
   name: jenkins
   spec:
   rules:

• host: jenkins.xxx.lan
  http:
  paths:
  • path: /
    backend:
    serviceName: jenkins
    servicePort: 8080

3. No IP ADDRESS
   [root@master jenkins]# kubectl get ing
   NAME HOSTS ADDRESS PORTS AGE
   jenkins jenkins.xxx.lan 80 10h
   What you expected to happen:
   IP ADDRESS should be configured?

How to reproduce it (as minimally and precisely as possible):
No special/extra action

Anything else we need to know:

[gyliu513]

/cc @aledbf , I also have same issue with ingress 0.9.0 , it works fine when I was using ingress 0.9.0-beta.12

[gyliu513]

@fengyd2018 As a workaround, you can add a parameter of - --report-node-internal-ip-address=true to ingress to enable it can still report internal ip.

@aledbf post some comments at #1503 , hope can get some feedback from you.

[aledbf]

@gyliu513 we cannot do that. This should be an explicit option from the user, please check #1414
and #1407. Those issues were the reason why the added the flag.

[gyliu513]

Thanks @aledbf I did go through both #1414 and #1407 , the problem is that the behavior of getting ip is changed.

The original logic is getting both externalIP and internalIP, but is treating externalIP as priority, if no externalIP, it will use internalIP https://github.com/kubernetes/ingress-nginx/blob/nginx-0.9.0-beta.12/core/pkg/k8s/main.go#L81-L102 , but current logic using a flag to enable end user can either use internalIP or externalIP https://github.com/kubernetes/ingress-nginx/blob/nginx-0.9.0/internal/k8s/main.go#L39-L65 , I think we should at least have the logic of enabling end user keep original logic to use externalIP first and then internalIP, comments?

[aledbf]

Closing. Please add the flag --report-node-internal-ip-address=true

[aledbf]

I think we should at least have the logic of enabling end user keep original logic to use externalIP first and then internalIP, comments?

Makes sense. The PR #2065 contains this change

[gyliu513]

Thanks @aledbf , I created another PR #2072 by setting the default value of report-node-internal-ip-address as true to keep backward compatibility.