[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-19。"],[],[],null,["# List Route resources\n====================\n\n\u003cbr /\u003e\n\n| **Note:** This guide only supports Cloud Service Mesh with Google Cloud APIs and does not support Istio APIs. For more information see, [Cloud Service Mesh overview](/service-mesh/docs/overview).\n\nThis document is for mesh administrators using the service routing APIs\nto configure service meshes.\n\nIn the service routing API model, `Route` resources are attached to `Mesh` or\n`Gateway` resources. In its configuration, the `Mesh` or `Gateway` resource\nreferences one or more `Route` resources.\n\nIf you are the owner of a `Mesh` or `Gateway` resource, you can list the `Route`\nresources attached to the `Mesh` or `Gateway`.\n\nEach `Mesh` or `Gateway` resource has synthetic child collection of `RouteView`\nresources. Each `RouteView` corresponds to a single `Route`. `RouteView` objects\nare created alongside `Route` objects.\n\nIn the following diagram, the `RouteView` for `Gateway` A consists of the\n`TCPRoute` resources from Project A. The `RouteView` for `Gateway` B comprises\nthe `HTTPRoute` resources from Project B and `GRPCRoute` resources from\nProject C.\n[](/static/service-mesh/docs/images/routeview.svg) The relationships among the \\`Route\\`, \\`Routeview\\`, and \\`Gateway\\` resources.(click to enlarge)\n\nThis feature is scoped to the `Mesh` or `Gateway` level. A `RouteView` for a\n`Gateway` or `Mesh` lists routes attached to that `Gateway` or `Mesh` and not\nall the routes attached to the associated scope.\n\nTo list the `RouteView` resources, issue the following command: \n\n```\ngcloud alpha network-services route-views list \\\n --location=global \\\n --[mesh | gateway]=[ MESH_NAME | GATEWAY_NAME ]\n```\n\nTo get more information on the Route itself, issue the following command: \n\n```\ngcloud alpha network-services route-views describe --route-view=ROUTEVIEW_FULLNAME\n```\n\n\u003cbr /\u003e\n\nA common workflow would be be listing the `RouteViews` for a Mesh or Gateway\nthen describing each for a full overview of the attached Routes.\n| **Note:** Google Cloud CLI wraps two endpoints for convenience. When you use the API directly, the specific `Mesh` or `Gateway` endpoint and associated requests must be used for the appropriate parent(`Mesh` or `Gateway`).\n\nYou cannot create, update, or delete `RouteView` resources. They are created,\nupdated, and deleted when their corresponding `Route` resources are created,\nupdated, and deleted.\n\nTroubleshooting\n---------------\n\n| **Important:** RouteViews were backfilled for existing resources as 'best effort' and will continue to self-heal during the course of normal HttpRoute, GrpcRoute, TcpRoute, and TlsRoute update operations. Routes not updated on or before 2024-08-20 may not be reflected with RouteViews for projects with certain security configurations.\n\nIf the route-views commands fail to list RouteViews for routes such as\n`Listed 0 items.` or not listing all known routes:\n\n- Verify that the Mesh or Gateway used in the `route-views list` are referenced within the Route's `meshes` or `gateways` fields, respectively using:\n -\n\n ```bash\n gcloud network-services [http-routes|grpc-routes|tcp-routes|tls-routes] describe \\\n --location global ROUTE_ID\n ```\n- For customers with many resources, create a support ticket for assistance.\n- Manually Trigger an update for your Route/s\n - Reimporting the route\n 1.\n\n ```bash\n gcloud network-services http-routes export my-route --location=global \\\n --destination=export.yaml\n ```\n 2.\n\n ```bash\n gcloud network-services http-routes import my-route --location=global \\\n --source=export.yaml\n ```\n - For customers using the generated NetworkServices client, call appropriate NetworkServices.Update\\*Route API.\n - Modify description to trigger Terraform automation.\n\n\u003cbr /\u003e\n\nWhat's next\n-----------\n\n- For information about how service routing works, read [Service routing overview](/service-mesh/docs/service-routing/service-routing-overview)\n- For information about the service routing APIs, read the documentation for the [network services APIs](/service-mesh/docs/reference/network-services/rest)."]]