This message was deleted.

Please do not use nodeports, if you wish to expose a limited amount of tcp ports, please use ingress tcp exposing https://kubernetes.github.io/ingress-nginx/user-guide/exposing-tcp-udp-services/ If you wish to expose a lot of ports, i believe using istio is a better solution

Hi @powerful-librarian-10572 thank you for your reply. Can you explain why I should not use node ports? I’m new to rancher and trying to experiment with the basics in my homelab. It’s only one port I’m trying to expose. I’m not currently using NGINX and am not in a hosted cloud provider with LB support. Is this something that will require me to start using NGINX instead of the default K8s ingress resource?

If you use rancher, nginx is the default ingress. Nodeports iirc are just not a recommended way of doing things in k8s. Also istio is WAY more complex than Nginx

I realized that nginx is already the default shortly after sending 😆 because I created an ingress without specifying the ingress class and saw it defaulted to that. So you think it’s acceptable to use nginx for this despite it not being officially supported? I guess I don’t really know all the implications of it. Maybe it works fine and is perfectly stable but always scares me off to hear stuff like that

I hope it's acceptable because i'm using it in production 😉

For on-prem solution - if you have IP address(es) available then you can also use MetalLB - you can deploy it from Apps in Rancher.