-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
openshift-4.14, openshift-4.15, openshift-4.13, openshift-4.12
-
None
-
False
-
-
False
-
Install
-
-
Description: The current OpenShift documentation lacks information about the ability to include ports in the NO_PROXY configuration for IPv6 addresses. This is a valid workaround that is not covered in the current documentation, which only mentions valid options such as domains, domain names, IP addresses, and network CIDR. This information should be added for all 4.x versions of OpenShift prior to version 4.16.
The following statement is from the documentation
A comma-separated list of destination domain names, domains, IP addresses or other network CIDRs to exclude proxying. Preface a domain with . to match subdomains only. For example, .y.com matches x.y.com, but not y.com. Use * to bypass proxy for all destinations. If you scale up workers that are not included in the network defined by the networking.machineNetwork[].cidr field from the installation configuration, you must add them to this list to prevent connection issues. This field is ignored if neither the httpProxy or httpsProxy fields are set.
Steps to Reproduce:
- Review the section of the documentation related to NO_PROXY configuration.
- Note that there is no mention of the ability to use ports in conjunction with IPv6 addresses in the NO_PROXY environment variable.
Expected Behavior: The documentation should explicitly state that ports can be used in the NO_PROXY configuration for IPv6 addresses as a valid option.
Actual Behavior: Currently, the documentation only includes domains, domain names, IP addresses, and CIDR for the NO_PROXY setting, with no mention of ports, particularly for IPv6.
Suggested Update: Please update the OpenShift documentation to include the following:
- Mention that ports can be used in the NO_PROXY variable for IPv6 addresses.
- Clarify that this option is only available for IPv6 and not for IPv4.