I suspect for either non-HTTP traffic or when you don't want to use a NodePort as per: >An Ingress…

Jun 8, 2022

1 min read

Tweaks were necessary because an ingress controller typically uses a service of type LoadBalancer to allow external access to services running in the cluster.

Kind, Cilium, MetalLB, and still no kube-proxy

Charles-Edouard Brétéché

I suspect for either non-HTTP traffic or when you don't want to use a NodePort as per:

>An Ingress does not expose arbitrary ports or protocols. Exposing services other than HTTP and HTTPS to the internet typically uses a service of type Service.Type=NodePort or Service.Type=LoadBalancer.

https://kubernetes.io/docs/concepts/services-networking/ingress/

More from Ashraf Miah

Get the Medium app

Ashraf Miah