設定管道會執行兩階段的設定提交作業，確保設定可靠。第一遍會執行驗證，檢查設定是否格式正確。後續階段會將設定全域傳播至服務部署作業。如要啟用 Google Cloud 服務 (例如全球跨區域或跨區域負載平衡、集中式健康狀態檢查、流量驅動的自動調度，以及受管理速率限制)，設定會傳播至這些系統，並獨立驗證正確性。此外，設定也會以內部方式儲存，讓 Google 網站可靠性工程團隊在任何生產緊急情況下，都能可靠且有效率地執行產品作業。
如果您使用代管控制層，現有車隊會遷移至新的控制層 (Cloud Service Mesh 中稱為代管控制層 (Traffic Director 或 TD 實作))，但有部分例外情形。請參閱下節「現有網格和車隊的控制層現代化」。如果您使用的功能不支援 Traffic Director 控制層實作，系統會暫時保留先前的控制層。請繼續閱讀本指南。
如果您使用叢集內控制層，控制層會維持不變。您不需要閱讀本指南的其餘部分。
如果您沒有 Google Cloud 機構，且在沒有機構的專案中使用受管理控制層，系統會提供 TD 控制層。
如果您是 Anthos 服務網格客戶，且正在建立新的車隊，系統會提供 Traffic Director 控制層實作項目。請繼續閱讀本指南。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["Managed control plane for continuing customers\n\nThis document is for you if you're a continuing Anthos Service Mesh customer\nusing the managed control plane or in-cluster control plane. This document\ndiscusses your control plane implementation and the possible modernization of your\ncontrol plane.\n\nIf you're a continuing Traffic Director customer or a new customer, you already\nhave the modernized control plane and don't need to read this document or the\nothers in this section.\n\nControl plane overview\n\nIn service meshes, the control plane provides traffic management, proxy\nmanagement when the Envoy proxy is in use, and other networking capabilities.\n\nAnthos Service Mesh offered two control planes: a managed control plane and an\nin-cluster control plane. Only Envoy proxies are used as the data plane.\n\nNew managed control plane\n\nThe new managed control plane is called the Traffic Director (TD)\nimplementation. What does the new control plane mean for you?\n\nOne of the most significant changes from the Anthos Service Mesh product to\nCloud Service Mesh is the move to a multi-tenant, global control plane.\n\nThe managed control plane used in Anthos Service Mesh is dedicated to a single\ncluster. Although the APIs (Istio CRDs) used for GKE are the same, and the xDS\nconfiguration sent to the sidecars is compatible with no behavioral differences,\nthe control plane differences result in a few characteristics that are\nvisible to you, the end user.\n\n- Configuration change response time. New service deployments, or changes to service policies, take slightly longer with the new control plane.\n - The configuration pipeline performs a two-pass configuration commit for reliability purposes. The first pass performs validations to check whether the configuration is well formed. The subsequent phase propagates the configuration globally to your service deployments. To enable use of Google Cloud services, such as global cross-zonal or cross-region load balancing, centralized health checking, traffic-driven autoscaling, and managed rate limiting, the configuration is propagated to these systems and independently validated for correctness. The configuration is also stored internally in a manner that allows Google site reliability engineering to reliably and efficiently perform product operations during any production emergencies.\n - These operations provide better reliability, but they result in a config push that is slower than the latency observed by current users of Anthos Service Mesh.\n - The latency for any new Pod to fetch existing configuration is measured to be slightly better with the new control plane. The slow configuration push is for the first-time propagation of any new service created or any new policies pushed for the service. Endpoint propagation latencies are functionally similar.\n- Speed of scaling events and other changes to the endpoints. These are handled at least as quickly with the new control plane. These events include new Pods starting or stopping because of horizontal Pod autoscaling, and Pods restarting with new IP addresses because they were moved to a different node in the cluster.\n- Scaling the number of endpoints. With the new global control plane, the endpoints of the mesh are sent directly from each cluster to the control plane from across all clusters in the mesh. This is a simpler, faster, and more scalable approach than the previous managed control plane uses. In older managed control plane (dedicated control plane) model, each Istiod must communicate with every other cluster in the mesh to determine the endpoints available in every other cluster. With the global control plane, the endpoints are propagated directly to the global control plane. This results in better reliability and performance in meshes with large numbers of endpoints and allows the meshes to scale to a larger number of endpoints.\n\nHow does the new control plane affect you?\n\nHow the new control plane affects you depends on the APIs and control plane that\nyou are using.\n\n- If you are a Traffic Director user, your control plane remains the same. You don't need to read the rest of this guide. Documentation for your Cloud Service Mesh implementation is under **Configure with\n Google Cloud APIs**.\n- If you are an Anthos Service Mesh user, the next steps for the control plane in your existing deployment depend on whether you use the managed control plane or the in-cluster control plane.\n - If you use the managed control plane, with some exceptions your existing fleets will be migrated to the new control plane, referred to in the Cloud Service Mesh as managed control plane (Traffic Director, or TD, implementation). Read the following section, [Control plane\n modernization for existing meshes and fleets](#control-plane-modernization). If you are using a feature that isn't supported by the Traffic Director control plane implementation, you remain temporarily on the previous control plane. You should continue reading this guide.\n - If you use the in-cluster control plane, your control plane remains the same. You don't need to read the rest of this guide.\n - If you don't have a Google Cloud Organization, and you use the managed control plane on an organization-less project, you will receive the TD control plane.\n- If you are an Anthos Service Mesh customer and you are creating new fleets, you will receive the Traffic Director control plane implementation. You should continue reading this guide.\n - You will be notified about [the date](#control-plane-new-meshes) when new fleets receive the TD control plane.\n\nControl plane modernization for existing meshes and fleets\n\nSee [managed control plane modernization](/service-mesh/docs/modernization).\n\nCheck control plane compatibility\n\nReview [differences in supported features between managed control plane\nimplementations](/service-mesh/docs/supported-features-managed) to determine\nwhether your current usage of Cloud Service Mesh will require changes.\n\nControl plane for new meshes\n\nStarting on July 1, 2024, most existing users of the managed `istiod` control\nplane implementation began to receive the updated managed control plane\nwith Google's globally available implementation - the Traffic Director (TD)\ncontrol plane, in *new* fleets.\n\nUsers whose existing usage of managed Cloud Service Mesh with the `istiod`\ncontrol plane implementation was not compatible with the Traffic Director\nimplementation without changes continued to get the `istiod` implementation\nuntil September 8, 2024.\n\nA small number of users were further snowflaked to get continue getting the\n`istiod` control plane implementation in new fleets. If this applies to your\norganization then you received a Service Announcement.\n\nIf you onboard a new fleet to managed Cloud Service Mesh, and this fleet is not\nin a Google Cloud Organization or it is in a new Google Cloud Organization,\nthen you will get the new managed control plane with the TD implementation from\nthe Cloud Service Mesh launch date.\n\nWhat's next\n\n- If you're a continuing Anthos Service Mesh customer, your documentation is in the left-hand table of contents under **Configure service mesh with Istio APIs**.\n- If you're a continuing Traffic Director customer, your documentation is under **Configure service mesh with Google Cloud APIs**."]]
