Cloud Service Mesh dan Traffic Director kini bergabung menjadi Cloud Service Mesh. Untuk mengetahui informasi selengkapnya, lihat ringkasan Cloud Service Mesh.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Bermigrasi dari IstioOperator
Bidang kontrol terkelola tidak secara langsung mendukung IstioOperator untuk penyesuaian. Migrasi ke bidang kontrol terkelola dari Cloud Service Mesh memerlukan konversi manual dari IstioOperator. Alat ini membantu mengurangi hambatan
dengan mengotomatiskan proses tersebut.
Tentang alat migrasi
Alat migrasi mengevaluasi file IstioOperator yang disediakan secara non-destruktif
untuk melakukan hal berikut:
Periksa masalah kompatibilitas.
Mengonversi konfigurasi IstioOperator yang kompatibel menjadi konfigurasi yang didukung oleh bidang kontrol terkelola, dengan menghasilkan konfigurasi baru ke file.
Menampilkan peringatan tentang nilai konfigurasi yang akan berkonflik dengan nilai default yang diperlukan oleh managed control plane.
Merekomendasikan cara menggunakan file yang dihasilkan.
Alat ini tidak memeriksa data atau konfigurasi cluster, dan tidak membuat
perubahan pada konfigurasi cluster. Anda harus menerapkan semua file yang dihasilkan secara terpisah.
Sebelum menggunakan alat migrasi, periksa batasan pada
fitur yang didukung bidang kontrol terkelola
untuk memverifikasi bahwa bidang kontrol terkelola mendukung penginstalan Cloud Service Mesh Anda.
Menggunakan alat migrasi
Alat migrasi tersedia sebagai bagian dari skrip asmcli. Anda harus
mendownload skrip
untuk menggunakan alat ini.
Perhatikan file yang tercantum yang dihasilkan oleh alat, khususnya asm/*meshconfig.yaml
dan asm/gateways*.
Periksa peringatan konfigurasi.
Tinjau output dan ikuti tindakan yang diperlukan untuk melakukan migrasi.
Kolom MeshConfig yang tidak didukung
Kolom berikut di MeshConfig diganti oleh bidang kontrol terkelola.
trustDomain
trustDomainAliases
configSources
defaultConfig.proxyMetadata - Kolom spesifik ini diganti. Anda dapat
menambahkan kolom baru:
XDS_ROOT_CA
CA_ROOT_CA
OUTPUT_CERTS
XDS_AUTH_PROVIDER
PROXY_CONFIG_XDS_AGENT
defaultConfig.meshId
defaultConfig.discoveryAddress
Contoh output
$ 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.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 UTC."],[],[],null,["# Migrate from IstioOperator\n==========================\n\n|\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------------------------\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\n------------------------\n\n| **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-----------------------------\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\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\n- Learn more about [managed control plane supported features](/service-mesh/docs/supported-features-managed)"]]
