Regulatory support in Cloud Service Mesh

This document describes the features, configurations and APIs in Cloud Service Mesh that align with the controls for supported control packages. This document assumes that you're using Assured Workloads.

Data Boundary for ITAR

Supported services

The following table lists the Cloud Service Mesh APIs and versions that meet the requirements of Data Boundary for ITAR.

Service Version Status
meshconfig.googleapis.com v1alpha1 SUPPORTED

Compliance supported regions

Cloud Service Mesh is available for Data Boundary for ITAR in the following Google Cloud regions:

  • us-central1
  • us-central2
  • us-east1
  • us-east4
  • us-east5
  • us-south1
  • us-west1
  • us-west2
  • us-west3
  • us-west4
  • us-central1
  • us-central2
  • us-east1
  • us-east4
  • us-east5
  • us-south1
  • us-west1
  • us-west2
  • us-west3
  • us-west4
  • us-central1
  • us-central2
  • us-east1
  • us-east4
  • us-east5
  • us-south1
  • us-west1
  • us-west2
  • us-west3
  • us-west4
  • us-central1
  • us-central2
  • us-east1
  • us-east4
  • us-east5
  • us-south1
  • us-west1
  • us-west2
  • us-west3
  • us-west4
  • us-central1
  • us-central2
  • us-east1
  • us-east4
  • us-east5
  • us-south1
  • us-west1
  • us-west2
  • us-west3
  • us-west4

Fields not intended for Sensitive data

The following table provides an illustrative list of field categories and specific fields that aren't suitable for sensitive information. To maintain compliance, avoid placing protected data in these fields. For a complete list, contact your Google Cloud representative.

Category Fields
Control plane configuration
  • controlPlane
Deployment channel
  • channel
Fleet management
  • fleetProject
Operation timeout
  • timeout
Resource identification
  • cluster
  • location
  • name
  • project
Revision control
  • revision
Target specification
  • target
Workload identity
  • workloadIdentityPools

What's next