Stay organized with collectionsSave and categorize content based on your preferences.
Migrate from controlPlaneManagement to management
ThecontrolPlaneManagementsetting for managing your service mesh control plane is deprecated. If you were previously usingcontrolPlaneManagement, you must migrate to themanagementsetting.
To check if you're usingcontrolPlaneManagement, use the Feature State API:
gcloudcontainerfleetmeshdescribe
Any value forcontrolPlaneunder your membership spec indicates that you're usingcontrolPlaneManagementand need to migrate tomanagement.
Differences between the controlPlaneManagement and management settings
Themanagementsetting enables additional automatic behaviors, compared to thecontrolPlaneManagementsetting:
Both the management and controlPlaneManagement settings are enabled
If you're already using themanagementsetting, you might see theDEPRECATED_SPEC_CONTROL_PLANE_MANAGEMENT_SAFEcondition displayed through the Feature State API. This indicates that the deprecatedcontrolPlaneManagementsetting is still present in your configuration even though it's no longer being used.
To remove this deprecated setting and ensure a clean configuration, run:
[[["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-09-04 UTC."],[],[],null,["# Migrate from controlPlaneManagement to management\n=================================================\n\nThe `controlPlaneManagement` setting for managing your service mesh control plane is deprecated. If you were previously using `controlPlaneManagement`, you must migrate to the `management` setting.\n\nTo check if you're using `controlPlaneManagement`, use the Feature State API: \n\n gcloud container fleet mesh describe\n\nAny value for `controlPlane` under your membership spec indicates that you're using `controlPlaneManagement` and need to migrate to `management`.\n\nDifferences between the controlPlaneManagement and management settings\n----------------------------------------------------------------------\n\nThe `management` setting enables additional automatic behaviors, compared to the\n`controlPlaneManagement` setting:\n\n- `management` automatically enables [managed data plane](/service-mesh/docs/onboarding/provision-control-plane#managed-data-plane).\n- `management` automatically enables [multi-cluster endpoint discovery](/service-mesh/docs/operate-and-maintain/multi-cluster#configure_endpoint_discovery).\n\nMigration steps:\n----------------\n\nThere are two possible scenarios depending on your setup. We'll outline the migration steps for each scenario.\n\n### controlPlaneManagement is enabled and management is unset\n\nCondition `DEPRECATED_SPEC_CONTROL_PLANE_MANAGEMENT` will be displayed through Feature State API. To migrate to `management`:\n\n1. [Enable automatic management](/service-mesh/docs/onboarding/provision-control-plane#configure) for the cluster, optionally disabling some capabilities. Run:\n\n gcloud container fleet mesh update \\\n --management automatic \\\n --memberships \u003cvar translate=\"no\"\u003eMEMBERSHIP_NAME\u003c/var\u003e \\\n --project \u003cvar translate=\"no\"\u003eFLEET_PROJECT_ID\u003c/var\u003e \\\n --location \u003cvar translate=\"no\"\u003eMEMBERSHIP_LOCATION\u003c/var\u003e\n\n2. Ensure you have the chosen configuration for multi-cluster endpoint discovery.\n\n - If you have multiple clusters, ensure you [enable prerequisites for endpoint discovery](/service-mesh/docs/onboarding/provision-control-plane#configure_endpoint_discovery_only_for_multi-cluster_installations), including ensuring firewall rules.\n - Alternately, follow the Disable instructions at [configure endpoint discovery](/service-mesh/docs/operate-and-maintain/multi-cluster#configure_endpoint_discovery).\n3. Note that you have enabled the managed data plane.\n\n - Alternately, [disable data plane management](/service-mesh/docs/onboarding/provision-control-plane#disable_the_managed_data_plane_optional).\n4. Disable the no-longer-used controlPlaneManagement setting:\n\n gcloud container fleet mesh update \\\n --control-plane unspecified \\\n --memberships \u003cvar translate=\"no\"\u003eMEMBERSHIP_NAME\u003c/var\u003e \\\n --project \u003cvar translate=\"no\"\u003eFLEET_PROJECT_ID\u003c/var\u003e \\\n --location \u003cvar translate=\"no\"\u003eMEMBERSHIP_LOCATION\u003c/var\u003e\n\n### Both the management and controlPlaneManagement settings are enabled\n\nIf you're already using the `management` setting, you might see the `DEPRECATED_SPEC_CONTROL_PLANE_MANAGEMENT_SAFE` condition displayed through the Feature State API. This indicates that the deprecated `controlPlaneManagement` setting is still present in your configuration even though it's no longer being used.\n\nTo remove this deprecated setting and ensure a clean configuration, run: \n\n gcloud container fleet mesh update \\\n --control-plane unspecified \\\n --memberships \u003cvar translate=\"no\"\u003eMEMBERSHIP_NAME\u003c/var\u003e \\\n --project \u003cvar translate=\"no\"\u003eFLEET_PROJECT_ID\u003c/var\u003e \\\n --location \u003cvar translate=\"no\"\u003eMEMBERSHIP_LOCATION\u003c/var\u003e\n\nThis will have no effect on your mesh's behavior, since the management\nsetting already overrides the controlPlaneManagement setting."]]
