Showcase Routing in Istio with a Thorntail application
- Docker installed and running
- OpenShift and Istio environment up and running with mTLS enabled.
See https://github.com/openshift-istio/istio-docs/blob/master/content/rhoar-workflow.adoc for details about the Launcher workflows and setting up the docker insecure registry required to run the istiooc.
Here is the sequence showing how to get up and running with the latest OpenShift 3.11 based istiooc release.
- Download the latest istiooc release, for example:
mkdir istiooc && cd istiooc
wget -O oc https://github.com/Maistra/origin/releases/download/v3.11.0%2Bmaistra-0.7.0/istiooc_linux
chmod +x oc
export PATH=/path/to/istiooc:$PATH
Note in this case it is based on Maistra 0.7.0 openshift-ansible release: https://github.com/Maistra/openshift-ansible/releases/tag/maistra-0.7.0
- Start the cluster:
oc cluster up
Note this will apply the the istio-operator described here: https://github.com/Maistra/openshift-ansible/blob/maistra-0.7.0/istio/Installation.md#installing-the-istio-operator
- Login as system:admin, create an admin user and relogin as admin:admin
oc create user admin
oc adm policy add-cluster-role-to-user cluster-admin admin
oc login
- Apply
anyuid
andprivileged
permissions to the service account of the project you are going to use to test the booster services, by default it will be adefault
account in the projectMyProject
:
oc adm policy add-scc-to-user anyuid system:serviceaccount:myproject:default
oc adm policy add-scc-to-user privileged system:serviceaccount:myproject:default
- Deploy the Istio control plane and the Fabric8 launcher:
oc create -f cr-full.yaml
where cr-full.yaml
should look like this:
apiVersion: "istio.openshift.com/v1alpha1"
kind: "Installation"
metadata:
name: "istio-installation"
namespace: istio-operator
spec:
deployment_type: openshift
istio:
authentication: true
community: false
prefix: registry.access.redhat.com/openshift-istio-tech-preview/
version: 0.7.0
jaeger:
prefix: registry.access.redhat.com/distributed-tracing-tech-preview/
version: 1.9.0
elasticsearch_memory: 1Gi
launcher:
openshift:
user: admin
password: admin
github:
username: YOUR_GIT_ACCOUNT_ID
token: YOUR_GIT_ACCOUNT_TOKEN
where the GIT token should have public_repo
, read:org
, and admin:repo_hook
permissions.
The more complete version may look like this: https://github.com/Maistra/openshift-ansible/blob/maistra-0.7.0/istio/cr-full.yaml
but the one above is sufficient for testing the boosters. Note, setting istio.authentication
to true
enables MTLS.
- Verify the Istio Control Plane and Launcher deployments:
Now proceed to testing the booster.
If the Booster is installed through the Launcher and the Continuous Delivery flow, no additional steps are necessary.
Skip to the Use Cases section.
Create a new namespace/project:
oc new-project <whatever valid project name you want>
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-b
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>
.
- 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.
- 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.