Chapter 1. Migrating from Service Mesh 2 to Service Mesh 3

The content in this migration section applies only in the following cases:

During the migration process, you might need to reference, or you might be directed to OpenShift Service Mesh 2.x content. It can be beneficial to open "OpenShift Service Mesh 2.x" in a new tab or window for easier reference. This can be especially helpful when you move between OpenShift Service Mesh 2 ServiceMeshControlPlane resource content and OpenShift Service Mesh 3 Istio resource content.

Consider the following recommendations to limit the risk of misconfigurations or possible conflicts:

The migration guides are designed to help you move from OpenShift Service Mesh 2.6.14 to OpenShift Service Mesh 3.0, based on your deployment model:

The migration guides use the bookinfo application as an example for demonstrations purposes.

You can also migrate gateways.

Before you can begin your migration, complete the premigration checklists.

These checklists include steps for managing your network policies and configuration updates to set up add ons such as Kiali Operator provided by Red Hat and distributed tracing platform (Tempo).

After you complete the premigration checklists, you can migrate your workloads and gateways, based on your deployment model:

Depending on your deployment model, you might need to take extra steps to complete the migration. For example, when you migrate with the cert-manager tool, you need to take additional steps before you can remove OpenShift Service Mesh 2 resources.

After you complete your migration, you can add new workloads, re-create network policies, and remove OpenShift Service Mesh 2 resources.