Service with type NodePort

[Pee_Tankulrat]

You can use ClusterPort on the deployment that’s exposed by an Ingress with hostname routing.

Kubernetes Ingress Support in Rancher

But! The ingress randomly make you wait 5 seconds until it is routed to the correct pods.

Nginx ingress slows occasionally?

Hi there! I’ve recently started trying out Rancher 2.0 and notice some strange behavior with hostname ingress. In my experiment, I tried deploying two replicas of tutum/hello-world image that’s linked to a service that’s then exposed by host-based ingress. In this configuration, I noticed The round-robin load balancing never kicked in If one of the replica pod is killed a 504 from nginx ingress is thrown for a few seconds There’s about a 50/50 chance that a request is delayed for 5 seconds fo…

Also! NodePort on Rancher 2.0 doesn’t seem to work either! If you need to use NodePort to connect to external loadbalancer now and doesn’t care much about Master’s HA then, I’d recommend just using Kubeadm…

Good luck