Nice video, yet I am afraid you are posing one misconception. OCP routes expose services, which in turn expose pods as endpoints. That is why, for instance, you may choose the route LoadBalancing policy, varying from RoundRobin to LeastConn, which is exposed on the router itself via the ENV ROUTER_LOAD_BALANCE_ALGORITHM. So, in the end of the day, OCP route is a weak attempt to beat a well-known and well-praised Ingress backed up by Traefik or Nginx, yet the approach is quite similar, they all rely on the K8S Service object to dynamically expose underlying endpoints aka pods. The mere fact that you do not see this transaction does not mean it is not there. Thanks.
Amazingly explained ❤
Nice video, yet I am afraid you are posing one misconception. OCP routes expose services, which in turn expose pods as endpoints. That is why, for instance, you may choose the route LoadBalancing policy, varying from RoundRobin to LeastConn, which is exposed on the router itself via the ENV ROUTER_LOAD_BALANCE_ALGORITHM. So, in the end of the day, OCP route is a weak attempt to beat a well-known and well-praised Ingress backed up by Traefik or Nginx, yet the approach is quite similar, they all rely on the K8S Service object to dynamically expose underlying endpoints aka pods. The mere fact that you do not see this transaction does not mean it is not there.
Thanks.
Quite insightful!