# "Tunnel Proxy" on k3s

**URL:** https://forums.suse.com/t/tunnel-proxy-on-k3s/17281
**Category:** k3s, k3OS, and k3d
**Created:** [April 27, 2020, 11:03am UTC](https://forums.suse.com/t/tunnel-proxy-on-k3s/17281 "2020-04-27T11:03:31Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Akito](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/akito/32/5805_2.png) [@Akito](https://forums.suse.com/u/Akito)
#### Post date: [April 27, 2020, 11:03am UTC](https://forums.suse.com/t/tunnel-proxy-on-k3s/17281/1 "2020-04-27T11:03:31Z")

</div>

[https://k3s.io/images/how-it-works-k3s.svg](https://k3s.io/images/how-it-works-k3s.svg)

I’m new to k3s and I am trying to understand it properly. How does the “Tunnel Proxy” element shown in above picture work in the Kubernetes and its Network Overlay context exactly? Is there any technical explanation on how exactly it works? (I am not familiar with Go.)  
Is all the communication between server and agent proxied through a special interface?  
Can a k3s Cluster behind a corporate proxy be connected to an outside Rancher instance?

---

<div class="post-metadata">

### Author: ![darshandkd](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@darshandkd](https://forums.suse.com/u/darshandkd)
#### Post date: [May 12, 2020, 3:41am UTC](https://forums.suse.com/t/tunnel-proxy-on-k3s/17281/2 "2020-05-12T03:41:46Z")

</div>

I am also new to k3s and trying to understand how proxy tunnel works in the k3s architecture. Any help is appreciated.

---

<div class="post-metadata">

### Author: ![kill-ux](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/kill-ux/32/12440_2.png) [@kill-ux](https://forums.suse.com/u/kill-ux)
#### Post date: [June 24, 2026, 11:07am UTC](https://forums.suse.com/t/tunnel-proxy-on-k3s/17281/3 "2026-06-24T11:07:29Z")

</div>

@Akito @darshandkd Tunnel Proxy is a long connection created by the sever to connect with agent(using web-socket so die die until the agent or the server kill his side end) the server use this to know which node is alive and he sends hid data to kubelet in this channel

---

<div class="post-metadata">

### Author: ![Akito](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/akito/32/5805_2.png) [@Akito](https://forums.suse.com/u/Akito)
#### Post date: [June 24, 2026, 8:53pm UTC](https://forums.suse.com/t/tunnel-proxy-on-k3s/17281/4 "2026-06-24T20:53:19Z")

</div>

Thanks. Is there any documentation on this? Where did you get this information from?

---

<div class="post-metadata">

### Author: ![kill-ux](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/kill-ux/32/12440_2.png) [@kill-ux](https://forums.suse.com/u/kill-ux)
#### Post date: [June 25, 2026, 9:40am UTC](https://forums.suse.com/t/tunnel-proxy-on-k3s/17281/5 "2026-06-25T09:40:17Z")

</div>

really i don’t remember i just read everything on front of me

---

<div class="post-metadata">

### Author: ![felixmarti46](https://avatars.discourse-cdn.com/v4/letter/f/a587f6/32.png) [@felixmarti46](https://forums.suse.com/u/felixmarti46)
#### Post date: [June 26, 2026, 8:45am UTC](https://forums.suse.com/t/tunnel-proxy-on-k3s/17281/6 "2026-06-26T08:45:24Z")

</div>

Thanks for bringing this up. I had the same question and the answers here saved me quite a bit of troubleshooting time.
