Description:

I'm testing the latest release (v1.2.0-rc.1) that adds IPv6 and dual-stack support to Envoy Gateway. On my IPv6-first cluster the pods created for the gateway resource fail the startup probe because, by default, the listener is listening only on IPv4 instead of IPv6 or all interfaces.

These IPs are not customizable and are used directly in the bootstrap.yaml.tpl template, example:

Repro steps:

1. Deploy Envoy Gateway on the cluster
2. Configure a resource of type Gateway

Environment:

• Kubernetes cluster configured in dual-stack with IPv6 as primary:

  apiVersion: kubeadm.k8s.io/v1beta4
  kind: ClusterConfiguration
  ...
  networking:
    podSubnet: fd00:10:244::/48,10.244.0.0/16
    serviceSubnet: fd00:10:96::/112,10.96.0.0/12

• Envoy Gateway version: v1.2.0-rc.1

Logs:

Startup probe failed: Get "http://[fd00:10:244:2::5b]:19001/ready": dial tcp [fd00:10:244:2::5b]:19001: connect: connection refused