From 3b1f101b9fbdcb0f4a6c8d16a1d904bb0f0a6623 Mon Sep 17 00:00:00 2001 From: Jason Boxman Date: Tue, 2 Feb 2021 20:58:05 -0500 Subject: [PATCH] For global proxy `noProxy` can be ignored - https://github.com/openshift/openshift-docs/issues/28782 --- modules/nw-proxy-configure-object.adoc | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/modules/nw-proxy-configure-object.adoc b/modules/nw-proxy-configure-object.adoc index ca70c6c58b75..205624ee9e88 100644 --- a/modules/nw-proxy-configure-object.adoc +++ b/modules/nw-proxy-configure-object.adoc @@ -93,15 +93,20 @@ spec: trustedCA: name: user-ca-bundle <5> ---- ++ +-- <1> A proxy URL to use for creating HTTP connections outside the cluster. The URL scheme must be `http`. <2> A proxy URL to use for creating HTTPS connections outside the cluster. If this is not specified, then `httpProxy` is used for both HTTP and HTTPS connections. <3> A comma-separated list of destination domain names, domains, IP addresses or -other network CIDRs to exclude proxying. Preface a domain with `.` to include -all subdomains of that domain. Use `*` to bypass proxy for all destinations. -Note that if you scale up workers not included in `networking.machineNetwork[].cidr` from the installation configuration, you must add them to this list to prevent connection issues. +other network CIDRs to exclude proxying. ++ +Preface a domain with `.` to include all the subdomains of that domain. Use `*` to bypass the 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. <4> One or more URLs external to the cluster to use to perform a readiness check before writing the `httpProxy` and `httpsProxy` values to status. <5> A reference to the ConfigMap in the `openshift-config` namespace that @@ -109,5 +114,6 @@ contains additional CA certificates required for proxying HTTPS connections. Note that the ConfigMap must already exist before referencing it here. This field is required unless the proxy's identity certificate is signed by an authority from the RHCOS trust bundle. +-- . Save the file to apply the changes.