public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 12:38:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1890 from rancher/main

Browse Source 
Sync v2.12.0 branch with main
This commit is contained in:
Billy Tat
2025-07-23 11:29:09 -07:00
committed by GitHub
parent ace61d8556 52e7a56504
commit 6b577eeacf
20 changed files with 150 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/create-issue.yml
-2
View File
@@ -4,8 +4,6 @@ on:
pull_request_target: pull_request_target:
types: types:
- closed - closed
branches:
- main
paths-ignore: paths-ignore:
- '**/README.md' - '**/README.md'
docs/getting-started/installation-and-upgrade/other-installation-methods/rancher-behind-an-http-proxy/install-kubernetes.md
+9 -1
View File
@@ -10,7 +10,15 @@ Once the infrastructure is ready, you can continue with setting up a Kubernetes
The steps to set up RKE, RKE2, or K3s are shown below. The steps to set up RKE, RKE2, or K3s are shown below.
For convenience, export the IP address and port of your proxy into an environment variable and set up the HTTP_PROXY variables for your current shell on every node: For convenience, export the IP address and port of your proxy into an environment variable and set up the `HTTP_PROXY` variables for your current shell on every node:
:::caution
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable for Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
``` ```
export proxy_host="10.0.0.5:8888" export proxy_host="10.0.0.5:8888"
docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/register-existing-clusters.md
+8
View File
@@ -57,6 +57,14 @@ GKE Autopilot clusters aren't supported. See [Compare GKE Autopilot and Standard
9. If you are using self-signed certificates, you will receive the message `certificate signed by unknown authority`. To work around this validation, copy the command starting with `curl` displayed in Rancher to your clipboard. Then run the command on a node where kubeconfig is configured to point to the cluster you want to import. 9. If you are using self-signed certificates, you will receive the message `certificate signed by unknown authority`. To work around this validation, copy the command starting with `curl` displayed in Rancher to your clipboard. Then run the command on a node where kubeconfig is configured to point to the cluster you want to import.
10. When you finish running the command(s) on your node, click **Done**. 10. When you finish running the command(s) on your node, click **Done**.
:::important
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable in Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
**Result:** **Result:**
- Your cluster is registered and assigned a state of **Pending**. Rancher is deploying resources to manage your cluster. - Your cluster is registered and assigned a state of **Pending**. Rancher is deploying resources to manage your cluster.
docs/integrations-in-rancher/fleet/use-fleet-behind-a-proxy.md
+8
View File
@@ -22,6 +22,14 @@ For private nodes or private clusters, the environment variables need to be set
When adding Fleet agent environment variables for the proxy, replace <PROXY_IP> with your private proxy IP. When adding Fleet agent environment variables for the proxy, replace <PROXY_IP> with your private proxy IP.
:::caution
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable in Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
| Variable Name | Value | | Variable Name | Value |
|------------------|--------| |------------------|--------|
| `HTTP_PROXY` | http://<PROXY_IP>:8888 | | `HTTP_PROXY` | http://<PROXY_IP>:8888 |
docs/reference-guides/single-node-rancher-in-docker/http-proxy-configuration.md
+5 -5
View File
@@ -10,11 +10,11 @@ If you operate Rancher behind a proxy and you want to access services through th
Make sure `NO_PROXY` contains the network addresses, network address ranges and domains that should be excluded from using the proxy. Make sure `NO_PROXY` contains the network addresses, network address ranges and domains that should be excluded from using the proxy.
| Environment variable | Purpose | | Environment variable | Purpose |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------- | |----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| HTTP_PROXY | Proxy address to use when initiating HTTP connection(s) | | HTTP_PROXY | Proxy address to use when initiating HTTP connection(s) |
| HTTPS_PROXY | Proxy address to use when initiating HTTPS connection(s) | | HTTPS_PROXY | Proxy address to use when initiating HTTPS connection(s) |
| NO_PROXY | Network address(es), network address range(s) and domains to exclude from using the proxy when initiating connection(s) | | NO_PROXY | Network address(es), network address range(s) and domains to exclude from using the proxy when initiating connection(s). <br/><br/> The value must be a comma-delimited string which contains IP addresses, CIDR notation, domain names, or special DNS labels (*). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config) |
:::note Important: :::note Important:
versioned_docs/version-2.10/getting-started/installation-and-upgrade/other-installation-methods/rancher-behind-an-http-proxy/install-kubernetes.md
+8
View File
@@ -12,6 +12,14 @@ The steps to set up RKE, RKE2, or K3s are shown below.
For convenience, export the IP address and port of your proxy into an environment variable and set up the HTTP_PROXY variables for your current shell on every node: For convenience, export the IP address and port of your proxy into an environment variable and set up the HTTP_PROXY variables for your current shell on every node:
:::caution
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable for Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
``` ```
export proxy_host="10.0.0.5:8888" export proxy_host="10.0.0.5:8888"
export HTTP_PROXY=http://${proxy_host} export HTTP_PROXY=http://${proxy_host}
versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/register-existing-clusters.md
+9
View File
@@ -56,6 +56,15 @@ GKE Autopilot clusters aren't supported. See [Compare GKE Autopilot and Standard
9. If you are using self-signed certificates, you will receive the message `certificate signed by unknown authority`. To work around this validation, copy the command starting with `curl` displayed in Rancher to your clipboard. Then run the command on a node where kubeconfig is configured to point to the cluster you want to import. 9. If you are using self-signed certificates, you will receive the message `certificate signed by unknown authority`. To work around this validation, copy the command starting with `curl` displayed in Rancher to your clipboard. Then run the command on a node where kubeconfig is configured to point to the cluster you want to import.
10. When you finish running the command(s) on your node, click **Done**. 10. When you finish running the command(s) on your node, click **Done**.
:::important
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable in Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
**Result:** **Result:**
- Your cluster is registered and assigned a state of **Pending**. Rancher is deploying resources to manage your cluster. - Your cluster is registered and assigned a state of **Pending**. Rancher is deploying resources to manage your cluster.
versioned_docs/version-2.10/integrations-in-rancher/fleet/use-fleet-behind-a-proxy.md
+8
View File
@@ -22,6 +22,14 @@ For private nodes or private clusters, the environment variables need to be set
When adding Fleet agent environment variables for the proxy, replace <PROXY_IP> with your private proxy IP. When adding Fleet agent environment variables for the proxy, replace <PROXY_IP> with your private proxy IP.
:::caution
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable in Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
| Variable Name | Value | | Variable Name | Value |
|------------------|--------| |------------------|--------|
| `HTTP_PROXY` | http://<PROXY_IP>:8888 | | `HTTP_PROXY` | http://<PROXY_IP>:8888 |
versioned_docs/version-2.10/reference-guides/single-node-rancher-in-docker/http-proxy-configuration.md
+5 -6
View File
@@ -10,12 +10,11 @@ If you operate Rancher behind a proxy and you want to access services through th
Make sure `NO_PROXY` contains the network addresses, network address ranges and domains that should be excluded from using the proxy. Make sure `NO_PROXY` contains the network addresses, network address ranges and domains that should be excluded from using the proxy.
| Environment variable | Purpose | | Environment variable | Purpose |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------- | |----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| HTTP_PROXY | Proxy address to use when initiating HTTP connection(s) | | HTTP_PROXY | Proxy address to use when initiating HTTP connection(s) |
| HTTPS_PROXY | Proxy address to use when initiating HTTPS connection(s) | | HTTPS_PROXY | Proxy address to use when initiating HTTPS connection(s) |
| NO_PROXY | Network address(es), network address range(s) and domains to exclude from using the proxy when initiating connection(s) | | NO_PROXY | Network address(es), network address range(s) and domains to exclude from using the proxy when initiating connection(s). <br/><br/> The value must be a comma-delimited string which contains IP addresses, CIDR notation, domain names, or special DNS labels (*). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config) |
:::note Important: :::note Important:
NO_PROXY must be in uppercase to use network range (CIDR) notation. NO_PROXY must be in uppercase to use network range (CIDR) notation.
versioned_docs/version-2.11/getting-started/installation-and-upgrade/other-installation-methods/rancher-behind-an-http-proxy/install-kubernetes.md
+8
View File
@@ -12,6 +12,14 @@ The steps to set up RKE, RKE2, or K3s are shown below.
For convenience, export the IP address and port of your proxy into an environment variable and set up the HTTP_PROXY variables for your current shell on every node: For convenience, export the IP address and port of your proxy into an environment variable and set up the HTTP_PROXY variables for your current shell on every node:
:::caution
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable for Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
``` ```
export proxy_host="10.0.0.5:8888" export proxy_host="10.0.0.5:8888"
export HTTP_PROXY=http://${proxy_host} export HTTP_PROXY=http://${proxy_host}
versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/register-existing-clusters.md
+8
View File
@@ -57,6 +57,14 @@ GKE Autopilot clusters aren't supported. See [Compare GKE Autopilot and Standard
9. If you are using self-signed certificates, you will receive the message `certificate signed by unknown authority`. To work around this validation, copy the command starting with `curl` displayed in Rancher to your clipboard. Then run the command on a node where kubeconfig is configured to point to the cluster you want to import. 9. If you are using self-signed certificates, you will receive the message `certificate signed by unknown authority`. To work around this validation, copy the command starting with `curl` displayed in Rancher to your clipboard. Then run the command on a node where kubeconfig is configured to point to the cluster you want to import.
10. When you finish running the command(s) on your node, click **Done**. 10. When you finish running the command(s) on your node, click **Done**.
:::important
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable in Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
**Result:** **Result:**
- Your cluster is registered and assigned a state of **Pending**. Rancher is deploying resources to manage your cluster. - Your cluster is registered and assigned a state of **Pending**. Rancher is deploying resources to manage your cluster.
versioned_docs/version-2.11/integrations-in-rancher/fleet/use-fleet-behind-a-proxy.md
+8
View File
@@ -22,6 +22,14 @@ For private nodes or private clusters, the environment variables need to be set
When adding Fleet agent environment variables for the proxy, replace <PROXY_IP> with your private proxy IP. When adding Fleet agent environment variables for the proxy, replace <PROXY_IP> with your private proxy IP.
:::caution
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable in Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
| Variable Name | Value | | Variable Name | Value |
|------------------|--------| |------------------|--------|
| `HTTP_PROXY` | http://<PROXY_IP>:8888 | | `HTTP_PROXY` | http://<PROXY_IP>:8888 |
versioned_docs/version-2.11/reference-guides/single-node-rancher-in-docker/http-proxy-configuration.md
+5 -6
View File
@@ -10,12 +10,11 @@ If you operate Rancher behind a proxy and you want to access services through th
Make sure `NO_PROXY` contains the network addresses, network address ranges and domains that should be excluded from using the proxy. Make sure `NO_PROXY` contains the network addresses, network address ranges and domains that should be excluded from using the proxy.
| Environment variable | Purpose | | Environment variable | Purpose |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------- | |----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| HTTP_PROXY | Proxy address to use when initiating HTTP connection(s) | | HTTP_PROXY | Proxy address to use when initiating HTTP connection(s) |
| HTTPS_PROXY | Proxy address to use when initiating HTTPS connection(s) | | HTTPS_PROXY | Proxy address to use when initiating HTTPS connection(s) |
| NO_PROXY | Network address(es), network address range(s) and domains to exclude from using the proxy when initiating connection(s) | | NO_PROXY | Network address(es), network address range(s) and domains to exclude from using the proxy when initiating connection(s). <br/><br/> The value must be a comma-delimited string which contains IP addresses, CIDR notation, domain names, or special DNS labels (*). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config) |
:::note Important: :::note Important:
NO_PROXY must be in uppercase to use network range (CIDR) notation. NO_PROXY must be in uppercase to use network range (CIDR) notation.
versioned_docs/version-2.12/getting-started/installation-and-upgrade/other-installation-methods/rancher-behind-an-http-proxy/install-kubernetes.md
+9 -1
View File
@@ -10,7 +10,15 @@ Once the infrastructure is ready, you can continue with setting up a Kubernetes
The steps to set up RKE, RKE2, or K3s are shown below. The steps to set up RKE, RKE2, or K3s are shown below.
For convenience, export the IP address and port of your proxy into an environment variable and set up the HTTP_PROXY variables for your current shell on every node: For convenience, export the IP address and port of your proxy into an environment variable and set up the `HTTP_PROXY` variables for your current shell on every node:
:::caution
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable for Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
``` ```
export proxy_host="10.0.0.5:8888" export proxy_host="10.0.0.5:8888"
versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/register-existing-clusters.md
+8
View File
@@ -57,6 +57,14 @@ GKE Autopilot clusters aren't supported. See [Compare GKE Autopilot and Standard
9. If you are using self-signed certificates, you will receive the message `certificate signed by unknown authority`. To work around this validation, copy the command starting with `curl` displayed in Rancher to your clipboard. Then run the command on a node where kubeconfig is configured to point to the cluster you want to import. 9. If you are using self-signed certificates, you will receive the message `certificate signed by unknown authority`. To work around this validation, copy the command starting with `curl` displayed in Rancher to your clipboard. Then run the command on a node where kubeconfig is configured to point to the cluster you want to import.
10. When you finish running the command(s) on your node, click **Done**. 10. When you finish running the command(s) on your node, click **Done**.
:::important
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable in Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
**Result:** **Result:**
- Your cluster is registered and assigned a state of **Pending**. Rancher is deploying resources to manage your cluster. - Your cluster is registered and assigned a state of **Pending**. Rancher is deploying resources to manage your cluster.
versioned_docs/version-2.12/integrations-in-rancher/fleet/use-fleet-behind-a-proxy.md
+8
View File
@@ -22,6 +22,14 @@ For private nodes or private clusters, the environment variables need to be set
When adding Fleet agent environment variables for the proxy, replace <PROXY_IP> with your private proxy IP. When adding Fleet agent environment variables for the proxy, replace <PROXY_IP> with your private proxy IP.
:::caution
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable in Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
| Variable Name | Value | | Variable Name | Value |
|------------------|--------| |------------------|--------|
| `HTTP_PROXY` | http://<PROXY_IP>:8888 | | `HTTP_PROXY` | http://<PROXY_IP>:8888 |
versioned_docs/version-2.12/reference-guides/single-node-rancher-in-docker/http-proxy-configuration.md
+5 -5
View File
@@ -10,11 +10,11 @@ If you operate Rancher behind a proxy and you want to access services through th
Make sure `NO_PROXY` contains the network addresses, network address ranges and domains that should be excluded from using the proxy. Make sure `NO_PROXY` contains the network addresses, network address ranges and domains that should be excluded from using the proxy.
| Environment variable | Purpose | | Environment variable | Purpose |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------- | |----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| HTTP_PROXY | Proxy address to use when initiating HTTP connection(s) | | HTTP_PROXY | Proxy address to use when initiating HTTP connection(s) |
| HTTPS_PROXY | Proxy address to use when initiating HTTPS connection(s) | | HTTPS_PROXY | Proxy address to use when initiating HTTPS connection(s) |
| NO_PROXY | Network address(es), network address range(s) and domains to exclude from using the proxy when initiating connection(s) | | NO_PROXY | Network address(es), network address range(s) and domains to exclude from using the proxy when initiating connection(s). <br/><br/> The value must be a comma-delimited string which contains IP addresses, CIDR notation, domain names, or special DNS labels (*). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config) |
:::note Important: :::note Important:
versioned_docs/version-2.9/getting-started/installation-and-upgrade/other-installation-methods/rancher-behind-an-http-proxy/install-kubernetes.md
+8
View File
@@ -12,6 +12,14 @@ The steps to set up RKE, RKE2, or K3s are shown below.
For convenience, export the IP address and port of your proxy into an environment variable and set up the HTTP_PROXY variables for your current shell on every node: For convenience, export the IP address and port of your proxy into an environment variable and set up the HTTP_PROXY variables for your current shell on every node:
:::caution
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable for Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
``` ```
export proxy_host="10.0.0.5:8888" export proxy_host="10.0.0.5:8888"
export HTTP_PROXY=http://${proxy_host} export HTTP_PROXY=http://${proxy_host}
versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/register-existing-clusters.md
+8
View File
@@ -56,6 +56,14 @@ GKE Autopilot clusters aren't supported. See [Compare GKE Autopilot and Standard
9. If you are using self-signed certificates, you will receive the message `certificate signed by unknown authority`. To work around this validation, copy the command starting with `curl` displayed in Rancher to your clipboard. Then run the command on a node where kubeconfig is configured to point to the cluster you want to import. 9. If you are using self-signed certificates, you will receive the message `certificate signed by unknown authority`. To work around this validation, copy the command starting with `curl` displayed in Rancher to your clipboard. Then run the command on a node where kubeconfig is configured to point to the cluster you want to import.
10. When you finish running the command(s) on your node, click **Done**. 10. When you finish running the command(s) on your node, click **Done**.
:::important
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable in Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
**Result:** **Result:**
- Your cluster is registered and assigned a state of **Pending**. Rancher is deploying resources to manage your cluster. - Your cluster is registered and assigned a state of **Pending**. Rancher is deploying resources to manage your cluster.
versioned_docs/version-2.9/integrations-in-rancher/fleet/use-fleet-behind-a-proxy.md
+8
View File
@@ -22,6 +22,14 @@ For private nodes or private clusters, the environment variables need to be set
When adding Fleet agent environment variables for the proxy, replace <PROXY_IP> with your private proxy IP. When adding Fleet agent environment variables for the proxy, replace <PROXY_IP> with your private proxy IP.
:::caution
The `NO_PROXY` environment variable is not standardized, and the accepted format of the value can differ between applications. When configuring the `NO_PROXY` variable in Rancher, the value must adhere to the format expected by Golang.
Specifically, the value should be a comma-delimited string which only contains IP addresses, CIDR notation, domain names, or special DNS labels (e.g. `*`). For a full description of the expected value format, refer to the [**upstream Golang documentation**](https://pkg.go.dev/golang.org/x/net/http/httpproxy#Config)
:::
| Variable Name | Value | | Variable Name | Value |
|------------------|--------| |------------------|--------|
| `HTTP_PROXY` | http://<PROXY_IP>:8888 | | `HTTP_PROXY` | http://<PROXY_IP>:8888 |