Configuring Rancher and Fleet agent to run behind an HTTP proxy

This is applicable when there is a cluster showing as “unavailable“ after the user configured a proxy on the server.

1. Run env on the user’s server to determine what is the proxy IP. Ensure that the following line is checked:

2. Open the file /etc/systemd/system/k3s.service.env and append the following lines:

http_proxy=http://X.X.X.X

http_proxy="$PROXY_IP"
https_proxy="$PROXY_IP"
no_proxy="$NODE_IP,localhost,127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,.svc,.cluster.local"

1. Restart k3s:

systemctl restart k3s.service

1. Go to the Rancher dashboard Cluster Management > Clusters and click on Edit Config for the cluster:

a. Go to Advanced Options:

b. Configure the following Agent Environment Variables and press Save:

HTTP_PROXY: $PROXY_IP
HTTPS_PROXY: $PROXY_IP
NO_PROXY: $NODE_IP,localhost,127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,.svc,.cluster.local

1. Run the command:

kubectl edit deployment -n  cattle-system cattle-cluster-agent -o yaml

6. Type letter “i“ to insert text and on the env section, type the following lines:

- name: HTTP_PROXY       
   value: $PROXY_IP

- name: HTTPS_PROXY       
   value: $PROXY_IP
- name: NO_PROXY     
   value: $NODE_IP,localhost,127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,.svc,.cluster.local

Example:

Save by pressing Esc and then typing "wq"

1. Do the same on the fleet-agent by running the command:

kubectl edit deployment -n  cattle-fleet-system fleet-agent  -o yaml

1. Repeat Step 6.

2. After applying all the changes, wait for the cluster to show as Online on Rancher.

Configure Dashboard

In order for the connectors to support proxy settings, you will need to enable it in the configuration page: