Address not set on Ingress resource

[nphmuller]

Contour does not set the IP value on the Ingress resource. This value is necessary for services like ExternalDNS to work properly.

Version

The version that https://j.hept.io/contour-deployment-norbac produces. Atm:
docker.io/envoyproxy/envoy-alpine:v1.6.0
gcr.io/heptio-images/contour:master (pointing to b9ede01f025)

Repro

1. Setup Contour in your cluster.
   kubectl apply -f kubectl apply -f https://j.hept.io/contour-deployment-norbac
2. Deploy a simple service with Ingress rules.
   kubectl apply -f https://gist.githubusercontent.com/nphmuller/1c980c72e2119b1482e19eb619def08f/raw/10331f4bbc18abe36a0c8c841bf70ab04a38eb92/service-with-ingress.yaml
3. (A) kubectl get ingress nginx
4. (B) kubectl get ingress nginx -o yaml

Expected

A. ADDRESS column should have external IP of Contour load balancer service, but is empty.
B. status should have value:

status:
  loadBalancer:
    ingress:
    - ip: %External IP-of-Contour-LoadBalancer-service%

but has value:

status:
  loadBalancer: {}

[davecheney]

Yup, this is a known limitation and a feature request that keeps getting bumped from release to release. Please don’t close his issue, I’ll close the other as a duplicate as you have put more details in this one.

…

On 18 May 2018, at 23:41, Nick ***@***.***> wrote: Contour does not set the IP value on the Ingress resource. This value is necessary for services like ExternalDNS to work properly. Version The version that https://j.hept.io/contour-deployment-norbac produces. Atm: docker.io/envoyproxy/envoy-alpine:v1.6.0 gcr.io/heptio-images/contour:master (pointing to b9ede01f025) Repro Setup Contour in your cluster. kubectl apply -f kubectl apply -f https://j.hept.io/contour-deployment-norbac Deploy a simple service with Ingress rules. kubectl apply -f https://gist.githubusercontent.com/nphmuller/1c980c72e2119b1482e19eb619def08f/raw/10331f4bbc18abe36a0c8c841bf70ab04a38eb92/service-with-ingress.yaml (A) kubectl get ingress nginx (B) kubectl get ingress nginx -o yaml Expected A. ADDRESS column should have external IP of Contour load balancer service, but is empty. B. status should have value: status: loadBalancer: ingress: - ip: %External IP-of-Contour-LoadBalancer-service% but has value: status: loadBalancer: {} — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[piclemx]

@davecheney do you know if this will be done soon?

[davecheney]

I’m sorry this won’t make it for 0.6. I know it is important but resources are limited.

…

On 1 Jun 2018, at 23:21, Alexandre Picard-Lemieux ***@***.***> wrote: @davecheney do you know if this will be done soon? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[nphmuller]

@davecheney Still appreciate all the effort! 👍

[davecheney]

This should be possible to cover as part of the IngressRoute refactor. No ETA on a milestone.

[vorozhko]

Hi @davecheney,
do you have any update on the issue?

I am using external-dns with Ingress and it require ADDRESS field to be set otherwise it will not create DNS records.

[davecheney]

I’m sorry I don’t have an eta when this issue will be worked on.

[davecheney]

I'm sorry to report that at this stage in the development freeze without a design we won't be able to deliver this for rc.2. Moving to the backlog for prioritisation after Contour 1.0