Este contenido no está disponible en el idioma seleccionado.

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


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

  • You are an existing Red Hat OpenShift Service Mesh user running OpenShift Service Mesh 2.6.9.
  • You want to move to OpenShift Service Mesh 3.0.
Important

If you are not running OpenShift Service Mesh 2.6.9, you must update before you can continue. For more information, see Upgrading Service Mesh.

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.

1.1. Recommendations for migrating

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

  • If you have automated updates configured in the OpenShift Container Platform web console, change them to Manual. By switching to manual updates, you can prevent updates to the OpenShift Service Mesh 2 Operator and control planes during your migration.
  • Keep the amount of the service mesh configuration changes, such as changes for traffic management or security or adding new workloads or gateways, to a minimum during the migration.
Note

If you need to add a new workload namespace during the migration, it must be managed by the OpenShift Service Mesh 3 control plane and labeled with maistra.io/ignore-namespace: "true" to avoid conflicts between the OpenShift Service Mesh 3 control plane and the OpenShift Service Mesh 2 ServiceMeshControlPlane resource.

  • Finish the migration without unnecessary delays.

1.1.1. Using the migration guides

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

  • Mulitenant
  • Mulitenant with cert-manager
  • Cluster-wide
  • Cluster-wide with cert-manager

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

You can also migrate gateways.

1.2. Premigration checklists

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).

1.3. Migrating your deployment and workloads

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

  • Mulitenant
  • Mulitenant with cert-manager
  • Cluster-wide
  • Cluster-wide with cert-manager

1.4. Completing your migration

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.

Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat