I know we discussed this over slack, but I thought I'd answer the question here too, so others might be aware of a possible solution.
From what I understood you are after an ingress controller which can be used to route incoming traffic to the service/deployment requested.
i.e; this.example.com would be your domain.
You've deployed a pod consisting of multiple containers.
Theoretically you could have the following ingress setup;
- host: this.example.com
- path: /one
- path: /two
- path: /three
In this ingress we've specified the same service, but each of which have different ports.
When a user navigates to
this.example.com/one The traffic comes into the Ingress Controller setup, it checks for any matching rules and if there are some directs the traffic to the service.
The service itself will have an endpoint, which the traffic is directed to. This would be the pod, (or if you have many replicas any one of them).
These resources might be of assistance in setting up an ingress controller.