Running the Java Bookshelf on Kubernetes Engine

This tutorial shows how to run the Java Bookshelf Application on Kubernetes Engine. Follow this tutorial to containerize and deploy an existing Java web application to Kubernetes Engine. It is highly recommended that you work through the Bookshelf app documentation as part of the tutorial for the App Engine flexible environment.


  • Create a Kubernetes Engine cluster.
  • Containerize a Java application.
  • Create a replicated frontend for the Bookshelf application.
  • Create a load-balanced service to route HTTP traffic to the Bookshelf frontend.


This tutorial uses billable components of Cloud Platform, including:

  • Kubernetes Engine
  • Compute Engine
  • Cloud Storage
  • Cloud Datastore
  • Cloud Pub/Sub

Use the Pricing Calculator to generate a cost estimate based on your projected usage. New GCP users might be eligible for a free trial.

Before you begin

  1. Sign in to your Google Account.

    If you don't already have one, sign up for a new account.

  2. Select or create a GCP project.

    Go to the Manage resources page

  3. Make sure that billing is enabled for your project.

    Learn how to enable billing

  4. Enable the Cloud Datastore, Cloud Storage, Cloud Pub/Sub, and Google+ APIs.

    Enable the APIs

  5. Install and initialize the Cloud SDK.
  6. Install Docker. Docker is used to build container images locally.
  7. Install kubectl:
    gcloud components install kubectl

Creating a Kubernetes Engine cluster

A Kubernetes Engine cluster is a managed set of Compute Engine virtual machines that operate as a single Kubernetes cluster. This tutorial needs a cluster with a minimum of two nodes, and these nodes need access to all Google APIs. Replace [YOUR_GCP_ZONE] with the Cloud Platform zone where you want your cluster to be hosted.

  1. Create the cluster:

    gcloud container clusters create bookshelf \
        --scopes "cloud-platform" \
        --num-nodes 2 \
        --enable-basic-auth \
        --issue-client-certificate \
        --enable-ip-alias \
        --zone [YOUR_GCP_ZONE]
  2. Verify that you have access to the cluster:

    kubectl get nodes

    Running this command lists the nodes in your container cluster and indicates that your container cluster is up and running and you have access to it.

You use the kubectl command to create resources in a Kubernetes Engine Cluster. To learn more about kubectl, see Kubernetes Engine Cluster Operations. In general, you use gcloud to manage resources in your GCP project and you use kubectl to manage resources within your Kubernetes Engine cluster. A single project can have multiple clusters, which makes it easy to have clusters that are made up of different machine types to satisfy different needs.

When you create a cluster with gcloud, it automatically sets up authentication for kubectl. Clusters created by using the Cloud Console can set up authentication using the gcloud container clusters get-credentials command.

Cloning the sample application

The sample application is available on GitHub at GoogleCloudPlatform/getting-started-java.

  1. Clone the repository:

    git clone
  2. Navigate to the sample directory:

    cd getting-started-java/bookshelf/optional-kubernetes-engine

Initializing Datastore

The Bookshelf application uses Cloud Datastore to store the books. To initialize Datastore in your project for the first time:

  1. Open the Datastore on GCP Console.

  2. Select a region for your datastore and click Continue. When you reach the “Create an Entity” page, close the window as the Bookshelf application is ready to create entities on Datastore.

Creating a Cloud Storage bucket

The Bookshelf application uses Google Cloud Storage to store image files.

The following instructions show how to create a Cloud Storage bucket. Buckets are the basic containers that hold your data in Cloud Storage.

Name your bucket the same as your project ID.

To create a bucket:

  1. Invoke the following command:

    gsutil mb gs://[YOUR-PROJECT-ID]

    Replace [YOUR-PROJECT-ID] with your project ID.

  2. Set the bucket's default ACL to public-read to enable users to see their uploaded images:

    gsutil defacl set public-read gs://[YOUR-PROJECT-ID]

    Replace [YOUR-PROJECT-ID] with your project ID.

Containerizing the application

The sample application includes a Dockerfile, which is used create the application's Docker image. This Docker image runs the application on Kubernetes Engine.

# The Google App Engine python runtime is Debian Jessie with Python installed
# and various os-level packages to allow installation of popular Python
# libraries. The source is on github at:

# Add application code.
ADD target/bookshelf-gke-1.0-SNAPSHOT/ /app

First package the Bookshelf application:

mvn clean -DprojectID=[YOUR_PROJECT_ID] package

Build the application's Docker image:

