title: Install two traefik ingress controller on same kubernetes Cluster
body: <p>I have a situation, where I am planning to use two separate traefik ingress controller inside the Kubernetes cluster.</p>
  
  <p>I have a few URLs which I want to be accessible through VPN only, and few which can be publicly accessible.  </p>
  
  <p>In the current architecture, I have one traefik-ingress controller, and two separate ALBs, one internal and one internet-facing, both pointing to traefik.<br>
  Let's say, I have a URL <code>public.example.com</code> and <code>private.example.com</code>. <code>public.example.com</code> is pointing to internet-facing ALB, and <code>private.example.com</code> is pointing to internal ALB. But what if someone get to know the pointing of <code>public.example.com</code> and points <code>private.example.com</code> to same pointing in his <code>/etc/hosts</code>, he will be able to access my private website.  </p>
  
  <p>To avoid this, I am planning to run two separate traefik-ingress-controller, one which will be serving only private URL and one public URL. Can this be done? Or is there any other way to avoid this </p>