Getting Started with Kubernetes Engine | GCP

Getting Started with Kubernetes

Objectives

In this lab you create a Kubernetes Engine cluster containing several containers, each containing a web server. You place a load balancer in front of the cluster and view its contents.

In this lab, you learn how to perform the following tasks:

• Provision a Kubernetes cluster using Kubernetes Engine.
• Deploy and manage Docker containers using kubectl.Sign in to the Google Cloud Platform (GCP) Console

1. Make sure that you have access to a standard web browser. The Google Chrome browser is recommended

Sign in to the Google Cloud Platform Console by using the username and password 

Confirm that needed APIs are enabled

1. Make a note of the name of your GCP project. This value is shown in the top bar of the Google Cloud Platform Console. It will be of the form qwiklabs-gcp-followed by hexadecimal numbers.
2. In the GCP Console, on the Products & Services () menu, click APIs & services.
3. Scroll down in the list of enabled APIs, and confirm that both of these APIs are enabled:

• Google Kubernetes Engine API
• Google Container Registry API

If either API is missing, click Enable APIs and Services at the top. Search for the above APIs by name and enable each for your current project. (You noted the name of your GCP project above.

Start a Kubernetes Engine cluster

1. On the Google Cloud Platform menu, click Activate Google Cloud Shell (). If a dialog box appears, click Start Cloud Shell.
2. For convenience, place the zone that assigned you to into an environment variable called MY_ZONE. At the Cloud Shell prompt, type this partial command:

export MY_ZONE=

followed by the zone that  assigned you to. Your complete command will look like this:

export MY_ZONE=us-central1-f

2. Start a Kubernetes cluster managed by Kubernetes Engine. Name the cluster webfrontend and configure it to run 2 nodes:

gcloud container clusters create webfrontend --zone $MY_ZONE --num-nodes 2

It takes several minutes to create a cluster as Kubernetes Engine provisions virtual machines for you.

3. After the cluster is created, check your installed version of Kubernetes using the kubectl version command:

kubectl version

The gcloud container clusters create command automatically authenticated kubectl for you.

4. View your running nodes in the GCP Console. On the Products & Servicesmenu, click Compute Engine > VM Instances.

Your Kubernetes cluster is now ready for use.

Run and deploy a container

1. From your Cloud Shell prompt, launch a single instance of the nginx container. (Nginx is a popular web server.)

kubectl run nginx --image=nginx:1.10.0

In Kubernetes, all containers run in pods. This use of the kubectl runcommand caused Kubernetes to create a deployment consisting of a single pod containing the nginx container. A Kubernetes deployment keeps a given number of pods up and running even in the event of failures among the nodes on which they run. In this command, you launched the default number of pods, which is 1.

2. View the pod running the nginx container:

kubectl get pods

3. Expose the nginx container outside Kubernetes:

kubectl expose deployment nginx --port 80 --type LoadBalancer

Kubernetes created a service and an external load balancer with a public IP address attached to it. The IP address remains the same for the life of the service. Any network traffic to that public IP address is routed to pods behind the service: in this case, the nginx pod.

4. View the new service:

kubectl get services

You can use the displayed external IP address to test and contact the nginx container remotely.

It may take a few seconds before the ExternalIP field is populated for your service. This is normal. Just re-run the kubectl get servicescommand every few seconds until the field is populated.

5. Open a new web browser tab and paste your cluster's external IP address into the address bar. The default home page of the Nginx browser is displayed.
6. Scale up the number of pods running on your service:

kubectl scale deployment nginx --replicas 3

Scaling up a deployment is useful when you want to increase available resources for an application that is becoming more popular.

7. Confirm that Kubernetes has updated the number of pods:

kubectl get pods

8. Confirm that your external IP address has not changed:

kubectl get services

9. Return to the web browser tab in which you viewed your cluster's external IP address. Refresh the page to confirm that the nginx web server is still responding.

Congratulations!

In this lab you configured a Kubernetes cluster in Kubernetes Engine. You populated the cluster with several pods containing an application, exposed the application, and scaled the application.

Source: Coursera