# URL extension on a Traefik ingress controller to a Kubernetes pod

**URL:** <https://forum.inductiveautomation.com/t/url-extension-on-a-traefik-ingress-controller-to-a-kubernetes-pod/60197>\
**Category:** Ignition\
**Created:** [May 31, 2022, 9:26am UTC](https://forum.inductiveautomation.com/t/url-extension-on-a-traefik-ingress-controller-to-a-kubernetes-pod/60197 "2022-05-31T09:26:07Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [May 31, 2022, 3:01pm UTC](https://forum.inductiveautomation.com/t/url-extension-on-a-traefik-ingress-controller-to-a-kubernetes-pod/60197/2 "2022-05-31T15:01:44Z")

</div>

See this thread:

> [@Reverse Proxy with subpath instead of subdomain](https://forum.inductiveautomation.com/t/reverse-proxy-with-subpath-instead-of-subdomain/58596):
>
> Hi everyone, I’ve been experimenting with a Reverse Proxy (Traefik) and been succesful in placing my whole gateway in a sudomain ([http://ignition.mydomain.com](http://ignition.mydomain.com)). The Reverse Proxy handles the TLS and automatically redirects http to https. I can get to the designer, vision launcher and any perspective site. Using Traefik, it seems the necessary headers are automatically added and the only thing I had to do was implement the main/statusping rewrite (see here: [Hard coded request for HTTP in Designe…](https://forum.inductiveautomation.com/t/hard-coded-request-for-http-in-designer-launcher-even-if-gateway-set-up-for-https/34027/9)

What we really need to make this work is some additional reverse proxy awareness at the Gateway level, where we can redirect based on a configured prefix.

---

_[View the full topic](https://forum.inductiveautomation.com/t/url-extension-on-a-traefik-ingress-controller-to-a-kubernetes-pod/60197)._