How to configure the no_proxy field in OSD and ROSA?

Solution Unverified - Updated -

Environment

  • Red Hat OpenShift Service on AWS (ROSA)
    • 4
  • Red Hat OpenShift Dedicated (OSD)
    • 4
  • Red Hat OpenShift Cluster Manager (OCM)

Issue

  • Is it supported to configure the no_proxy field in OSD/ROSA?
  • How to modify the no_proxy field in OSD and ROSA?
  • How to modify the noProxy in the cluster-wide proxy in OSD and ROSA?

Resolution

For ROSA clusters, starting with the rosa CLI version 1.2.3, it's now possible to configure the no_proxy field using the --no-proxy parameter with the rosa create cluster and rosa edit cluster commands.

Note: When editing the no_proxy field with the rosa edit cluster command and the --no-proxy parameter, the old value is overwritten. So for adding additional domains/IPs it's needed to pass the previous value of the noProxy including the new domains/IPs (see the Diagnostic Steps section to get the value of the noProxy before editing it).

It's not yet possible to configure the no_proxy field through the OCM web console, so as it's not possible to use the rosa CLI with OSD, it's not yet possible to configure the no_proxy field in OSD. There is a RFE to support the no_proxy field in the OCM web console: HAC-1358.

Root Cause

Starting with the rosa CLI version 1.2.3, it's now possible to configure the no_proxy field.

Diagnostic Steps

Check if the noProxy is already configured:

$ oc get proxy cluster -o yaml | grep noProxy
  noProxy: proxy.example.com

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments