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

callback. See https://github.com/Pylons/waitress/pull/249 1.2.1 (2019-01-25) Bugfixes When given an IPv6 address in X-Forwarded-For or Forwarded for= waitress was placing the IP address in REMOTE_ADDR with the requirements in the CGI spec which REMOTE_ADDR was lifted from. Waitress will now place the bare IPv6 address in REMOTE_ADDR: 2001:db8::0. See https://github.com/Pylons/waitress/pull/232 and https://github com/Pylons/waitress/issues/149 and https://github.com/Pylons/waitress/pull/153 1.0.1 (2016-10-22) Bugfixes IPv6 support on Windows was broken due to missing constants in the socket module. This has been resolved

callback. See https://github.com/Pylons/waitress/pull/249 1.2.1 (2019-01-25) Bugfixes When given an IPv6 address in X-Forwarded-For or Forwarded for= waitress was placing the IP address in REMOTE_ADDR with the requirements in the CGI spec which REMOTE_ADDR was lifted from. Waitress will now place the bare IPv6 address in REMOTE_ADDR: 2001:db8::0. See https://github.com/Pylons/waitress/pull/232 and https://github com/Pylons/waitress/issues/149 and https://github.com/Pylons/waitress/pull/153 1.0.1 (2016-10-22) Bugfixes IPv6 support on Windows was broken due to missing constants in the socket module. This has been resolved

callback. See https://github.com/Pylons/waitress/pull/249 1.2.1 (2019-01-25) Bugfixes When given an IPv6 address in X-Forwarded-For or Forwarded for= waitress was placing the IP address in REMOTE_ADDR with the requirements in the CGI spec which REMOTE_ADDR was lifted from. Waitress will now place the bare IPv6 address in REMOTE_ADDR: 2001:db8::0. See https://github.com/Pylons/waitress/pull/232 and https://github com/Pylons/waitress/issues/149 and https://github.com/Pylons/waitress/pull/153 1.0.1 (2016-10-22) Bugfixes IPv6 support on Windows was broken due to missing constants in the socket module. This has been resolved

callback. See https://github.com/Pylons/waitress/pull/249 1.2.1 (2019-01-25) Bugfixes When given an IPv6 address in X-Forwarded-For or Forwarded for= waitress was placing the IP address in REMOTE_ADDR with the requirements in the CGI spec which REMOTE_ADDR was lifted from. Waitress will now place the bare IPv6 address in REMOTE_ADDR: 2001:db8::0. See https://github.com/Pylons/waitress/pull/232 and https://github com/Pylons/waitress/issues/149 and https://github.com/Pylons/waitress/pull/153 1.0.1 (2016-10-22) Bugfixes IPv6 support on Windows was broken due to missing constants in the socket module. This has been resolved

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