관리형 컨트롤 플레인에서 맞춤설정할 수 있는 IstioOperator를 직접 지원하지 않습니다. Cloud Service Mesh에서 관리형 컨트롤 플레인으로 마이그레이션하려면 IstioOperator에서 수동으로 변환해야 합니다. 이 도구는 프로세스를 자동화하여 불편함을 줄이는 데 도움이 됩니다.
마이그레이션 도구 정보
마이그레이션 도구는 제공된 IstioOperator 파일을 비파괴적으로 평가하여 다음을 수행합니다.
호환성 문제를 확인합니다.
호환되는 IstioOperator 구성을 관리형 컨트롤 플레인에서 지원하는 구성으로 변환하여 새 구성을 파일로 출력합니다.
관리형 컨트롤 플레인에 필요한 기본값과 충돌하는 구성 값에 대한 경고를 출력합니다.
생성된 파일을 사용하는 방법을 권장합니다.
이 도구는 클러스터 데이터 또는 구성을 검사하지 않으며 클러스터 구성을 변경하지 않습니다. 생성된 모든 파일을 별도로 적용해야 합니다.
마이그레이션 도구를 사용하기 전에 관리형 컨트롤 플레인 지원 기능의 제한사항을 확인하여 관리형 컨트롤 플레인에서 Cloud Service Mesh 설치를 지원하는지 확인합니다.
마이그레이션 도구 사용
마이그레이션 도구는 asmcli 스크립트의 일부로 제공됩니다. 이 도구를 사용하려면 스크립트를 다운로드해야 합니다.
나열된 파일, 특히 asm/*meshconfig.yaml 및 asm/gateways*가 도구에서 출력됩니다.
구성 경고를 조사합니다.
출력을 검토하고 마이그레이션에 필요한 조치를 따릅니다.
지원되지 않는 MeshConfig 필드
관리형 컨트롤 플레인에서 MeshConfig의 다음 필드를 재정의합니다.
trustDomain
trustDomainAliases
configSources
defaultConfig.proxyMetadata - 이 특정 필드는 재정의됩니다. 새 필드를 추가할 수 있습니다.
XDS_ROOT_CA
CA_ROOT_CA
OUTPUT_CERTS
XDS_AUTH_PROVIDER
PROXY_CONFIG_XDS_AGENT
defaultConfig.meshId
defaultConfig.discoveryAddress
출력 예
$ asmcli experimental mcp-migrate-check -f some-iop.yaml
asmcli: Downloading ASM..
Generating equivalent configuration for Anthos Service Mesh managed control plane...
Migrating MeshConfig settings...
✔ Wrote MeshConfig to asm-generated-configs/meshconfig.yaml.
Migrating gateway deployments...
Checking configuration compatibility...
! Found unsupported configurations:
Components.Base: not configurable in managed control plane
Components.Pilot: not configurable in managed control plane
Hub=gcr.io/gke-release/asm: not configurable in managed control plane
Tag=1.10.4-asm.6: not configurable in managed control plane
Actions required to migrate:
! Found potentially unsupported configurations; review warnings above before proceeding
- Found custom mesh configuration settings. To apply these settings to ASM managed
control plane, run: `kubectl apply -f 'asm-generated-configs/meshconfig.yaml'`
TIP: steps recommending `kubectl apply` to be run should be integrated into your
CI/CD pipeline, if applicable.
[[["이해하기 쉬움","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,["Migrate from IstioOperator\n| **Preview\n| --- Migration tool**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nManaged control plane doesn't directly support `IstioOperator` for\ncustomization. Migrating to managed control plane from Cloud Service Mesh requires\nmanually converting from an `IstioOperator`. This tool helps reduce the friction\nby automating that process.\n\nAbout the migration tool\n\nThe migration tool non-destructively evaluates the provided `IstioOperator` file\nto do the following:\n\n- Check for compatibility issues.\n- Convert compatible `IstioOperator` configurations to configuration supported by managed control plane, outputting the new configurations to files.\n- Output warnings about configuration values that would conflict with default values required by managed control plane.\n- Recommend how to use the generated files.\n\nThis tool does not examine cluster data or configurations nor does it make\nchanges to a cluster configuration. You must separately apply all generated\nfiles.\n\nBefore using the migration tool, check the limitations on\n[managed control plane supported features](/service-mesh/docs/supported-features-managed)\nto verify that managed control plane supports your installation of Cloud Service Mesh.\n\nUsing the migration tool **Warning:** GitOps tools (including Config Sync, Argo CD, Terraform, and Jenkins) may interfere with your Cloud Service Mesh installation, migration, or upgrade processes. For best results, disable your GitOps tools before you install, migrate, or upgrade Cloud Service Mesh.\n\nThe migration tool is available as part of the `asmcli` script. You must\n[download the script](/service-mesh/docs/unified-install/get-started#download_asmcli)\nto use this tool.\n\n1. Run the migration tool:\n\n ```\n asmcli experimental mcp-migrate-check -f path/to/istiooperator.yaml\n ```\n2. Note the listed files output by the tool, specifically `asm/*meshconfig.yaml`\n and `asm/gateways*`.\n\n3. Examine configuration warnings.\n\n4. Review the output and follow the actions required to migrate.\n\nUnsupported MeshConfig fields\n\nThe following fields on MeshConfig are overridden by managed control plane.\n| **Note:** This list of fields is subject to change.\n\n- `trustDomain`\n- `trustDomainAliases`\n- `configSources`\n- `defaultConfig.proxyMetadata` - These specific fields are overridden. You can add new fields:\n - `XDS_ROOT_CA`\n - `CA_ROOT_CA`\n - `OUTPUT_CERTS`\n - `XDS_AUTH_PROVIDER`\n - `PROXY_CONFIG_XDS_AGENT`\n- `defaultConfig.meshId`\n- `defaultConfig.discoveryAddress`\n\nExample output \n\n```sh\n$ asmcli experimental mcp-migrate-check -f some-iop.yaml\nasmcli: Downloading ASM..\nGenerating equivalent configuration for Anthos Service Mesh managed control plane...\n\nMigrating MeshConfig settings...\n✔ Wrote MeshConfig to asm-generated-configs/meshconfig.yaml.\n\nMigrating gateway deployments...\n\nChecking configuration compatibility...\n! Found unsupported configurations:\n Components.Base: not configurable in managed control plane\n Components.Pilot: not configurable in managed control plane\n Hub=gcr.io/gke-release/asm: not configurable in managed control plane\n Tag=1.10.4-asm.6: not configurable in managed control plane\n\nActions required to migrate:\n! Found potentially unsupported configurations; review warnings above before proceeding\n- Found custom mesh configuration settings. To apply these settings to ASM managed\n control plane, run: `kubectl apply -f 'asm-generated-configs/meshconfig.yaml'`\n\nTIP: steps recommending `kubectl apply` to be run should be integrated into your\n CI/CD pipeline, if applicable.\n```\n\nWhat's next\n\n- Learn more about [managed control plane supported features](/service-mesh/docs/supported-features-managed)"]]
