John Gardiner Myers

```yaml apiVersion: apps/v1 kind: DaemonSet metadata: annotations: deprecated.daemonset.template.generation: "1" creationTimestamp: "2021-11-15T07:17:55Z" generation: 1 labels: addon.kops.k8s.io/name: networking.amazon-vpc-routed-eni app.kubernetes.io/instance: aws-vpc-cni app.kubernetes.io/managed-by: kops app.kubernetes.io/name: aws-node app.kubernetes.io/version: v1.9.3 k8s-app: aws-node role.kubernetes.io/networking: "1" name: aws-node...

``` bash-4.2# ip route default via 172.20.32.1 dev ens5 proto dhcp src 172.20.59.200 metric 100 169.254.172.2 dev veth417b9f8e scope link 169.254.172.3 dev veth30e71106 scope link 169.254.172.4 dev veth33b2a2cf scope link...

I gave you `ip route` and `ip addr` output from inside the pod. The pod doesn't have `ifconfig` installed; the `ip addr` output should be equivalent. This was all gotten...

Ah, from inside the non-host-network pod. On a new cluster, running v0.10.1: ``` root@sample-app-5b87df5d88-ttntd:~# ip route default via 169.254.172.1 dev v4if0 169.254.172.0/22 via 169.254.172.1 dev v4if0 src 169.254.172.5 169.254.172.1 dev...

Not sure what happened there. Here's the full `ip -6 route` from the node: ``` ubuntu@ip-172-20-34-242:~$ ip -6 route ::1 dev lo proto kernel metric 256 pref medium 2600:1f18:1e5f:8500:5256:: dev...

``` ubuntu@ip-172-20-34-242:~$ sudo iptables -L # Warning: iptables-legacy tables present, use iptables-legacy to see them Chain INPUT (policy ACCEPT) target prot opt source destination KUBE-NODEPORTS all -- anywhere anywhere /*...

``` jgmyers@bzxy473 kops % kubectl describe node ip-172-20-34-242.ec2.internal Name: ip-172-20-34-242.ec2.internal Roles: node Labels: beta.kubernetes.io/arch=amd64 beta.kubernetes.io/instance-type=t3.medium beta.kubernetes.io/os=linux failure-domain.beta.kubernetes.io/region=us-east-1 failure-domain.beta.kubernetes.io/zone=us-east-1a kops.k8s.io/instancegroup=nodes-us-east-1a kubernetes.io/arch=amd64 kubernetes.io/hostname=ip-172-20-34-242.ec2.internal kubernetes.io/os=linux kubernetes.io/role=node node-role.kubernetes.io/node= node.kubernetes.io/instance-type=t3.medium topology.kubernetes.io/region=us-east-1 topology.kubernetes.io/zone=us-east-1a Annotations: node.alpha.kubernetes.io/ttl: 0...

@MTRNord could you provide reproduction steps?

I'm not aware of anything other than review being needed. I tested on a frankenimage including commits from #2419 because I had difficulty creating IPv6-capable Ingresses due to AWS LBC...

There are going to be followup PRs extending AAAA support to other resources and possibly the AWS SD registry.