ingress-nginx: IP does not found

Hi:

I deploy a single ingress to provide grafana access from outside, the ingress is as follow:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: monitoring-ingress
  annotations:
    kubernetes.io/ingress.class: "nginx"
spec:
  rules:
    - http:
       paths:
       - path:
         backend:
          serviceName: monitoring-grafana
          servicePort: 5432

So, when I get the ingress details, the IP address does not appear!!!

kubectl get ing
NAME                       HOSTS     ADDRESS   PORTS     AGE
coiling-toucan-monocular   *                   80        1d
monitoring-ingress         *                   80        13m

kubectl get ing monitoring-ingress -o yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
  creationTimestamp: 2017-10-03T14:03:35Z
  generation: 1
  name: monitoring-ingress
  namespace: default
  resourceVersion: "929379"
  selfLink: /apis/extensions/v1beta1/namespaces/default/ingresses/monitoring-ingress
  uid: a5b84800-a843-11e7-b4b3-005056b77c78
spec:
  rules:
  - http:
      paths:
      - backend:
          serviceName: monitoring-grafana
          servicePort: 5432
status:
  loadBalancer: {}

Where is my IP address??? The other ingress running about 2 days also does not show the IP address!! What happend with this?

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 31 (3 by maintainers)

Commits related to this issue

k8s ingress https://github.com/kubernetes/ingress-nginx/issues/1467 — committed to RouR/ToDo-ToBuy by RouR 6 years ago

Most upvoted comments

@felixPG Ok, I create a service for the ingress controller with an external IP. https://github.com/RouR/ToDo-ToBuy/blob/c1019a8d130e9940906651ac817bf61501f1274e/k8s/dev/nginx.yaml#L167

My web service is opened, cool! But

> kubectl get services --all-namespaces
NAMESPACE       NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP      PORT(S)                      AGE
default         kubernetes             ClusterIP   10.96.0.1       <none>           443/TCP                      1d
dev             web-service            ClusterIP   10.111.22.32    <none>           80/TCP                       1d
ingress-nginx   default-http-backend   ClusterIP   10.110.232.9    <none>           80/TCP                       1d
ingress-nginx   ingress-nginx          NodePort    10.110.64.203   192.168.99.100   80:31824/TCP,443:31181/TCP   1d
kube-system     default-http-backend   NodePort    10.108.203.14   <none>           80:30001/TCP                 3m
kube-system     heapster               ClusterIP   10.111.139.88   <none>           80/TCP                       1d
kube-system     kube-dns               ClusterIP   10.96.0.10      <none>           53/UDP,53/TCP                1d
kube-system     kubernetes-dashboard   NodePort    10.98.208.102   <none>           80:30000/TCP                 1d
kube-system     monitoring-grafana     NodePort    10.110.37.141   <none>           8011:30700/TCP               1d
kube-system     monitoring-influxdb    ClusterIP   10.100.177.72   <none>           8086/TCP                     1d

> kubectl get --all-namespaces ing -o wide
NAMESPACE   NAME          HOSTS     ADDRESS   PORTS     AGE
dev         web-ingress   *                   80        1d

What`s going on with ingress address?

RouR on Jan 15, 2018

@RouR create a service for the ingress controller with an external IPs.

Regards

ghost on Jan 15, 2018