What values are defined in 'noProxy' section under proxy configuration in OpenShift Container Platform 4.

Issue

• Most Web clients support connection to proxy servers via environment variables. These variables tell the client what URL should be used to access the proxy servers and which exceptions should be made:

  http_proxy / HTTP_PROXY
  https_proxy / HTTPS_PROXY
  no_proxy / NO_PROXY
  

• no_proxy value defines a list of destination domain names, domains, IP addresses, or other network CIDRs to exclude proxying. no_proxy provides a way to exclude traffic destined to certain hosts from using the proxy.

  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 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` nor `httpsProxy` fields are set.
  

• Review the sites that your cluster requires access to and determine whether any of them must bypass the proxy. All cluster system egress traffic is proxied by default, including calls to the cloud provider API for the cloud that hosts your cluster. System-wide proxy affects system components only, not user workloads. Add sites to the Proxy object’s spec.noProxy field to bypass the proxy if necessary.