contour: Endpoints are missing for Contour when installed on an IPV6 only kubernetes cluster

What steps did you take and what happened:

I have an IPV6 only kubernetes cluster with one master and one worker node.
Installed Contour using ‘kubectl apply -f https://j.hept.io/contour-deployment-rbac’
I can see Contour pods are running with IPV6 addresses. I can also list service which has IPV6 address.
When I list endpoints using ‘kubectl get endpoints --all-namespaces’ , contour has empty field while all other services got endpoints.

What did you expect to happen: Contour should be able to detect the endpoints , the same way as in IPV4 cluster.

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] Not sure whether anything need to be set in Contour for IPV6 support. If yes then the documentation needs to include those details.

Environment:

Contour version: master
Kubernetes version: (use kubectl version): 1. 13.3
Kubernetes installer & version: kubeadm 1.13.3
Cloud provider or hardware configuration: k8s on VMs
OS (e.g. from /etc/os-release): Ubuntu 18.04 LTS

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 24 (17 by maintainers)

Most upvoted comments

I stand corrected. Thank you for explaining Alex

On Wed, 6 Mar 2019 at 00:34, Alexander Brand notifications@github.com wrote:

I suspect they are related. The contour deployment has a readiness probe on the Envoy container. If the readiness probe is failing, the pod overall is considered “NotReady”, and the pod IP address will not show up as a Ready address in the list of Endpoints.

@roshnihp https://github.com/roshnihp can you provide the output of the following commands?

kubectl -n heptio-contour describe endpoints

kubectl -n heptio-contour describe pod contour

re: init container changes - It looks like I missed the – for the flag. It should be - --xds-address=“::1”. To make the readiness probe work, however, I think we also need to make the stats endpoint listen on IPv6. With that said, let’s verify first that the readiness probe is the actual issue before making any more changes.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/heptio/contour/issues/911#issuecomment-469681070, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAcAyBkBb3KAAAscnMXeUIb9AOH5ziuks5vTnJegaJpZM4bajba .

davecheney on Mar 5, 2019