Nginx

In my previous post we discussed about deploying a app to the created GKE cluster. Now we will focus how we can access this app using a cost effective method. Typically to access a application deployed in GKE you can use HTTP LoadBalancers, but Google LoadBalancers are pretty expensive. As solution we are deploying a nginx pod to every node (as a Daemonset) with a config map which will contain nginx configs....

To access services deployed in your GKE cluster, you can use nginx ingress controller. You can quickly deploy nginx ingress controller via stable helm-charts. Nginx ingress controller will scan entire namespaces and will update the nginx configurations base on you ingress objects. If you want to limit your scope of nginx ingress controller, you can do that via enabling ‘scope’ and indicating which namespace you want for your scope. Enable scope in helm values file...