File: proc_starting-behind-proxy.adoc

package info (click to toggle)
golang-github-crc-org-crc 2.34.0%2Bds1-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 2,548 kB
  • sloc: sh: 398; makefile: 326; javascript: 40
file content (35 lines) | stat: -rw-r--r-- 1,338 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
= Starting {prod} behind a proxy

You can start {prod} behind a defined proxy using environment variables or configurable properties.

[NOTE]
====
SOCKS proxies are not supported by {ocp}.
====

.Prerequisites
* 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].

.Procedure
. Define a proxy using the `http_proxy` and `https_proxy` environment variables or using the [command]`{bin} config set` command as follows:
+
[subs="+quotes,attributes"]
----
$ {bin} config set http-proxy http://proxy.example.com:__<port>__
$ {bin} config set https-proxy http://proxy.example.com:__<port>__
$ {bin} config set no-proxy __<comma-separated-no-proxy-entries>__
----

. If the proxy uses a custom CA certificate file, set it as follows:
+
[subs="+quotes,attributes"]
----
$ {bin} config set proxy-ca-file __<path-to-custom-ca-file>__
----

[NOTE]
====
Proxy-related values set in the configuration for {prod} have priority over values set with environment variables.
====