membershipStates:
projects/656460026795/locations/us-central1/memberships/cluster:
servicemesh:
conditions:
- code: MODERNIZATION_SCHEDULED
details: This cluster has been scheduled for modernization on or after (date ~ at least 2 weeks).
documentationLink:
severity: INFO
使用 meshconfig.googleapis.com API 注册的任何旧版托管式控制平面集群都将通过 gkehub.googleapis.com Membership 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"]],["最后更新时间 (UTC)：2025-09-03。"],[],[],null,["# Managed control plane modernization\n===================================\n\nStarting on July 22, 2024, Google will gradually update existing clusters to use\nthe managed control plane with TD implementation. You will be notified before we\nupdate your meshes.\n\nYou can review the capabilities of the Istiod and Traffic Director control planes\non the page that describes [Supported features using Istio APIs (managed control\nplane)](/service-mesh/v1.23/docs/supported-features-managed).\n\nScheduling and Notification\n---------------------------\n\nYou should receive notification that a cluster is scheduled to be updated at least two\nweeks before the update. Notifications are available in your cluster-level\nfeature state conditions.\n\nUse the following Google Cloud CLI command to check the notification: \n\n```\ngcloud container fleet mesh describe --project=PROJECT_ID\n```\n\nYou see results similar to the following: \n\n```\nmembershipStates:\n projects/656460026795/locations/us-central1/memberships/cluster:\n servicemesh:\n conditions:\n - code: MODERNIZATION_SCHEDULED\n details: This cluster has been scheduled for modernization on or after (date ~ at least 2 weeks).\n documentationLink: \n severity: INFO\n```\n\nAny legacy managed control plane clusters that were onboarded using the\n`meshconfig.googleapis.com` API will be automatically registered to the fleet\nin the cluster's project with the `gkehub.googleapis.com` Membership API. If\nyou have any automation that deregisters a cluster, you must remove it before\nmodernization or the modernization will have issues. For the managed product\nto work successfully, it must be registered to a fleet with the mesh feature\nenabled.\n\n[Contact support](/service-mesh/v1.23/docs/getting-support) if you need to customize\nyour modernization or if you have questions about whether you are using unsupported\nfeatures.\n\nActive modernization\n--------------------\n\nDuring the modernization, in a safe and controlled way, the following changes take\nplace:\n\n- To enable health checking, the `snk` daemonset is created in the `kube-system` namespace of the cluster and a per-cluster a firewall rule is created.\n- To enable [network endpoint group (NEG)](/load-balancing/docs/negs) ingestion, the annotation `cloud.google.com/neg` is added to all Kubernetes services.\n- New Google Cloud resources such as [`Mesh`](/service-mesh/v1.23/docs/service-routing/service-routing-overview), [`Routes`](/service-mesh/v1.23/docs/service-routing/service-routing-overview), [backend\n services](/load-balancing/docs/backend-service), and [health\n checks](/load-balancing/docs/health-check-concepts) are created in the cluster.\n- Pods managed by Kubernetes deployments are restarted to reconnect to the Traffic Director control plane.\n\nSome of the new resources are quota-limited. You can\n[view quotas and request more if necessary](/load-balancing/docs/quotas).\n\nYou can track the progress of a fleet's modernization with the following\nGoogle Cloud CLI command, and looking in each member's `conditions`: \n\n```\ngcloud container fleet mesh describe --project=PROJECT_ID\n```\n\nWhen a cluster is being modernized you will see: \n\n```\nconditions:\n- code: MODERNIZATION_IN_PROGRESS\n details: The modernization for this cluster is in progress.\n documentationLink: \n severity: INFO\n```\n\nWhen the modernization is complete you will see: \n\n```\nconditions:\n- code: MODERNIZATION_COMPLETED\n details: The modernization for this cluster was completed.\n documentationLink: \n severity: INFO\n```\n\n\u003cbr /\u003e\n\nIf the modernization is cancelled you will see: \n\n```\nconditions:\n- code: MODERNIZATION_ABORTED\n details: The modernization for this cluster was aborted.\n documentationLink: \n severity: INFO\n```\n\n\u003cbr /\u003e"]]
