NodePort vs LoadBalancer vs Ingress on Google Kubernetes Engine

It can be quite daunting deciding the type of service that manages external traffic for your Workloads containing the pods running in a cluster on Google Kubernetes Engine (GKE). The best way to come to an optimal decision would first involve having a clear understanding of the different types of services and how they operate in comparison to each other.

There are three methods for dealing with external traffic namely:

  1. Proxy
  2. NodePort
  3. Ingress

By default the Kubernetes engine provisions a ClusterIP service inside your cluster to enable pods to communicate with each other internally, with external access. Continue reading “NodePort vs LoadBalancer vs Ingress on Google Kubernetes Engine”

Using Google Cloud Kubernetes Engine for faster CI/CD operations


The race for faster CI/CD operations has been the central focus for most software companies that provide devops solutions. Google Cloud Platform currently sits at the top of the list when it comes to seamless continuous integration and delivery.

I am going to talk about how we can deploy a simple Pub/Sub Python application in Google Cloud Kubernetes Engine. Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications. Now Google has built a solution thats sits on top Kubernetes and it has revolutionized the use of containers for enterprise applications that require a clustered distributed architecture, to ensure that services are highly scalable and robust during future upgrades and rollouts and even during application failures using various self-healing mechanisms. Continue reading “Using Google Cloud Kubernetes Engine for faster CI/CD operations”