Migrate from Gloo Mesh v1 to v2
Gloo Mesh Enterprise version 2.0 sets up new custom resources for scalable, multitenant service mesh environments.
Request migration support
To get started, submit a request for Support to help you through the migration process. Include the following details:
- Subject: Migrating Gloo Mesh Enterprise 1.2 to 2.0
- Description: Copy in your premigration checklist along with any other concerns that you might have. You can also include attachments.
Benefits of migrating
When you migrate to Gloo Mesh Enterprise 2.0, you unlock key new benefits such as the following:
- Workspaces to automatically onboard your app teams across multiple namespaces, clusters, and meshes.
- Gloo Mesh-managed Istio installation for scalable clusters.
- Flexible and reusable policies that apply to both ingress (“north-south”) and cross-mesh (“east-west”) traffic.
- Virtual machine onboarding to extend your mesh beyond your Kubernetes cluster setup.
For more information, see the following docs.
Comparison of v1 and v2
Review the key benefits and compare important differences between Gloo Mesh v1 and v2 APIs.
API core concepts
Review the core concepts behind Gloo Mesh, along with how the v2 API is organized.
Review the following considerations before you request a migration. You can also discuss these areas or any others with your Solo Account Representative. For more details, see the Migration process.
Cluster hardware and software resources
You currently run a version of Kubernetes and Istio that Gloo Mesh v2 supports.
You currently run Gloo Mesh Enterprise version 1.2.
You have enough resources to either create a new management cluster, or to run two management servers simultaneously in your existing cluster.
Gather configuration details for any services that you integrate Gloo Mesh with, such as:
- Certificate management tools like AWS ACM or Vault
- GitOps and CI/CD tooling such as ArgoCD
Identify any external services such as in VMs that you want to extend your mesh to.
Describe your cluster environment, including:
- Number and size of workload clusters
- Region and zone locations
- Public, private, and edge networks, including external load balancers
- Attached storage devices
Gloo Mesh, Istio, and Kubernetes resources
Make backups of cluster resources, including the following:
- Kubernetes resources
- Istio resources
- Gloo Mesh v1 resources
Identify any resources that you do NOT want to migrate, such as outdated apps.
Gather the Kubernetes RBAC, Gloo Mesh RBAC, and other permissions for current team.
v2 API strategy
- Review the API groups of objects that you can create with API v2.
- Decide if you want to set up workspaces for your multi-tenant teams. Otherwise, you can create one workspace by default and set up more fine-grained workspaces later on.
- Make sure that you have a labelling strategy for your resources. The Gloo Mesh v2 API relies on selectors to choose objects. For example, labels select the policies to apply to resources like virtual destinations. For more information about labels and selectors, see the Kubernetes documentation.