Making 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 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.

Making 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 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.

Making 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 POLICY (ingress) POLICY (egress) IDENTITY LABELS (source:key[=value]) IPv6 IPv4 STATUS ENFORCEMENT ENFORCEMENT 232 Disabled Disabled

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 POLICY (ingress) POLICY (egress) IDENTITY LABELS (source:key[=value]) IPv6 IPv4 STATUS ENFORCEMENT ENFORCEMENT 232 Disabled Disabled

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 POLICY (ingress) POLICY (egress) IDENTITY LABELS (source:key[=value]) IPv6 IPv4 STATUS ENFORCEMENT ENFORCEMENT 108 Disabled POLICY (ingress) POLICY (egress) IDENTITY LABELS (source:key[=value]) IPv6 IPv4 STATUS ENFORCEMENT ENFORCEMENT 108 Disabled

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 POLICY (ingress) POLICY (egress) IDENTITY LABELS (source:key[=value]) IPv6 IPv4 STATUS ENFORCEMENT ENFORCEMENT 108 Disabled POLICY (ingress) POLICY (egress) IDENTITY LABELS (source:key[=value]) IPv6 IPv4 STATUS ENFORCEMENT ENFORCEMENT 108 Disabled

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 any etcd support Introduc�on of IPSec and use of ESP or u�liza�on of the traffic class field in the IPv6 header will allow to use more than 8 bits for the cluster-id and thus support more than 256 clusters we simply create a single network named ‘cilium-net’ for all containers: $ docker network create --ipv6 --subnet ::1/112 --driver cilium --ipam-driv Step 6: Start an Example Service with Docker In this

28 6.3.1.5.2 手动网络配置 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 6.3.1.5.3 IPv4 和 IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 6.3.2 设置用户和密码 . . . . . . . . . . d 来执行）。 netcfg/disable_autoconfig debian-installer 默认自动检测 IPv6 的网络配置和 DHCP。如果检测成 功的话，将没有机会回顾并且更改已经获得的设定。只能在自动检测失败的情况下手工配置网络。 如果本地网络上有 IPv6 路由器或 DHCP 服务器，但是因为例如它们给出错误的答案而不想使用它， 那么可以使用参数 netcfg/disable_autoconfig=true openssh-client-udeb （使您可以在安装过程中使用 scp）和 ppp-udeb（请 参见第 D.4 节）。 netcfg/disable_autoconfig 如果您想禁止 IPv6 自动配置和 DHCP，并强制使用静态网络设置来代替，那 么将它设为 true。 mirror/protocol (protocol) 安装程序默认会使用 http 协议从 Debian 镜像下载文件，在普通优先级的安

31 6.3.1.5.2 手动网络配置 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 6.3.1.5.3 IPv4 和 IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 6.3.2 设置用户和密码 . . . . . . . . . . d 来执行）。 netcfg/disable_autoconfig debian-installer 默认自动检测 IPv6 的网络配置和 DHCP。如果检测成 功的话，将没有机会回顾并且更改已经获得的设定。只能在自动检测失败的情况下手工配置网络。 如果本地网络上有 IPv6 路由器或 DHCP 服务器，但是因为例如它们给出错误的答案而不想使用它， 那么可以使用参数 netcfg/disable_autoconfig=true openssh-client-udeb （使您可以在安装过程中使用 scp）和 ppp-udeb（请 参见第 D.4 节）。 netcfg/disable_autoconfig 如果您想禁止 IPv6 自动配置和 DHCP，并强制使用静态网络设置来代替，那 么将它设为 true。 mirror/protocol (protocol) 安装程序默认会使用 http 协议从 Debian 镜像下载文件，在普通优先级的安

28 6.3.1.5.2 手动网络配置 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 6.3.1.5.3 IPv4 和 IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 6.3.2 设置用户和密码 . . . . . . . . . . d 来执行）。 netcfg/disable_autoconfig debian-installer 默认自动检测 IPv6 的网络配置和 DHCP。如果检测成 功的话，将没有机会回顾并且更改已经获得的设定。只能在自动检测失败的情况下手工配置网络。 如果本地网络上有 IPv6 路由器或 DHCP 服务器，但是因为例如它们给出错误的答案而不想使用它， 那么可以使用参数 netcfg/disable_autoconfig=true openssh-client-udeb （使您可以在安装过程中使用 scp）和 ppp-udeb（请 参见第 D.4 节）。 netcfg/disable_autoconfig 如果您想禁止 IPv6 自动配置和 DHCP，并强制使用静态网络设置来代替，那 么将它设为 true。 mirror/protocol (protocol) 安装程序默认会使用 http 协议从 Debian 镜像下载文件，在普通优先级的安