Stay organized with collections
Save and categorize content based on your preferences.
Adding Cloud Service Mesh (In-cluster) services to the
service perimeters
If you have created a
service perimeter in your
organization, you must add the
Certificate Authority
(Cloud Service Mesh certificate authority or Certificate Authority Service), Mesh Configuration,
Stackdriver logging, Cloud Monitoring, and Cloud Trace services to the
perimeter, in the following cases:
The cluster on which you have installed Cloud Service Mesh is in a project
that is included in a service perimeter.
The cluster on which you have installed Cloud Service Mesh is a
service project in a Shared VPC network.
By adding these services to the service perimeter, your Cloud Service Mesh
cluster can access these services. Access to the services is also restricted
within your cluster's Virtual Private Cloud (VPC) network.
Not adding the aforementioned services may cause the Cloud Service Mesh
installation to fail or cause functions to be missing. For example, if you don't
add Cloud Service Mesh certificate authority to the service perimeter, the workloads can not get
certificates from the Cloud Service Mesh certificate authority.
On the Edit VPC Service Perimeter page, under Services to
protect, click Add Services.
On the Specify services to restrict dialog, click Filter
services. Depending on your Certificate Authority (CA), enter either
Cloud Service Mesh Certificate Authority API or
Certificate Authority Service API.
Select the service's checkbox.
Click Add Cloud Service Mesh Certificate Authority API.
Repeat steps 2 - 5, to add:
Mesh Configuration API
Cloud Monitoring API
Cloud Trace API
Click Save.
gcloud
To update the list of restricted services, use the update command and
specify the services to add as a comma-delimited list:
PERIMETER_NAME is the name of the service perimeter that you
want to update.
OTHER_SERVICES is an optional comma-separated list
of one or more services to include in the perimeter in addition to the
services populated in the preceding command. For example:
storage.googleapis.com,bigquery.googleapis.com.
POLICY_NAME is the numeric name of your organization's access
policy. For example, 330193482019.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Adding Cloud Service Mesh (In-cluster) services to the service perimeters\n\nAdding Cloud Service Mesh (In-cluster) services to the\nservice perimeters\n=========================================================================\n\n| **Note:** This guide only supports Cloud Service Mesh with Istio APIs and does not support Google Cloud APIs. For more information see, [Cloud Service Mesh overview](/service-mesh/v1.24/docs/overview).\n\nIf you have created a\n[service perimeter](/vpc-service-controls/docs/service-perimeters) in your\norganization, you must add the\n[Certificate Authority](/service-mesh/v1.24/docs/unified-install/plan-install#choose_a_certificate_authority)\n(Cloud Service Mesh certificate authority or Certificate Authority Service), Mesh Configuration,\nStackdriver logging, Cloud Monitoring, and Cloud Trace services to the\nperimeter, in the following cases:\n\n- The cluster on which you have installed Cloud Service Mesh is in a project that is included in a service perimeter.\n- The cluster on which you have installed Cloud Service Mesh is a *service project* in a [Shared VPC network](/vpc/docs/shared-vpc).\n\nBy adding these services to the service perimeter, your Cloud Service Mesh\ncluster can access these services. Access to the services is also restricted\nwithin your cluster's Virtual Private Cloud (VPC) network.\n\nNot adding the aforementioned services may cause the Cloud Service Mesh\ninstallation to fail or cause functions to be missing. For example, if you don't\nadd Cloud Service Mesh certificate authority to the service perimeter, the workloads can not get\ncertificates from the Cloud Service Mesh certificate authority.\n\nBefore you begin\n----------------\n\nThe setup for the VPC Service Controls service perimeter is at the\n[organization level](/resource-manager/docs/cloud-platform-resource-hierarchy).\nEnsure that you have been granted the\n[proper roles for administering VPC Service Controls](/vpc-service-controls/docs/access-control).\nIf you have multiple projects, you can apply the service perimeter to all of\nthe projects by\n[adding each project to the service perimeter](/vpc-service-controls/docs/manage-service-perimeters#update).\n\nAdding Cloud Service Mesh services to an existing service perimeter\n-------------------------------------------------------------------\n\n### Console\n\n1. Follow the steps in [Updating a service perimeter](/vpc-service-controls/docs/manage-service-perimeters#update) to edit the perimeter.\n2. On the **Edit VPC Service Perimeter** page, under **Services to\n protect** , click **Add Services**.\n3. On the **Specify services to restrict** dialog, click **Filter\n services** . Depending on your Certificate Authority (CA), enter either **Cloud Service Mesh Certificate Authority API** or **Certificate Authority Service API**.\n4. Select the service's checkbox.\n5. Click **Add Cloud Service Mesh Certificate Authority API**.\n6. Repeat steps 2 - 5, to add:\n - **Mesh Configuration API**\n - **Cloud Monitoring API**\n - **Cloud Trace API**\n7. Click **Save**.\n\n### gcloud\n\nTo update the list of restricted services, use the `update` command and\nspecify the services to add as a comma-delimited list:\n**Note:** If your service mesh uses Certificate Authority Service, then replace `meshca.googleapis.com` with `privateca.googleapis.com` in the following command. \n\n```bash\ngcloud access-context-manager perimeters update PERIMETER_NAME \\\n --add-restricted-services=meshconfig.googleapis.com,meshca.googleapis.com,monitoring.googleapis.com,cloudtrace.googleapis.com,OTHER_SERVICES \\\n --policy=POLICY_NAME\n```\n\nWhere:\n\n- \u003cvar translate=\"no\"\u003ePERIMETER_NAME\u003c/var\u003e is the name of the service perimeter that you\n want to update.\n\n- \u003cvar translate=\"no\"\u003eOTHER_SERVICES\u003c/var\u003e is an optional comma-separated list\n of one or more services to include in the perimeter in addition to the\n services populated in the preceding command. For example:\n `storage.googleapis.com,bigquery.googleapis.com`.\n\n- \u003cvar translate=\"no\"\u003ePOLICY_NAME\u003c/var\u003e is the numeric name of your organization's access\n policy. For example, `330193482019`.\n\nRefer to\n[Updating a service perimeter](/vpc-service-controls/docs/manage-service-perimeters#update)\nfor additional information."]]
