Changes Add/update a golang dependency Add/update a new Kubernetes version Optional: Docker and IPv6 Debugging Building Container Images Developer images Official release images Official Cilium repositories requires some awareness of the underlying networking infrastructure. This mode works well with: Native IPv6 networks In conjunction with cloud network routers If you are already running routing daemons Load coredns-86c58d9df4-4g7dd 0/1 ContainerCreating 0 8m57s coredns-86c58d9df4-4l6b2 0/1 ContainerCreating 0 8m57s It may take a couple of minutes for all components

requires some awareness of the underlying networking infrastructure. This mode works well with: Native IPv6 networks In conjunction with cloud network routers If you are already running routing daemons Load coredns-86c58d9df4-4g7dd 0/1 ContainerCreating 0 8m57s coredns-86c58d9df4-4l6b2 0/1 ContainerCreating 0 8m57s It may take a couple of minutes for all components 4m12s coredns-86c58d9df4-4g7dd 1/1 Running 0 13m coredns-86c58d9df4-4l6b2 1/1 Running 0 13m Deploy the connectivity test You can deploy the

Changes Add/update a golang dependency Add/update a new Kubernetes version Optional: Docker and IPv6 Debugging Building Container Images Developer images Official release images Experimental Docker BuildKit requires some awareness of the underlying networking infrastructure. This mode works well with: Native IPv6 networks In conjunction with cloud network routers If you are already running routing daemons Load Limitations: The AWS ENI integration of Cilium is currently only enabled for IPv4. If you want to use IPv6, use a datapath/IPAM mode other than ENI. Install Cilium: Install Cilium into the EKS cluster. cilium

requires some awareness of the underlying networking infrastructure. This mode works well with: Native IPv6 networks In conjunction with cloud network routers If you are already running routing daemons Load coredns-86c58d9df4-4g7dd 0/1 ContainerCreating 0 8m57s coredns-86c58d9df4-4l6b2 0/1 ContainerCreating 0 8m57s It may take a couple of minutes for all components 4m12s coredns-86c58d9df4-4g7dd 1/1 Running 0 13m coredns-86c58d9df4-4l6b2 1/1 Running 0 13m Deploy the connectivity test You can deploy the

Local Development in Vagrant Box Making Changes Add/update a golang dependency Optional: Docker and IPv6 Debugging Building Container Images Developer images Official release images Update cilium-builder requires some awareness of the underlying networking infrastructure. This mode works well with: Native IPv6 networks In conjunction with cloud network routers If you are already running routing daemons Load coredns-86c58d9df4-4g7dd 0/1 ContainerCreating 0 8m57s coredns-86c58d9df4-4l6b2 0/1 ContainerCreating 0 8m57s It may take a couple of minutes for all components

Changes Add/update a golang dependency Add/update a new Kubernetes version Optional: Docker and IPv6 Debugging Building Container Images Developer images Official release images Experimental Docker BuildKit requires some awareness of the underlying networking infrastructure. This mode works well with: Native IPv6 networks In conjunction with cloud network routers If you are already running routing daemons Load Limitations: The AWS ENI integration of Cilium is currently only enabled for IPv4. If you want to use IPv6, use a datapath/IPAM mode other than ENI. Install Cilium: Install Cilium into the EKS cluster. cilium

requires some awareness of the underlying networking infrastructure. This mode works well with: Na�ve IPv6 networks In conjunc�on with cloud network routers If you are already running rou�ng daemons Load balancing name. If you are using CoreDNS, check the CoreDNS ConfigMap and validate that in-addr.arpa and ip6.arpa are listed as wildcards for the kubernetes block like this: kubectl -n kube-system edit cm coredns health kubernetes cluster.local in-addr.arpa ip6.arpa { pods insecure upstream fallthrough in-addr.arpa ip6.arpa } prometheus :9153 proxy

targetPort node IP and nodePort inserted to option field of ipv4 header , or to extension header of ipv6 header eth0 tc ingress tailCall redirect_peer redirect_neigh step1 client -> node1 : nodePort step3 client -> pod2 : targetPort native DSR DNAT and No SNAT step4 pod2:targetPort -> client step6 node2 : nodePort -> client client step5 node2 : nodePort -> client unNAT source IP by recored 的数量。 pod1 worker node1 veth veth eth0 pod2 veth veth eth0 packet ipv6 case: soure identity-> FLowLabel field of ipv6 header ipv4 tunnel case: soure identity->vxlan VNI field tc eBPF look up