<p>I have a kubernetes setup running in google container engine. one of the k8s Service "type: LoadBalancer"... so i guess it created a Google Network Load Balancing. Now part of my billing 
"Compute Engine Network Load Balancing" is way higher than my compute engine cost. Is there a way to eliminate "Network Load Balancing" cost item with any other solution in kubernates...please advise.</p>

<p>This question is close to what I'm looking for:</p>

<p><a href="https://stackoverflow.com/questions/44493779/gcp-kube-lego-forwarding-rule-pricing">GCP Kube-Lego forwarding rule pricing</a></p>

<p>...but no answers so far.</p>

<p>1) Deploy nginx-ingress-controller to kube-cluster:</p>

<pre><code>helm install --name my-lb stable/nginx-ingress --set controller.service.type=NodePort
helm list
kubectl get svc 
</code></pre>

<p>This will create "my-lb-nginx-ingress-controller" - a custom nginx load balancer instead of gke-load-balancer(google's). This will implement ingress rule objects in the kube-cluster.
   *** After this, any ingress rule object created with "annotations: kubernetes.io/ingress.class: nginx", will be enforced by this ngnix-controller.</p>

<p>2) Create firewall rule to open nodePorts:
   Since nginx-controller deployed as "conroller.service.type=NodePort", check the nodePorts from "kubect get svc" command and create gcloud "networking/firewall" rule to allow ports "tcp:31181;tcp:31462". Now you can use browser to reach "<a href="http://node-ip-address:31181" rel="nofollow noreferrer">http://node-ip-address:31181</a>" or "<a href="https://node-ip-address:31462" rel="nofollow noreferrer">https://node-ip-address:31462</a>" reach ngnix controllers..</p>

<p>3) Delete stuff:</p>

<pre><code>helm delete my-lb
helm del --purge my-lb
</code></pre>

<p>I did above in gke, and now i have ngnix-load-balancer instead of google's cloud-load-balancer. But one limitation i experience is "<a href="http://node-ip:80" rel="nofollow noreferrer">http://node-ip:80</a>" gets connection refused...don't know why is this. But, access through nodeport "<a href="http://node-ip-address:31181" rel="nofollow noreferrer">http://node-ip-address:31181</a>" is working. Ok for now, have to figure out port 80 access denial.</p>
