Istio Routing Mission for Thorntail
Purpose
Showcase Routing in Istio with a Thorntail application
Prerequisites
- Docker installed and running
- OpenShift and Istio environment up and running (See https://github.com/openshift-istio/istio-docs/blob/master/content/rhoar-workflow.adoc for details)
Launcher Flow Setup
If the Booster is installed through the Launcher and the Continuous Delivery flow, no additional steps are necessary.
Skip to the Use Cases section.
Local Source to Image Build (S2I)
Prepare the Namespace
Create a new namespace/project:
oc new-project <whatever valid project name you want>
Build and Deploy the Application
With Source to Image build (S2I)
Run the following commands to apply and execute the OpenShift templates that will configure and deploy the applications:
find . | grep openshiftio | grep application | xargs -n 1 oc apply -f
oc new-app --template=thorntail-istio-routing-client-service -p SOURCE_REPOSITORY_URL=https://github.com/wildfly-swarm-openshiftio-boosters/wfswarm-istio-routing -p SOURCE_REPOSITORY_REF=master -p SOURCE_REPOSITORY_DIR=routing-client
oc new-app --template=thorntail-istio-routing-service-a-service -p SOURCE_REPOSITORY_URL=https://github.com/wildfly-swarm-openshiftio-boosters/wfswarm-istio-routing -p SOURCE_REPOSITORY_REF=master -p SOURCE_REPOSITORY_DIR=routing-service-a
oc new-app --template=thorntail-istio-routing-service-b-service -p SOURCE_REPOSITORY_URL=https://github.com/wildfly-swarm-openshiftio-boosters/wfswarm-istio-routing -p SOURCE_REPOSITORY_REF=master -p SOURCE_REPOSITORY_DIR=routing-service-bUse Cases
Any steps issuing oc commands require the user to have run oc login first and switched to the appropriate project with oc project <project name>.
Default Service load balancing
- Create a Gateway and Virtual Service in Istio so that we can access the service within the Mesh:
oc apply -f istio-config/gateway.yaml - Retrieve the URL for the Istio Ingress Gateway route, with the below command, and open it in a web browser.
echo http://$(oc get route istio-ingressgateway -o jsonpath='{.spec.host}{"\n"}' -n istio-system)/thorntail-istio-routing - The user will be presented with the web page of the Booster
- Click the "Invoke" button. You should see a message in the result box indicating which service instance was called.
- Click "Invoke" several more times. Notice that there is an even 50% split between service a and b.
Transfer load between services
- Modify the load balancing such that all requests go to service a:
oc apply -f istio-config/load-balancing-rule.yaml - Clicking on "Invoke" in the UI you will see that more requests are now being sent to service b.