docker build -t[YOUR_PROJECT_ID]/bookshelf .

Push the image to Google Container Registry so that your cluster can access the image:

gcloud docker -- push[YOUR_PROJECT_ID]/bookshelf

Deploying the Bookshelf front end

The Bookshelf application is comprised of a set of frontend servers that handles and processes the web requests.

The cluster resources needed to run the frontend are defined in bookshelf-frontend.yaml. These resources are described as a Kubernetes Deployment. Deployments make it easy to create and update a replica set and its associated pods.

# Copyright 2017 Google Inc.
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# See the License for the specific language governing permissions and
# limitations under the License

# This file configures the bookshelf application frontend. The frontend serves
# public web traffic.

apiVersion: extensions/v1beta1
kind: Deployment
  name: bookshelf-frontend
    app: bookshelf

# The bookshelf frontend replica set ensures that at least 3
# instances of the bookshelf app are running on the cluster.
# For more info about Pods see:
  replicas: 3

        app: bookshelf
        tier: frontend

      - name: bookshelf-app
        # Replace [GCLOUD_PROJECT] with your project ID.

        # This setting makes nodes pull the docker image every time before
        # starting the pod. This is useful when debugging, but should be turned
        # off in production.
        imagePullPolicy: Always

        # The bookshelf process listens on port 8080 for web traffic by default.
        - name: http-server
          containerPort: 8080
  1. In bookshelf-frontend.yaml, replace [GCLOUD_PROJECT] with your project ID.
  2. Use kubectl to deploy the resources to the cluster:

    kubectl create -f bookshelf-frontend.yaml
  3. Track the status of the deployment:

    kubectl get deployments

    Once the deployment has the same number of available pods as desired pods, the deployment is complete. If you run into issues with the deployment, you can delete it and start over:

    kubectl delete deployments bookshelf-frontend
  4. Once the deployment is complete you can see the pods that the deployment created:

    kubectl get pods

Creating the Bookshelf service

Kubernetes Services provide a single point of access to a set of pods. While it's possible to access a single pod, pods are ephemeral and it's usually more convenient to address a set of pods with a single endpoint. In the Bookshelf application, The Bookshelf service allows you to access the Bookshelf frontend pods from a single IP address. This service is defined in bookshelf-service.yaml

# Copyright 2017 Google Inc.
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# See the License for the specific language governing permissions and
# limitations under the License

# The bookshelf service provides a load-balancing proxy over the bookshelf
# frontend pods. By specifying the type as a 'LoadBalancer', Kubernetes Engine
# will create an external HTTP load balancer.
# For more information about Services see:
# For more information about external HTTP load balancing see:
apiVersion: v1
kind: Service

  name: bookshelf-frontend
    app: bookshelf
    tier: frontend

  type: LoadBalancer
  - port: 80
    targetPort: http-server
    app: bookshelf
    tier: frontend

Notice that the pods and the service that uses the pods are separate. Kubernetes uses labels to select the pods that a service addresses. With labels, you can have a service that addresses pods from different replica sets and have multiple services that point to an individual pod.

  1. Create the Bookshelf service:

    kubectl create -f bookshelf-service.yaml
  2. Get the service's external IP address:

    kubectl describe service bookshelf

    Note that it may take up to 60 seconds for the IP address to be allocated. The external IP address will be listed under LoadBalancer Ingress.

Accessing the Bookshelf application

You have now deployed all the resources needed to run the Bookshelf application on Kubernetes Engine. Use the external IP address from the previous step to load the application in your web browser and create books.

Cleaning up

To avoid incurring charges to your Google Cloud Platform account for the resources used in this tutorial:

Deleting the project

The easiest way to eliminate billing is to delete the project you created for the tutorial.

To delete the project:

  1. In the GCP Console, go to the Projects page.

    Go to the Projects page

  2. In the project list, select the project you want to delete and click Delete project. After selecting the checkbox next to the project name, click
      Delete project
  3. In the dialog, type the project ID, and then click Shut down to delete the project.

Deleting the cluster

Deleting the cluster removes all Kubernetes Engine and Compute Engine resources, but you need to manually remove any resources in Cloud Storage, Cloud Datastore, and Cloud Pub/Sub.

Delete the cluster using the following command. Replace [YOUR_GCP_ZONE] with the zone you used when creating the cluster.

gcloud container clusters delete bookshelf --zone [YOUR_GCP_ZONE]

What's next

Was this page helpful? Let us know how we did:

Send feedback about...