sgrman / simple_whackapod Goto Github PK

This repo contains a yaml based approach to deploying Whack-a-Pod. The original repository was by Terrance Ryan and can be found at https://github.com/tpryan/whack_a_pod.

From the original repo:

"This is a demo that can be used to show how resilient services running on Kubernetes can be. Main app shows a giant sign that flashes in various random colors. Those colors come a Kubernetes powered microservice. If the service goes down, the sign turns red. Your goal is to try and knock the service down by killing the Kubernetes pods that run the service. You can do that by whacking the pods wich are respresented as moles."

There is also a less busy verison of the game available at /next.html. This version has an advanced mode that allows someone to do a more visual explanation of the mechanics.

The original repo directions assumed you were using Google Cloud Platform to take advantage of Container Engine to build a manage your Kubernetes cluster.

With the help of @nvpnathan, this repo provides a deployment methodology based on yaml files to deploy the required resources and configs for deployment of the application. The container images used in these yaml files are the same from the original repo.

On your environment, download or clone the files the .yaml files to a directory of your choice

git clone https://github.com/sgrman/simple_whackapod.git

Two namespaces are deployed for this application. The first is wap-admin and the second is wap-game. The wap-admin namespace is where the containers supporting the admin, api and game deployment will reside. The wap-game namespace is used by the game for the deployment of simulated kubernetes pods that you will attempt to "whack" or "kill".

Once authenticated to your environment delpoy the namespaces:

kubectl apply -f namespace.yaml

kubectl config set-context <your cluster> --namespace wap-admin

*note if you have kubens installed, you can use

kubens wap-admin

This yaml will create a service account 'wap-admin' and bind it to a cluster admin role. It is important that this step be completed prior to the deployment of the 'admin-deployment.yaml'. The service account will be applied to that deployment and you cannot change the service account once the pods for a given deployment are already deployed.

kubectl apply -f service-account-cluster-role.yaml

This will deploy 12 replicas for the "api" tier, 4 replicas for the "game" tier and 1 pod for the "admin" teir. In addition, each yaml will define and expose a service for each deployment. As mentioned above, the "admin-deployment" tier will also apply the previously created 'wap-admin' service tier and specify the 'wap-game' namespace for the deployment of the simulated kubernetes pods that will be the target of the game.

kubectl apply -f api-deployment.yaml
kubectl apply -f game-deployment.yaml
kubectl apply -f admin-deployment.yaml

This yaml will deploy and ingress for the application. You may need to change the host value in line 23 for your environment.

kubectl apply -f wap-ingress.yaml

That's it! You should be able to use your use your ingress IP or hostname value (provided you have the appropriate DNS config) to log into the application.

This is my first repo, so special thanks to @nvpnathan for his help and again to Terrance Ryan for the original application repo.