Name: gke-gobang-app-example
Owner: Google Cloud Platform
Description: Lab: Deploy a Sample Game API Application on GKE
Created: 2016-09-09 20:34:11.0
Updated: 2018-05-19 11:00:23.0
Pushed: 2018-04-08 02:13:20.0
Size: 164
Language: Python
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
Disclaimer: This is not an official Google product.
This guide will take you through the steps to build and deploy a sample game API application with the following architecture.
The following is the fictional story of this lab.
In this section you will start your Google Cloud Shell and clone the lab code repository to it.
Click the Google Cloud Shell icon in the top-right and wait for your shell to open:
When the shell is open, set your default compute zone, and project ID which you have created for this lab.
loud config set compute/zone us-central1-a
port PROJECT_ID=$(gcloud config list project --format "value(core.project)")
Create an App Engine application. This is required to prepare the Cloud Datastore environment in the project.
loud app create --region=us-central
Clone the lab repository in your cloud shell, then cd into that dir:
t clone https://github.com/GoogleCloudPlatform/gke-gobang-app-example.git
ing into 'gke-gobang-app-example'...
gke-gobang-app-example
Build three container images corresponding to frontend, backend-dummy and backend-smart.
cker build -t frontend:v1.0 frontend/
cker build -t backend:v1.0 backend-dummy/
cker build -t backend:v1.1 backend-smart/
Run frontend and backend-dummy containers locally on the Cloud Shell instance.
cker run -d --name backend -e PROJECT_ID=$PROJECT_ID backend:v1.0
cker run -d --name frontend -p 8080:8080 -e PROJECT_ID=$PROJECT_ID \
nk backend:backend frontend:v1.0
Play the game using a CLI client. (Unfortunatelly, no fancy smartphone client app is provided at the moment.)
I_URL=http://localhost:8080/api/v1 client/client.py
ome to Gobang (Five in a Row) game.
ID (0:new game)? 0
game ID is 5649391675244544
2 3 4 5 6 7 8 9
- - - - - - - - -
- - - - - - - - -
- - - - - - - - -
- - - - - - - - -
- - - - - - - - -
- - - - - - - - -
- - - - - - - - -
- - - - - - - - -
- - - - - - - - -
- - - - - - - - -
- - - - - - - - -
uit) x(0-9), y(0-9)? 4,5
2 3 4 5 6 7 8 9
- - - - - - - - -
- - - - - - - x -
- - - - - - - - -
- - - - - - - - -
- - - - - - - - -
- - - o - - - - -
- - - - - - - - -
- - - - - - - - -
- - - - - - - - -
- - - - - - - - -
uit) x(0-9), y(0-9)? 5,5
2 3 4 5 6 7 8 9
- - - - - - - - -
- - - - - - - x -
- - - - - - - - -
- - - - - - - - -
- - - - - - - - -
- - - o o - - - -
- - - - - - - - -
- - - - - - - - -
- - - - - - - x -
- - - - - - - - -
uit) x(0-9), y(0-9)? q
game ID is 5649391675244544
you again.
Gameplay is explained by example here with the console messages. Your goal is to build a row of five consecutive stones. Please make a note of the game ID so that you can resume the game at a later time.
Stop and remove the containers on the Cloud Shell instance.
cker stop frontend backend
cker rm frontend backend
Push the container images to the Google Container Registry.
cker tag frontend:v1.0 gcr.io/$PROJECT_ID/frontend:v1.0
cker tag backend:v1.0 gcr.io/$PROJECT_ID/backend:v1.0
cker tag backend:v1.1 gcr.io/$PROJECT_ID/backend:v1.1
loud docker -- push gcr.io/$PROJECT_ID/frontend:v1.0
loud docker -- push gcr.io/$PROJECT_ID/backend:v1.0
loud docker -- push gcr.io/$PROJECT_ID/backend:v1.1
You'll use Google Container Engine to create and manage your Kubernetes cluster. Provision the cluster with gcloud:
gcloud container clusters create gobang-cluster \
--num-nodes 3 \
--scopes "https://www.googleapis.com/auth/datastore"
Once that operation completes download the credentials for your cluster using the gcloud CLI:
gcloud container clusters get-credentials gobang-cluster --zone us-central1-a
tching cluster endpoint and auth data.
beconfig entry generated for gobang-cluster.
Confirm that the cluster is running and kubectl is working by listing nodes:
kubectl get nodes
ME STATUS AGE
e-gobang-cluster-default-pool-c84a331c-a0wq Ready 1m
e-gobang-cluster-default-pool-c84a331c-h8v0 Ready 1m
e-gobang-cluster-default-pool-c84a331c-xcxx Ready 1m
You should see the list of three running nodes. The names of the nodes can be different from the example.
Replace the project id part of the image repository name in the deployment config files.
d -i "s/<PROJECT ID>/$PROJECT_ID/" config/frontend-deployment.yaml
d -i "s/<PROJECT ID>/$PROJECT_ID/" config/backend-deployment.yaml
Deploy frontend and backend pods using the deployment config files.
bectl create -f config/frontend-deployment.yaml
oyment "frontend-node" created
bectl create -f config/backend-deployment.yaml
oyment "backend-node" created
Confirm that frontend and backend pods are running.
bectl get pods
READY STATUS RESTARTS AGE
end-node-3459171109-05n3d 1/1 Running 0 30s
end-node-3459171109-0pox3 1/1 Running 0 30s
end-node-3459171109-gar1j 1/1 Running 0 30s
tend-node-3555902700-03429 1/1 Running 0 33s
tend-node-3555902700-gaslb 1/1 Running 0 33s
tend-node-3555902700-z2q5p 1/1 Running 0 33s
You should see the list of pods, three pods for frontend and three pods for backend.
Define services using the service config files.
bectl create -f config/frontend-service.yaml
ice "frontend-service" created
bectl create -f config/backend-service.yaml
ice "backend-service" created
Confirm that backend-service provides CLUSTER-IP, and frontend-service provides both CLUSTER-IP and EXTERNAL-IP.
bectl get services
CLUSTER-IP EXTERNAL-IP PORT(S) AGE
end-service 10.19.248.157 <none> 8081/TCP 1m
tend-service 10.19.246.242 104.197.109.15 80/TCP 1m
rnetes 10.19.240.1 <none> 443/TCP 13m
The CLUSTER-IP is used for the communication between pods, and the EXTERNAL-IP is used to access the service from external networks.
Now you can play the game using the CLI client again. You should specify the EXTERNAL-IP in the API URL.
I_URL=http://104.197.109.15/api/v1 client/client.py
ome to Gobang (Five in a Row) game.
ID (0:new game)? 5649391675244544
game ID is 5649391675244544
1 2 3 4 5 6 7 8 9
- - - - - - - - -
- - - - - - - x -
- - - - - - - - -
- - - - - - - - -
- - - - - - - - -
- - - o o - - - -
- - - - - - - - -
- - - - - - - - -
- - - - - - - x -
- - - - - - - - -
uit) x(0-9), y(0-9)? 4,4
1 2 3 4 5 6 7 8 9
- - - - - - - - -
- - - - - - - x -
- - - - - - - - -
- - - - - - - - -
- - - o - - - - -
- - - o o - - - -
- x - - - - - - -
- - - - - - - - -
- - - - - - - x -
- - - - - - - - -
uit) x(0-9), y(0-9)?
In this example, you resumed the previous game by specifying the game ID. But the computer player is still a dummy one. Without quitting the current game, open a new Cloud Shell terminal and go through the following operations.
Make a copy of the deployment config for backend pods, and open it with vi editor.
~/gke-gobang-app-example
config/backend-deployment.yaml config/backend-deployment-v1_1.yaml
config/backend-deployment-v1_1.yaml
Replace the image tag from v1.0 to v1.1 as below.
ec:
ntainers:
image: gcr.io/<PROJECT ID>/backend:v1.0 <-- change to v1.1
Apply the modified deployment config.
bectl apply -f config/backend-deployment-v1_1.yaml
Now, the backend pods will be automatically replaced with new images. The following events indicate that pods are replaced through the rolling update.
bectl describe deployment/backend-node
ts:
rstSeen LastSeen Count From SubobjectPath Type Reason Message
------- -------- ----- ---- ------------- -------- ------ -------
m 14m 1 {deployment-controller } Normal ScalingReplicaSet Scaled up replica set backend-node-3459171109 to 3
s 14s 1 {deployment-controller } Normal ScalingReplicaSet Scaled up replica set backend-node-3540566822 to 1
s 14s 1 {deployment-controller } Normal ScalingReplicaSet Scaled down replica set backend-node-3459171109 to 2
s 14s 1 {deployment-controller } Normal ScalingReplicaSet Scaled up replica set backend-node-3540566822 to 2
s 13s 1 {deployment-controller } Normal ScalingReplicaSet Scaled down replica set backend-node-3459171109 to 1
s 13s 1 {deployment-controller } Normal ScalingReplicaSet Scaled up replica set backend-node-3540566822 to 3
s 11s 1 {deployment-controller } Normal ScalingReplicaSet Scaled down replica set backend-node-3459171109 to 0
Then, going back to the previous terminal, continue the game.
1 2 3 4 5 6 7 8 9
- - - - - - - - -
- - - - - - - x -
- - - - - - - - -
- - - - - - - - -
- - - o - - - - -
- - - o o - - - -
- x - - - - - - -
- - - - - - - - -
- - - - - - - x -
- - - - - - - - -
uit) x(0-9), y(0-9)? 4,6
1 2 3 4 5 6 7 8 9
- - - - - - - - -
- - - - - - - x -
- - - - - - - - -
- - - - - - - - -
- - - o - - - - -
- - - o o - - - -
- x - o - - - - -
- - - x - - - - -
- - - - - - - x -
- - - - - - - - -
uit) x(0-9), y(0-9)? 4,3
1 2 3 4 5 6 7 8 9
- - - - - - - - -
- - - - - - - x -
- - - x - - - - -
- - - o - - - - -
- - - o - - - - -
- - - o o - - - -
- x - o - - - - -
- - - x - - - - -
- - - - - - - x -
- - - - - - - - -
uit) x(0-9), y(0-9)?
You will notice that the computer player has now become more intelligent!
Clean up is really easy, but also super important: if you don't follow these instructions, you will continue to be billed for the Google Container Engine cluster you created.
To clean up, navigate to the Google Developers Console Project List, choose the project you created for this lab, and delete it. That's it.