Can you route an Kubernetes ingress resource based on port?

Question

I have a Kubernetes service that expose two ports, one for the external interface (target port 8080) and one for the admin interface (target port 8081). I\'d like to make bo

Answer 1

Via separate Ingress objects, you should be able to direct HTTP and HTTPS traffic to different ports and/or services, and hostnames can map to distinct ports and/or services.

However, Ingress currently assumes port 80 for HTTP and 443 for HTTPS for ingress, so it's not currently possible to direct traffic to ports 81 and 4431 via Ingress. I recommend using a different hostname for the admin interface.

Note that TLS is only supported in release 1.2.