What benefits does service mesh add to Cloud Run?

Service mesh adds several capabilities beyond Cloud Run's built-in traffic splitting: mutual TLS encryption between services without code changes, fine-grained traffic routing based on headers, paths, and query parameters, circuit breaker patterns for resilience, distributed tracing and metrics collection, and policy enforcement across both GKE and Cloud Run services. It is most valuable in microservice architectures where Cloud Run services communicate with each other or with GKE services.

Is Cloud Service Mesh required for Cloud Run traffic splitting?

No. Cloud Run provides built-in traffic splitting between revisions using percentage-based routing, which is sufficient for basic canary deployments and gradual rollouts. Cloud Service Mesh adds advanced routing capabilities like header-based routing, mirroring, fault injection, and circuit breakers. Use the built-in traffic splitting for simple use cases and service mesh when you need more sophisticated traffic management.

GCP Cloud Run Service Mesh Builder

ServerlessGCP

Build Cloud Run service mesh traffic configurations with weighted routing, canary deployments, and retry policies.

Cloud Run Service Mesh Configuration

Build Cloud Run service mesh traffic configurations with weighted routing, canary deployments, and retry policies.

Required Fields

serviceMesh.nameservicestrafficConfig.httpRoutes

{
  "serviceMesh": {
    "name": "prod-service-mesh",
    "project": "my-project",
    "region": "us-central1"
  },
  "services": [
    {
      "name": "frontend",
      "uri": "projects/my-project/locations/us-central1/services/frontend",
      "meshAnnotations": {
        "run.googleapis.com/mesh": "projects/123456789/locations/global/meshes/prod-mesh"
      }
    },
    {
      "name": "api-gateway",
      "uri": "projects/my-project/locations/us-central1/services/api-gateway",
      "meshAnnotations": {
        "run.googleapis.com/mesh": "projects/123456789/locations/global/meshes/prod-mesh"
      }
    },
    {
      "name": "order-service",
      "uri": "projects/my-project/locations/us-central1/services/order-service",
      "meshAnnotations": {
        "run.googleapis.com/mesh": "projects/123456789/locations/global/meshes/prod-mesh"
      }
    }
  ],
  "trafficConfig": {
    "httpRoutes": [
      {
        "name": "api-route",
        "hostnames": ["api.example.com"],
        "meshes": ["projects/123456789/locations/global/meshes/prod-mesh"],
        "rules": [
          {
            "matches": [
              {
                "path": {
                  "type": "PREFIX",
                  "value": "/v2/orders"
                },
                "headers": [
                  {
                    "header": "x-canary",
                    "type": "EXACT",
                    "value": "true"
                  }
                ]
              }
            ],
            "action": {
              "destinations": [
                {
                  "serviceName": "order-service-canary",
                  "weight": 100
                }
              ]
            }
          },
          {
            "matches": [
              {
                "path": {
                  "type": "PREFIX",
                  "value": "/v2/orders"
                }
              }
            ],
            "action": {
              "destinations": [
                {
                  "serviceName": "order-service",
                  "weight": 90
                },
                {
                  "serviceName": "order-service-canary",
                  "weight": 10
                }
              ],
              "retryPolicy": {
                "retryConditions": ["connect-failure", "refused-stream", "unavailable"],
                "numRetries": 3
              },
              "timeout": "30s",
              "faultInjectionPolicy": {
                "delay": {
                  "fixedDelay": "0s",
                  "percentage": 0
                },
                "abort": {
                  "httpStatus": 0,
                  "percentage": 0
                }
              }
            }
          }
        ]
      }
    ]
  }
}

Generated Output

Output will appear here...

About This Tool

Cloud Run now integrates with Cloud Service Mesh (formerly Anthos Service Mesh / Traffic Director) to bring service mesh capabilities — traffic management, mutual TLS, observability, and policy enforcement — to serverless containers. This lets you apply consistent networking policies across GKE and Cloud Run services. This builder helps you configure service mesh settings for Cloud Run services including traffic routing, retry policies, circuit breakers, and mTLS enforcement.

When to Use This Tool

•Configuring traffic splitting between Cloud Run revisions using service mesh routing rules for canary deployments with custom headers
•Setting up mutual TLS between Cloud Run services to encrypt all service-to-service communication without application code changes
•Building circuit breaker and retry policies for Cloud Run services that call external APIs or downstream microservices
•Defining request-based routing that directs traffic to different Cloud Run service revisions based on HTTP headers or URL paths

Frequently Asked Questions

What benefits does service mesh add to Cloud Run?: Service mesh adds several capabilities beyond Cloud Run's built-in traffic splitting: mutual TLS encryption between services without code changes, fine-grained traffic routing based on headers, paths, and query parameters, circuit breaker patterns for resilience, distributed tracing and metrics collection, and policy enforcement across both GKE and Cloud Run services. It is most valuable in microservice architectures where Cloud Run services communicate with each other or with GKE services.
Is Cloud Service Mesh required for Cloud Run traffic splitting?: No. Cloud Run provides built-in traffic splitting between revisions using percentage-based routing, which is sufficient for basic canary deployments and gradual rollouts. Cloud Service Mesh adds advanced routing capabilities like header-based routing, mirroring, fault injection, and circuit breakers. Use the built-in traffic splitting for simple use cases and service mesh when you need more sophisticated traffic management.

Related Learning Guides

Cloud Run for Production22 min read

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.

GCP Cloud Run Service Mesh Builder

ServerlessGCP

Build Cloud Run service mesh traffic configurations with weighted routing, canary deployments, and retry policies.

Cloud Run Service Mesh Configuration

Build Cloud Run service mesh traffic configurations with weighted routing, canary deployments, and retry policies.

Required Fields

serviceMesh.nameservicestrafficConfig.httpRoutes

Generated Output

Output will appear here...

About This Tool

When to Use This Tool

•Configuring traffic splitting between Cloud Run revisions using service mesh routing rules for canary deployments with custom headers
•Setting up mutual TLS between Cloud Run services to encrypt all service-to-service communication without application code changes
•Building circuit breaker and retry policies for Cloud Run services that call external APIs or downstream microservices
•Defining request-based routing that directs traffic to different Cloud Run service revisions based on HTTP headers or URL paths

Frequently Asked Questions

What benefits does service mesh add to Cloud Run?: Service mesh adds several capabilities beyond Cloud Run's built-in traffic splitting: mutual TLS encryption between services without code changes, fine-grained traffic routing based on headers, paths, and query parameters, circuit breaker patterns for resilience, distributed tracing and metrics collection, and policy enforcement across both GKE and Cloud Run services. It is most valuable in microservice architectures where Cloud Run services communicate with each other or with GKE services.
Is Cloud Service Mesh required for Cloud Run traffic splitting?: No. Cloud Run provides built-in traffic splitting between revisions using percentage-based routing, which is sufficient for basic canary deployments and gradual rollouts. Cloud Service Mesh adds advanced routing capabilities like header-based routing, mirroring, fault injection, and circuit breakers. Use the built-in traffic splitting for simple use cases and service mesh when you need more sophisticated traffic management.

Related Learning Guides

Cloud Run for Production22 min read