Google Cloud GKE
Step 1: Create a Kubernetes cluster
1) Create a Google Cloud Platform (GCP) account
2) Install CLI
3) Create a Kubernetes cluster (GKE)
To create a new Kubernetes cluster, go to your GCP Console Home Page (https://console.cloud.google.com) and select Kubernetes Engine / Clusters.
Then select the CREATE CLUSTER button 
from the top menu.
Enter the Cluster Name, select the Zone based on your location and I’ve selected 2 vCPUs and left the Size to the default value (3).
GKE cluster creation settings
Once the cluster is created click on the Connect Button on the right hand side of the table:
Kubernetes clusters list view
This will open a popup with a command to connect to the cluster. Copy it to your clipboard, open a terminal and paste the command into your terminal.
Note: if you are working with an existing cluster, you will need to check if you have an Ingress Controller already installed, you can skip the NGINX Ingress installation (step 2) if that is the case.
Step 2: Configure HELM and install NGINX Ingress
Let's now configure HELM to work in the Cluster. We first need to give HELM permissions to deploy things into the cluster. Download the file below:
helm-service-account-role.yaml
347B
Code
helm-service-account-role.yaml
Run the following commands in your terminal:
1
kubectl apply -f helm-service-account-role.yaml
Copied!
1
helm init --service-account helm --upgrade
Copied!
In order to be able to expose our services to be accessed from outside the cluster, we need to set up an Ingress Controller, which will automatically create routes to the internal services that we want to expose. To install the NGINX Ingress controller, run the following command:
1
helm install stable/nginx-ingress --version 1.5
Copied!
Now that NGINX Ingress Controller is being deployed, we need to wait for it to expose itself using a Public IP. We need this Public IP to interact with our services from outside the cluster. You can find this IP by running the following command:
1
kubectl get services
Copied!
Example output with GCP deployment:
External IP for NGINX Ingress controller.
Last modified 5mo ago