<p>I have multiple pods, that scale up and down automatically.</p>
<p>I am using an ingress as entry point. I need to route external traffic to a specific pod base on some conditions (lets say path). At the point the request is made I am sure the specific pod is up.</p>
<p>For example lets say I have domain someTest.com, that normally routes traffic to pod 1, 2 and 3 (lets say I identify them by internal ips - 192.168.1.10, 192.168.1.11 and 192.168.1.13).</p>
<p>When I call someTest.com/specialRequest/12, I need to route the traffic to 192.168.1.12, when I call someTest.com/specialRequest/13, I want to route traffic to 192.168.1.13. For normal cases (someTest.com/normalRequest) I just want to do the lb do his epic job normally.</p>
<p>If pods scale up and 192.168.1.14 appears, I need to be able to call someTest.com/specialRequest/14 and be routed to the mentioned pod.</p>
<p>Is there anyway I can achieve this?</p>

zozo
<p>I am not aware of built-in functionality to implement this (if this is what your really want). You can achieve this by building your own <a href="https://kubernetes.io/docs/concepts/extend-kubernetes/operator/" rel="nofollow noreferrer">operator</a> for Kubernetes. Your operator may provision a Pod+Ingress combo which will do exactly what you want - forward your traffic to a single pod, or you can provision 2 pods and 1 ingress to achive HA setup.</p>
<p>Depending on the Ingress you are using, it also may be possible to group multiple ingress resources under the same load balancer.</p>
<p>Here is a brief diagram of how this could look like.
<a href="https://i.stack.imgur.com/fhDMt.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/fhDMt.png" alt="example operator" /></a></p>
