Red Hat Bugzilla – Bug 1303232
[RFE] Supporting non HTTP[s](80/443) traffic routes [traffic ingress]
Last modified: 2016-02-22 11:23:32 EST
Description of problem:
Allow services/applications to bind to not http(s) ports such as an application hosting content at 80 and 443 but have a rest cli at 8180. We should be able to expose multiple ports from one service or expose more than one service, and its port, on a single pod.
Currently the view point for this issue is that we do not support non-http(s)/non-SNI but that it is loosely possible by customizing the router. But there has also been disagreement on the viability of actually exposing these because of how ports should be handled or are handled.
It has been discussed what needs to be modified, the NodePort, which may or may not be non-functional, the HostPort, or the HostNetwork.
I was able to find a trello card  that discusses this topic.
Our default answer for exposing ports in NodePort. We should ensure we have clear requirements about what the gaps are in the existing NodePort solution (claiming known ports) so that whatever is built on top of service node ports are clear.
*** This bug has been marked as a duplicate of bug 1287471 ***