Doc Title

Forcepoint

Forcepoint Data Classification Powered

by GetVisibility Configuring Rancher
and Fleet agent to run behind HTTP
proxy

Report

Forcepoint
December 20, 2022
forcepoint.com Forcepoint Proprietary
GetVisibility: Configuring Rancher and Fleet agent to run behind HTTP proxy forcepoint.com

Table of Contents

INTRODUCTION.................................................................................................................................................................. 2
DETAILS .............................................................................................................................................................................. 2

© 2021 Forcepoint Forcepoint Proprietary 1

GetVisibility: Configuring Rancher and Fleet agent to run behind HTTP proxy forcepoint.com

Introduction
This document provides information about how to configure k3s with proxy.

Details
Note: Replace $PROXY_IP with the IP: PORT of the corporate proxy server and $NODE_IP with the IP or CIDR of the server
running Kubernetes.

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

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"

2. To restart the k3s, run the following command:

systemctl restart k3s.service

Note: The below step requires access to rancher portal, if the team does not have access to Rancher, then contact Forcepoint
technical support.

3. Navigate to Rancher Dashboard > Menu > Cluster Management > Clusters.
4. Click on the kebab menu from your cluster.
5. From the drop-down list, select Edit Config.

Figure 1: Cluster Management Dashboard

© 2021 Forcepoint Forcepoint Proprietary 2

GetVisibility: Configuring Rancher and Fleet agent to run behind HTTP proxy forcepoint.com

6. Click on Advanced Options:

Figure 2: Advanced Options

7. Configure the following Agent Environment Variables and click on 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

8. To register Rancher, run the following command:

kubectl apply -f https://. yaml

© 2021 Forcepoint Forcepoint Proprietary

3
GetVisibility: Configuring Rancher and Fleet agent to run behind HTTP proxy forcepoint.com

About Forcepoint

forcepoint.com/contact Forcepoint is the leading user and data protection cybersecurity

company, entrusted to safeguard organizations while driving
digital transformation and growth. Forcepoint’s humanly-attuned
solutions adapt in real-time to how people interact with data,
providing secure access while enabling employees to create
value. Based in Austin, Texas, Forcepoint creates safe, trusted
environments for thousands of customers worldwide.

© 2021 Forcepoint. Forcepoint and the FORCEPOINT logo are trademarks of Forcepoint.
All other trademarks used in this document are the property of their respective owners.
[Forcepoint Data Classification Powered by GetVisibility Configuring Rancher and Fleet
© 2021 Forcepoint Forcepoint Proprietary
agent to run behind HTTP proxy] [Status]20 Dec. 22 4