これらのオペレーションにより信頼性が向上しますが、Anthos Service Mesh の現在のユーザーによって観察されるレイテンシよりも構成プッシュが遅くなります。
新しい Pod が既存の構成を取得するレイテンシは、新しいコントロール プレーンではわずかに短縮されていることが測定されています。低速構成プッシュは、作成された新しいサービスや、サービスにプッシュされた新しいポリシーの初回伝播用です。エンドポイントの伝播レイテンシは機能的に類似しています。
エンドポイントに対するスケーリング イベントやその他の変更の速度。これらは、新しいコントロール プレーンでも少なくとも同じ速さで処理されます。これらのイベントには、水平 Pod 自動スケーリングによる新しい Pod の起動または停止、Pod がクラスタ内の別のノードに移動されたことによる新しい IP アドレスでの Pod の再起動などがあります。
新しいフリートをマネージド Cloud Service Mesh にオンボーディングし、このフリートが Google Cloud 組織に存在しないか、新しい Google Cloud 組織にある場合、Cloud Service Mesh のリリース日から TD 実装をベースとする新しいマネージド コントロール プレーンが提供されます。
次のステップ
Anthos Service Mesh の継続的なお客様の場合は、左側の目次の Istio API でサービス メッシュを構成するをご覧ください。
Traffic Director の継続的なお客様の場合は、 Google Cloud API でサービス メッシュを構成するをご覧ください。
[[["わかりやすい","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 UTC。"],[],[],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**."]]
