Envoy not listening dualstack, IPv6?

[matejvasek]

Hi, for mostly experimental purposes I am trying to run knative in IPv6-only KinD cluster.
It looks like most components works all right, however I have an issue with contour installation.
I am installing contour like so.
In cluster events I see failed health probes to envoy pod. This is almost certainly caused by the fact that envoy does listen on 0.0.0.0 and NOT on ::.

Is that intentional? Can I fix it somehow?

[matejvasek]

@rgarrigue I think you had similar problem. How did you solve it.

[rgarrigue]

Using the bitnami contour helm chart, version ~ 20

contour:
  extraArgs:
    - "--stats-address=::"
    - "--envoy-service-http-address=::"
    - "--envoy-service-https-address=::"
  
envoy:
  service:
    annotations:
      service.beta.kubernetes.io/aws-load-balancer-type: nlb
    ipFamilyPolicy: PreferDualStack
    ipFamilies:
      - IPv6

Note that my setup never worked with AWS NLB, but could have been due to a glitch in my EKS setup

[matejvasek]

Also why it would not listen on :: by default? That would listen on all interface and both stacks.