Skip to content

Latest commit

 

History

History
executable file
·
91 lines (49 loc) · 4.59 KB

OS4ServiceMesh.md

File metadata and controls

executable file
·
91 lines (49 loc) · 4.59 KB

Installing Istio aka OpenShift Service Mesh on your OpenShift Cluster

Install Istio on OpenShift 4

Istio is called 'Red Hat OpenShift Service Mesh' on OpenShift and is installed with the help of multiple operators:

  • Elasticsearch
  • Jaeger
  • Kiali
  • OpenShift Service Mesh (= Istio)

You only need to install the OpenShift Service Mesh operator, it will pull in the others.

Follow these steps:

  1. In the OpenShift dashboard, switch to the Adminstrator view, then open Operators and OperatorHub. This will show the OperatorHub catalog (could take a moment). Select Project: 'openshift-operators':

    operatorhub

  2. Enter 'openshift service mesh' in the search field, and select the 'Red Hat OpenShift Service Mesh provided by Red Hat, Inc', not the "Community" version!

  3. Click 'Install' on the next dialog.

  4. Keep the defaults for Installation Mode and Approval Strategy and click 'Subscribe'.

    crt subscr

  5. The dashboard switches to the 'Installed Operators' view. After a moment you will see 4 operators being installed: Elasticsearch, Jaeger, Kiali, and OpenShift Service Mesh. Wait a few minutes until the status shows 'InstallSucceeded' for all of them. In the end you should see these 4 operators:

    installed ops

    This shows that we have all required operators in place. Next we will create the Istio / Service Mesh control plane.

In upstream Kubernetes you install (upstream) Istio or its control plane only once. In OpenShift you can install multiple Service Mesh control planes with different configurations that control different projects/namespaces.

  1. Create a project for the Service Mesh control plane. Call it 'istio-system' to be consistent with the Istio installations of the other platforms.

    Use the OpenShift Console (Administrator view -> Home -> Projects -> 'Create Project') or the oc CLI for this.

  2. Go to the 'Installed Operators' view and make sure that project 'istio-system' is selected. It may take a moment for the operators to show up, they are copied into this namespace.

  3. Click on the 'Red Hat OpenShift Service Mesh' operator and select the 'Istio Service Mesh Control Plane' API:

    crt istio cp

  4. Click on 'Create instance' and have a look at the YAML definition:

    • Name is 'basic-install' into namespace 'istio-system'
    • auto scaling is off, traceSampling 100 (which is OK for a demo)
    • jaeger is using the 'all-in-one' template

    Click 'Create'. This will take several minutes to complete, it took some 10 minutes when I last tried.

  5. Go to Administrator -> Home -> Projects, and open the 'istio-system' project.

    In the project view, open the 'Workloads' tab.

    You will see 3 applications: istio, jaeger, and kiali

    Click on the kiali deployment (D) and open the Resources tab of the kiali deployment:

    istio-system kiali

    Click on the route.

    • When using CRC accept the self-signed certificate. Log in with user 'kubeadmin' and the password displayed when you started CRC or use crc console --credentials to redisplay them for you.
    • On IBM Cloud you will logged in with your IAM credentials automatically.

    You should see the Kiali console now.

Next, we add an Istio Service Mesh Member Roll which is basically just a list of namespaces/projects that belong to our Service Mesh control plane.

  1. Create a new project 'cloud-native-starter'. It will hold our sample application later.

  2. Go to 'Installed Operators', Project: istio-system, and click on 'Red Hat OpenShift Service Mesh'

    member roll 1

  3. Click on 'Create instance' for 'Istio Service Mesh Member Roll' API

  4. As members, add 'cloud-native-starter', click 'Create':

    member roll 1

Istio aka OpenShift Service Mesh is now installed and functional in your OpenShift cluster.

With upstream Istio you would add a label to the cloud-native-starter namespace to enable Istio sidecar auto injection. This is not available in OpenShift. Instead, you need to opt in and add an annotation to each of your deployment YAML files to add sidecar auto injection. "Opting in ensures the sidecar injection does not interfere with other OpenShift features such as builder pods used by numerous frameworks within the OpenShift ecosystem."

Continue with the Requirements for OpenShift