From e176c29a801ff6b2eda050e86e784796e76799d2 Mon Sep 17 00:00:00 2001 From: Christophe Fergeau Date: Mon, 29 Aug 2022 10:40:03 +0200 Subject: [PATCH] doc: Clarify when no_proxy=.testing needs to be set The current documentation can be misleading and make people think it's only needed when using `oc` This fixes #2726 --- docs/source/topics/proc_starting-behind-proxy.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/topics/proc_starting-behind-proxy.adoc b/docs/source/topics/proc_starting-behind-proxy.adoc index 8a7ef35a5c..adc95c0d0d 100644 --- a/docs/source/topics/proc_starting-behind-proxy.adoc +++ b/docs/source/topics/proc_starting-behind-proxy.adoc @@ -10,7 +10,7 @@ SOCKS proxies are not supported by {ocp}. .Prerequisites -* To use an existing {openshift} CLI ([command]`oc`) executable on your host machine, export the `.testing` domain as part of the `no_proxy` environment variable. +* If you are not using [command]`crc oc-env`, when interacting with the cluster, export the `.testing` domain as part of the `no_proxy` environment variable. The embedded [command]`oc` executable does not require manual settings. For more information about using the embedded [command]`oc` executable, see link:{crc-gsg-url}#accessing-the-openshift-cluster-with-oc_gsg[Accessing the {openshift} cluster with the {openshift} CLI].