# kubectl port-forward versus kubectl proxy

**URL:** <https://discuss.kubernetes.io/t/kubectl-port-forward-versus-kubectl-proxy/1177>\
**Category:** General Discussions\
**Created:** [July 12, 2018, 2:35pm UTC](https://discuss.kubernetes.io/t/kubectl-port-forward-versus-kubectl-proxy/1177 "2018-07-12T14:35:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![thcdrt](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/thcdrt/32/667_2.png) [@thcdrt](https://discuss.kubernetes.io/u/thcdrt)\
**Post date:** [July 12, 2018, 2:35pm UTC](https://discuss.kubernetes.io/t/kubectl-port-forward-versus-kubectl-proxy/1177/1 "2018-07-12T14:35:29Z")

</div>

Hello Kubernetes community,

From what I understood kubectl port-forward allows to do the same things as kubectl proxy and more.  
Indeed kubectl port-forward allows TCP traffic, therefore HTTP, while kubectl proxy allows only HTTP…

So what is the purpose of kubectl proxy? Why don’t we have only kubectl port-forward command?

Thanks,  
Thomas

---

<div class="post-metadata">

**Author:** ![mrbobbytables](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/mrbobbytables/32/7_2.png) [@mrbobbytables](https://discuss.kubernetes.io/u/mrbobbytables)\
**Post date:** [July 19, 2018, 11:41am UTC](https://discuss.kubernetes.io/t/kubectl-port-forward-versus-kubectl-proxy/1177/2 "2018-07-19T11:41:08Z")

</div>

This question came up on yesterday’s Office Hours 🙂 I’ve linked to the specific time below:

---

<div class="post-metadata">

**Author:** ![thcdrt](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/thcdrt/32/667_2.png) [@thcdrt](https://discuss.kubernetes.io/u/thcdrt)\
**Post date:** [July 19, 2018, 12:35pm UTC](https://discuss.kubernetes.io/t/kubectl-port-forward-versus-kubectl-proxy/1177/3 "2018-07-19T12:35:00Z")

</div>

Nice ! Thanks for sharing the link.