development and in situations where the likes of PasteDeploy is not necessary: # Listen on both IPv4 and IPv6 on port 8041 waitress-serve --listen=*:8041 myapp:wsgifunc # Listen on only IPv4 on port 8041 waitress-serve wildcard for the hostname is also supported and will bind to both IPv4/IPv6 depending on whether they are enabled or disabled. IPv6 IP addresses are supported by surrounding the IP address with brackets brackets. New in version 1.0. ipv4 Enable or disable IPv4 (boolean) ipv6 Enable or disable IPv6 (boolean) unix_socket Path of Unix socket (string). If a socket path is specified, a Unix domain socket is made

without patching the core Apache server. IPv6 Support On systems where IPv6 is supported by the underlying Apache Portable Runtime library, Apache gets IPv6 listening sockets by default. Additionally Additionally, the LISTEN, NAMEVIRTUALHOST, and VIRTUALHOST directives support IPv6 numeric address strings (e.g., "Listen [2001:db8::1]:8080"). Filtering Apache modules may now be written as filters which 1:80 Listen 192.170.2.5:8000 IPv6 addresses must be surrounded in square brackets, as in the following example: Listen [2001:db8::a00:20ff:fea7:ccea]:80 ## Special IPv6 Considerations A growing number

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

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

在以前的版本中，裸机 kube-apiserver 健康检查探测使用硬编码的 IPv4 地址与负载均衡器通信。这个版本修复了使用 localhost 的健康检查，它可以正确处理 IPv4 和 IPv6。另外，API 服务器会检查 readyz 端点而不是 healthz。(BZ#1847082) 由于没有列出所有依赖步骤的 Terraform 步骤，Red Hat OpenStack Pla 在裸机环境中，一些 DNS 记录是为 IPv4 硬编码的。这会导致在 IPv6 环境中无法正确提供一些记录，这可能需要在外部 DNS 服务器中创建这些记录。在这个版本中，更新了 Machine Config Operator（MCO），现在 DNS 记录可根据使用的网络协议版本正确填充。现在，在 IPv4 和 IPv6 中都可以正确提供内部记录。(BZ#1820785) 在以前的版本中，机器 operand 列表视图。在这个版本中，这个问题已解决。(BZ#1842965) - 当禁用 IPv6 时，下载 pod socket 无法绑定，下载 pod 会崩溃。如果没有启用 IPv6，现在会使用 IPv4 作为 socket。下载 Pod 现在可以正常工作，无论是否启用了 IPv4 和 IPv6。（BZ#1846922） - Operator 状态显示值没有考虑手动批准策略。因此，显示 upgrade

Add/update a golang dependency ■ Add/update a new Kubernetes version ■ Optional: Docker and IPv6 ■ Debugging ○ Building Container Images ■ Developer images ■ Official release 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 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. ## I nstall Cilium: Install Cilium into the EKS cluster

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

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 ues/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

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 ues/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

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 ues/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