<p>I am able to access the <code>nginx ingress controller</code> on the <code>NodePort</code>. My goal is to access the controller on <code>port 80</code>.</p>

<blockquote>
  <p>Output of <code>kubectl -n ingress-nginx describe service/ingress-nginx</code></p>
</blockquote>

<pre><code>Name:                     ingress-nginx
Namespace:                ingress-nginx
Labels:                   app.kubernetes.io/name=ingress-nginx
                          app.kubernetes.io/part-of=ingress-nginx
Annotations:              kubectl.kubernetes.io/last-applied-configuration:
                            {"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"labels":{"app.kubernetes.io/name":"ingress-nginx","app.kubernetes.io/par...
Selector:                 app.kubernetes.io/name=ingress-nginx,app.kubernetes.io/part-of=ingress-nginx
Type:                     NodePort
IP:                       10.100.48.223
Port:                     http  80/TCP
TargetPort:               80/TCP
NodePort:                 http  30734/TCP
Endpoints:                192.168.0.8:80
Port:                     https  443/TCP
TargetPort:               443/TCP
NodePort:                 https  32609/TCP
Endpoints:                192.168.0.8:443
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   &lt;none&gt;
</code></pre>

<p>I have few ideas of solving that problem:</p>

<ul>
<li>redirect traffinc incoming on port 30734 to port 80 via <code>iptables</code></li>
<li>resize the range for nodeports so port 80 can be a nodeport as well</li>
</ul>

<p>I am not sure if these are common ways to do this, so I'd love to hear how you usually deal with this. Probably there is another component necessary?</p>

<p>The normal way to handle this is with a LoadBalancer mode service which puts a cloud load balancer in front of the existing NodePort so that you can remap the normal ports back onto it.</p>
