# About Cloud Service Mesh

Cloud Service Mesh is a suite of tools that helps you monitor and manage a reliable
service mesh on-premises or on Google Cloud.

## What is a service mesh?

A service mesh is an architecture that enables managed, observable, and secure
communication across your services, letting you create robust enterprise
applications made up of many microservices on your chosen infrastructure.
Service meshes factor out all the common concerns of running a service such as
monitoring, networking, and security, with consistent, powerful tools, making it
easier for service developers and operators to focus on creating and managing
great applications for their users.

Cloud Service Mesh is powered by [Istio](https://istio.io),
a highly configurable and powerful open source service mesh platform, with
tools and features that enable industry best practices. Cloud Service Mesh is
deployed as a uniform layer across your entire infrastructure. Service
developers and operators can use its rich feature set without making changes to
application code.

Architecturally, a service mesh consists of one or more control planes and a
data plane. The service mesh monitors all traffic through a proxy. On Kubernetes,
the proxy is deployed by a
[sidecar pattern](https://kubernetes.io/blog/2015/06/the-distributed-system-toolkit-patterns/#example-1-sidecar-containers)
to the microservices in the mesh. This pattern decouples application or business
logic from network functions, and enables developers to focus on the features
that the business needs. Service meshes also let operations teams and
development teams decouple their work from one another.

## How can Cloud Service Mesh help me?

With Cloud Service Mesh, you get an GKE Enterprise tested and supported
distribution of Istio, letting you create and deploy a service mesh on
GKE on Google Cloud and other
[platforms](https://docs.cloud.google.com/service-mesh/v1.20/docs/supported-platforms.md.txt)
with full Google support.

## Features

Cloud Service Mesh has a suite of features and tools that help you observe and
manage secure, reliable services in a unified way.

> [!NOTE]
> **Note:** Some features, such as Cloud Service Mesh certificate authority and the Cloud Service Mesh dashboards in the Google Cloud console aren't available on all GKE Enterprise environments. To learn about the service mesh features supported on each environment, see [In-cluster control plane supported features](https://docs.cloud.google.com/service-mesh/v1.20/docs/supported-features.md.txt).

### Traffic management

Cloud Service Mesh controls the flow of traffic between services, into the mesh
(ingress), and to outside services (egress). You configure and deploy
[Istio-compatible custom resources](https://istio.io/v1.31/docs/concepts/traffic-management/)
to manage this traffic at the application (L7) layer. For example, with the
custom resources, you can:

- Create [canary](https://martinfowler.com/bliki/CanaryRelease.html) and [blue-green](https://martinfowler.com/bliki/BlueGreenDeployment.html) deployments.
- Provide fine-grained control over specific routes for services.
- Configure [load balancing](https://docs.cloud.google.com/service-mesh/v1.20/docs/supported-features.md.txt#load_balancing_policies) between services.
- Set up [circuit breakers](https://martinfowler.com/bliki/CircuitBreaker.html).

Cloud Service Mesh maintains a service registry of all services in the mesh by
name and by their respective endpoints. It maintains the registry to manage the
flow of traffic (for example, Kubernetes Pod IP addresses). By using this
service registry, and by running the proxies side-by-side with the services, the
mesh can direct traffic to the appropriate endpoint.

### Observability insights

The Cloud Service Mesh pages in the Google Cloud console provide the following
insights into your service mesh:

- Service metrics and logs for HTTP traffic within your mesh's
  GKE cluster are automatically ingested to Google Cloud.

- Preconfigured service dashboards give you the information you need to understand
  your services.

- In-depth telemetry---powered by [Cloud Monitoring](https://docs.cloud.google.com/monitoring/docs.md.txt),
  [Cloud Logging](https://docs.cloud.google.com/logging/docs.md.txt), and [Cloud Trace](https://docs.cloud.google.com/trace/docs.md.txt)---lets you
  dig deep into your service metrics and logs. You can filter and slice your
  data on a wide variety of attributes.

- Service-to-service relationships at a glance help you understand who connects to
  each service and the services that each service depends on.

- You can quickly see the communication security posture not only of your service,
  but its relationships to other services.

- Service level objectives (SLOs) give you insight into the health of your
  services. You can easily define an SLO and alert on your own standards of
  service health.

Learn more about Cloud Service Mesh's observability features in our
[Observability guide](https://docs.cloud.google.com/service-mesh/v1.20/docs/observability-overview.md.txt).

### Security benefits

- Mitigates risk of replay or impersonation attacks that use stolen credentials.
  Cloud Service Mesh relies on mutual TLS (mTLS) certificates to authenticate
  peers, rather than bearer tokens such as
  [JSON Web Tokens](https://jwt.io/introduction/) (JWT).

- Ensures encryption in transit. Using mTLS for authentication also ensures that
  all TCP communications are encrypted in transit.

- Ensures that only authorized clients can access a service with sensitive data,
  irrespective of the network location of the client and the application-level
  credentials.

- Mitigates the risk of user data breach within your production network.
  You can ensure that insiders can only access sensitive data through
  authorized clients.

- Identifies which clients accessed a service with sensitive data.
  Cloud Service Mesh access logging captures the mTLS identity of the client in
  addition to the IP address.

- All in-cluster control plane components and proxies use
  [FIPS 140-2 validated](https://cloud.google.com/security/compliance/fips-140-2-validated) encryption
  modules.

Learn more about Cloud Service Mesh's security benefits and features in our
[Security guide](https://docs.cloud.google.com/service-mesh/v1.20/docs/security/security-overview.md.txt).

## Deployment options

You have the following deployment options in Cloud Service Mesh:

- Managed Cloud Service Mesh
- In-cluster control plane

### Managed Anthos Service Mesh

Managed Cloud Service Mesh consists of the managed control plane and the managed data
plane. With managed Cloud Service Mesh, Google handles upgrades, scaling, and
security for you, minimizing manual user maintenance. With the
managed data plane enabled, Google installs an in-cluster controller that manages
the sidecar proxies for you.

The following diagram shows the Cloud Service Mesh components and features for
managed Cloud Service Mesh:

![Managed Cloud Service Mesh](https://docs.cloud.google.com/static/service-mesh/v1.20/docs/images/mesh-arch-managed-asm.svg)

For information on setting up or migrating
to a managed Cloud Service Mesh, see
[Provision managed Cloud Service Mesh](https://docs.cloud.google.com/service-mesh/docs/managed/provision-managed-anthos-service-mesh).

### In-cluster control plane

The following diagram shows the Cloud Service Mesh components and features
for the in-cluster control plane and sidecar proxies.

![service mesh architecture with in-cluster control plane](https://docs.cloud.google.com/static/service-mesh/v1.20/docs/images/mesh-arch.svg)

For information on installing an in-cluster Cloud Service Mesh, see
[Install Cloud Service Mesh](https://docs.cloud.google.com/service-mesh/v1.20/docs/unified-install/install-anthos-service-mesh.md.txt).

## What's next?

- [Install Cloud Service Mesh](https://docs.cloud.google.com/service-mesh/v1.20/docs/unified-install/asmcli-overview.md.txt)
- [Configure transport security](https://docs.cloud.google.com/service-mesh/v1.20/docs/security/configuring-mtls.md.txt)