Bookinfo Application
This example deploys a sample application composed of four separate microservices used to demonstrate various Istio features.
The application displays information about a book, similar to a single catalog entry of an online book store. Displayed on the page is a description of the book, book details (ISBN, number of pages, and so on), and a few book reviews.
The Bookinfo application is broken into four separate microservices:
productpage. Theproductpagemicroservice calls thedetailsandreviewsmicroservices to populate the page.details. Thedetailsmicroservice contains book information.reviews. Thereviewsmicroservice contains book reviews. It also calls theratingsmicroservice.ratings. Theratingsmicroservice contains book ranking information that accompanies a book review.
There are 3 versions of the reviews microservice:
- Version v1 doesn’t call the
ratingsservice. - Version v2 calls the
ratingsservice, and displays each rating as 1 to 5 black stars. - Version v3 calls the
ratingsservice, and displays each rating as 1 to 5 red stars.
The end-to-end architecture of the application is shown below.
This application is polyglot, i.e., the microservices are written in different languages.
It’s worth noting that these services have no dependencies on Istio, but make an interesting
service mesh example, particularly because of the multitude of services, languages and versions
for the reviews service.
Before you begin
If you haven’t already done so, setup Istio by following the instructions in the installation guide.
Deploying the application
To run the sample with Istio requires no changes to the application itself. Instead, you simply need to configure and run the services in an Istio-enabled environment, with Envoy sidecars injected along side each service. The resulting deployment will look like this:
All of the microservices will be packaged with an Envoy sidecar that intercepts incoming and outgoing calls for the services, providing the hooks needed to externally control, via the Istio control plane, routing, telemetry collection, and policy enforcement for the application as a whole.
Start the application services
Change directory to the root of the Istio installation.
The default Istio installation uses automatic sidecar injection. Label the namespace that will host the application with
istio-injection=enabled:$ kubectl label namespace default istio-injection=enabledDeploy your application using the
kubectlcommand:$ kubectl apply -f @samples/bookinfo/platform/kube/bookinfo.yaml@The command launches all four services shown in the
bookinfoapplication architecture diagram. All 3 versions of the reviews service, v1, v2, and v3, are started.Confirm all services and pods are correctly defined and running:
$ kubectl get services NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE details ClusterIP 10.0.0.31 <none> 9080/TCP 6m kubernetes ClusterIP 10.0.0.1 <none> 443/TCP 7d productpage ClusterIP 10.0.0.120 <none> 9080/TCP 6m ratings ClusterIP 10.0.0.15 <none> 9080/TCP 6m reviews ClusterIP 10.0.0.170 <none> 9080/TCP 6mand
$ kubectl get pods NAME READY STATUS RESTARTS AGE details-v1-1520924117-48z17 2/2 Running 0 6m productpage-v1-560495357-jk1lz 2/2 Running 0 6m ratings-v1-734492171-rnr5l 2/2 Running 0 6m reviews-v1-874083890-f0qf0 2/2 Running 0 6m reviews-v2-1343845940-b34q5 2/2 Running 0 6m reviews-v3-1813607990-8ch52 2/2 Running 0 6mTo confirm that the Bookinfo application is running, send a request to it by a
curlcommand from some pod, for example fromratings:$ kubectl exec "$(kubectl get pod -l app=ratings -o jsonpath='{.items[0].metadata.name}')" -c ratings -- curl -sS productpage:9080/productpage | grep -o "<title>.*</title>" <title>Simple Bookstore App</title>
Determine the ingress IP and port
Now that the Bookinfo services are up and running, you need to make the application accessible from outside of your Kubernetes cluster, e.g., from a browser. A gateway is used for this purpose.
Create a gateway for the Bookinfo application:
Create an Istio Gateway using the following command:
$ kubectl apply -f @samples/bookinfo/networking/bookinfo-gateway.yaml@ gateway.networking.istio.io/bookinfo-gateway created virtualservice.networking.istio.io/bookinfo createdConfirm the gateway has been created:
$ kubectl get gateway NAME AGE bookinfo-gateway 32sFollow these instructions to set the
INGRESS_HOSTandINGRESS_PORTvariables for accessing the gateway. Return here, when they are set.Create a Kubernetes Gateway using the following command:
$ kubectl apply -f @samples/bookinfo/gateway-api/bookinfo-gateway.yaml@ gateway.gateway.networking.k8s.io/bookinfo-gateway created httproute.gateway.networking.k8s.io/bookinfo createdBecause creating a Kubernetes
Gatewayresource will also deploy an associated proxy service, run the following command to wait for the gateway to be ready:$ kubectl wait --for=condition=programmed gtw bookinfo-gatewayGet the gateway address and port from the bookinfo gateway resource:
$ export INGRESS_HOST=$(kubectl get gtw bookinfo-gateway -o jsonpath='{.status.addresses[0].value}') $ export INGRESS_PORT=$(kubectl get gtw bookinfo-gateway -o jsonpath='{.spec.listeners[?(@.name=="http")].port}')Set
GATEWAY_URL:$ export GATEWAY_URL=$INGRESS_HOST:$INGRESS_PORT
Confirm the app is accessible from outside the cluster
To confirm that the Bookinfo application is accessible from outside the cluster, run the following curl command:
$ curl -s "http://${GATEWAY_URL}/productpage" | grep -o "<title>.*</title>"
<title>Simple Bookstore App</title>You can also point your browser to http://$GATEWAY_URL/productpage
to view the Bookinfo web page. If you refresh the page several times, you should
see different versions of reviews shown in productpage, presented in a round robin style (red
stars, black stars, no stars), since we haven’t yet used Istio to control the
version routing.
Define the service versions
Before you can use Istio to control the Bookinfo version routing, you need to define the available versions.
Istio uses subsets, in destination rules, to define versions of a service. Run the following command to create default destination rules for the Bookinfo services:
$ kubectl apply -f @samples/bookinfo/networking/destination-rule-all.yaml@Wait a few seconds for the destination rules to propagate.
You can display the destination rules with the following command:
$ kubectl get destinationrules -o yamlUnlike the Istio API, which uses DestinationRule subsets to define the versions of a service,
the Kubernetes Gateway API uses backend service definitions for this purpose.
Run the following command to create backend service definitions for the three versions of the reviews service:
$ kubectl apply -f @samples/bookinfo/platform/kube/bookinfo-versions.yaml@What’s next
You can now use this sample to experiment with Istio’s features for traffic routing, fault injection, rate limiting, etc. To proceed, refer to one or more of the Istio Tasks, depending on your interest. Configuring Request Routing is a good place to start for beginners.
Cleanup
When you’re finished experimenting with the Bookinfo sample, uninstall and clean it up using the following command:
$ @samples/bookinfo/platform/kube/cleanup.sh@