// Module included in the following assemblies: // // * networking/enable-cluster-wide-proxy.adoc :_mod-docs-content-type: PROCEDURE [id="nw-rosa-proxy-remove-cli_{context}"] = Removing the cluster-wide proxy using CLI You must use the {product-title} (ROSA) CLI, `rosa`, to remove the proxy's address from your cluster. .Prerequisites * You must have cluster administrator privileges. * You have installed the ROSA CLI (`rosa`). .Procedure * Use the `rosa edit` command to modify the proxy. You must pass empty strings to the `--http-proxy` and `--https-proxy` arguments to clear the proxy from the cluster: + [source,terminal] ---- $ rosa edit cluster -c --http-proxy "" --https-proxy "" ---- + [NOTE] ==== While your proxy might only use one of the proxy arguments, the empty fields are ignored, so passing empty strings to both the `--http-proxy` and `--https-proxy` arguments do not cause any issues. ==== + .Example Output + [source,yaml] ---- I: Updated cluster ---- .Verification * You can verify that the proxy has been removed from the cluster by using the `rosa describe` command: + [source,yaml] ---- $ rosa describe cluster -c ---- + Before removal, the proxy IP displays in a proxy section: + [source,yaml,subs="attributes+"] ---- Name: ID: External ID: OpenShift Version: {product-version}.0 Channel Group: stable DNS: AWS Account: API URL: Console URL: Region: us-east-1 Multi-AZ: false Nodes: - Control plane: 3 - Infra: 2 - Compute: 2 Network: - Type: OVNKubernetes - Service CIDR: - Machine CIDR: - Pod CIDR: - Host Prefix: Proxy: - HTTPProxy: Additional trust bundle: REDACTED ---- + After removing the proxy, the proxy section is removed: + [source,yaml,subs="attributes+"] ---- Name: ID: External ID: OpenShift Version: {product-version}.0 Channel Group: stable DNS: AWS Account: API URL: Console URL: Region: us-east-1 Multi-AZ: false Nodes: - Control plane: 3 - Infra: 2 - Compute: 2 Network: - Type: OVNKubernetes - Service CIDR: - Machine CIDR: - Pod CIDR: - Host Prefix: Additional trust bundle: REDACTED ----