# Provision managed Cloud Service Mesh on a GKE cluster in the Google Cloud console

Cloud Service Mesh is Google's service mesh offering, based on open source
[Istio](https://istio.io/). The Cloud Service Mesh feature in the GKE
UI allows users to easily provision
[managed Cloud Service Mesh](https://docs.cloud.google.com/service-mesh/docs/overview.md.txt#managed_anthos_service_mesh) on a
[new GKE cluster](https://docs.cloud.google.com/service-mesh/docs/managed/install-anthos-service-mesh-console.md.txt#create_a_cluster_with) or an
[existing GKE cluster](https://docs.cloud.google.com/service-mesh/docs/managed/install-anthos-service-mesh-console.md.txt#provision_on_an_existing_cluster). With
managed Cloud Service Mesh Google hosts and manages the control plane and,
optionally, the data plane for the mesh and handles its upgrades, scaling, and
security in a backward-compatible manner.

Cloud Service Mesh provides a uniform way to connect, manage, and secure
microservices. It supports managing traffic flows between services, enforcing
access policies, and aggregating telemetry data, all without requiring changes
to the microservice code. Cloud Service Mesh also provides a set of management
capabilities to simplify lifecycle management of the mesh.

You configure Istio access control, routing rules, and other features by using a
custom Kubernetes API, either via kubectl or the Istio command-line tool
istioctl, which provides extra validation.

For more information, see [Cloud Service Mesh](https://docs.cloud.google.com/service-mesh/docs/overview.md.txt).

## Before you begin

## Provision Cloud Service Mesh

The steps required to provision Cloud Service Mesh depend on whether you are
[creating a new GKE cluster](https://docs.cloud.google.com/service-mesh/docs/managed/install-anthos-service-mesh-console.md.txt#create_a_cluster_with) or
[provisioning Cloud Service Mesh on an existing GKE cluster](https://docs.cloud.google.com/service-mesh/docs/managed/install-anthos-service-mesh-console.md.txt#provision_on_an_existing_cluster).

> [!WARNING]
> **Warning:** GitOps tools (including Config Sync, Argo CD, Terraform, and Jenkins) may interfere with your Cloud Service Mesh installation, migration, or upgrade processes. For best results, disable your GitOps tools before you install, migrate, or upgrade Cloud Service Mesh.

### Create a GKE cluster with Cloud Service Mesh

*** ** * ** ***

To follow step-by-step guidance for this task directly in the
Google Cloud console, click **Guide me**:

[Guide me](https://console.cloud.google.com/?walkthrough_id=servicemesh--servicemesh_ui_autopilot_start)

*** ** * ** ***

1. Go to the **Google Kubernetes Engine** page in the Google Cloud console.

   [Go to Google Kubernetes Engine](https://console.cloud.google.com/kubernetes/list)
2. Click **Create**.

3. Click **Configure** next to your preferred option between GKE Standard and GKE Autopilot.

### Standard

In the **Cluster basics** section, complete the following:

1. Enter the **Name** for your cluster.
2. For the **Location type** , select **Regional** , and then select the
   desired [region](https://docs.cloud.google.com/service-mesh/docs/managed/supported-features-mcp#regions) for your
   cluster.

   > [!IMPORTANT]
   > **Important:** We support \> 90% of GKE cluster regions, but there are a few that are still not supported. See [Regions](https://docs.cloud.google.com/service-mesh/docs/managed/supported-features-mcp#regions) for a full list of supported regions.

3. In the navigation pane, click **Advanced settings**.

4. In the **Service Mesh** row, click **Edit feature configuration**.

5. Select the **Enable Service Mesh** checkbox.

   After you check the box, a screen detailing the requirements appears. The
   requirements include:
   - **[Cloud Monitoring](https://docs.cloud.google.com/stackdriver/docs/solutions/gke)** is enabled on the cluster.
   - Cloud Service Mesh uses Cloud Monitoring to provide automatic telemetry and logs.
   - **[Workload Identity](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/workload-identity.md.txt)** is enabled on the cluster.
   - Cloud Service Mesh uses Workload Identity to provide secure access to required Google APIs and resources.
   - In order to secure, monitor, and manage the service mesh, the
     [`mesh.googleapis.com` API](https://docs.cloud.google.com/service-mesh/docs/unified-install/project-cluster-setup#required_apis) is enabled (if it hasn't been already).

   - The Cluster is registered to the
     [project's Fleet](https://docs.cloud.google.com/anthos/multicluster-management/fleets#fleet-host-project),
     and the [Cloud Service Mesh Fleet feature](https://docs.cloud.google.com/anthos/multicluster-management/fleets#fleet-enabled-components)
     is enabled.

   - The managed control plane is provisioned and set up to use a revision
     that matches the GKE channel configured on the cluster.

6. Click **Make changes** to automatically enable the requirements, and then click **Save**.

7. Click **Create**.

### Autopilot


In the **Cluster basics** section, complete the following:

1. Enter the **Name** for your cluster.
2. Select the desired **Region** for your cluster.

   > [!IMPORTANT]
   > **Important:** We support \> 90% of GKE cluster regions, but there are a few that are still not supported. See [Regions](https://docs.cloud.google.com/service-mesh/docs/managed/supported-features-mcp#regions) for a full list of supported regions.

3. Expand the **Advanced Options** section dropdown.

4. In the **Cloud Service Mesh** section, check the box next to **Enable Cloud Service Mesh**.

   After you check the box, a screen detailing the requirements appears. The
   requirements include:
   - In order to secure, monitor, and manage the service mesh, the
     [`mesh.googleapis.com` API](https://docs.cloud.google.com/service-mesh/docs/unified-install/project-cluster-setup#required_apis)
     is enabled (if it hasn't been already).

   - The Cluster is registered to the
     [project's Fleet](https://docs.cloud.google.com/anthos/multicluster-management/fleets#fleet-host-project),
     and the [Cloud Service Mesh Fleet feature](https://docs.cloud.google.com/anthos/multicluster-management/fleets#fleet-enabled-components)
     is enabled.

   - The managed control plane is provisioned and set up to use a revision
     that matches the GKE channel configured on the cluster.

5. Click **Make changes** to automatically enable the requirements.

6. Click **Create**.

### Provision Cloud Service Mesh on an existing GKE cluster

1. Go to the **Google Kubernetes Engine** page in the Google Cloud console.

   [Go to Google Kubernetes Engine](https://console.cloud.google.com/kubernetes/list)
2. Select the cluster that you would like to provision Cloud Service Mesh on.

3. In the **Features** section, click the edit button next to Cloud Service Mesh.

   After you click the edit button, a screen detailing the requirements
   will appear. The requirements include:
   - **[Cloud Monitoring](https://docs.cloud.google.com/stackdriver/docs/solutions/gke)**
     is enabled on the cluster.

     - Cloud Service Mesh uses Cloud Monitoring to provide automatic telemetry and logs.
   - **[Workload Identity](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/workload-identity.md.txt)**
     is enabled on the cluster.

     - Cloud Service Mesh uses Workload Identity to provide secure access to required Google APIs and resources.
   - In order to secure, monitor, and manage the service mesh, the
     [`mesh.googleapis.com` API](https://docs.cloud.google.com/service-mesh/docs/unified-install/project-cluster-setup#required_apis) is enabled (if it hasn't been already).

   - The Cluster is registered to the
     [project's Fleet](https://docs.cloud.google.com/anthos/multicluster-management/fleets#fleet-host-project),
     and the [Cloud Service Mesh Fleet feature](https://docs.cloud.google.com/anthos/multicluster-management/fleets#fleet-enabled-components)
     is enabled (if it hasn't been already).

   - The managed control plane is provisioned and set up to use a revision
     that matches the GKE channel configured on the cluster.

4. Click **Make changes** to automatically enable the requirements.

## Next steps

Enabling Cloud Service Mesh on your cluster is only the first step. To fully take
advantage of service mesh functionality, complete the following tasks:

1. (Required) [Inject sidecar proxies](https://docs.cloud.google.com/service-mesh/docs/anthos-service-mesh-proxy-injection) to enhance
   network security, reliability and observability.

2. (Highly recommended) [Deploy gateways](https://docs.cloud.google.com/service-mesh/docs/operate-and-maintain/gateways.md.txt#deploy_gateways)
   to manage ingress and egress traffic.

3. (Highly recommended) [Configuring transport security](https://docs.cloud.google.com/service-mesh/docs/security/configuring-mtls.md.txt)
   to secure your mesh.

4. (Optional) [Enable Managed Data Plane](https://docs.cloud.google.com/service-mesh/docs/managed/provision-managed-anthos-service-mesh#apply_the_google-managed_data_plane_optional)
   to automatically upgrade the proxies.

## Troubleshooting

To address problems when provisioning Cloud Service Mesh, see
[Resolving issues enabling Cloud Service Mesh through Google Cloud console](https://docs.cloud.google.com/service-mesh/docs/troubleshooting/troubleshoot-ui-onboarding.md.txt).

## What's next

- To find out more about Managed Cloud Service Mesh, see [Provisioning managed Cloud Service Mesh](https://docs.cloud.google.com/service-mesh/docs/managed/provision-managed-anthos-service-mesh)
- For a quick introduction to the gcloud CLI used in this tutorial, see [`gcloud` commands](https://docs.cloud.google.com/sdk/gcloud/reference.md.txt)
- To find out how to explore Cloud Service Mesh in the Google Cloud console, see [Exploring Cloud Service Mesh in the Google Cloud console](https://docs.cloud.google.com/service-mesh/docs/observability/explore-dashboard)
- To explore Cloud Service Mesh optional features, such as Cloud Trace, distroless proxy images, and end user authentication, see [Enable optional features on managed Cloud Service Mesh](https://docs.cloud.google.com/service-mesh/docs/managed/enable-managed-anthos-service-mesh-optional-features)
- To learn more about Security in Cloud Service Mesh, see [Cloud Service Mesh Security Overview](https://docs.cloud.google.com/service-mesh/docs/security/security-overview.md.txt) and [Cloud Service Mesh Security Best Practices](https://docs.cloud.google.com/service-mesh/docs/security/anthos-service-mesh-security-best-practices.md.txt)
- To find out more about Telemetry in Cloud Service Mesh, see [Observability Overview](https://docs.cloud.google.com/service-mesh/docs/observability-overview.md.txt)