Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Arsitektur Migrate to Containers CLI
Halaman ini memberikan deskripsi umum tentang cara CLI Migrate to Containers mengubah aplikasi yang berada di instance virtual machine (VM) menjadi artefak yang dapat Anda gunakan untuk men-deploy komponen aplikasi dari lingkungan sumber ke cluster target di Google Kubernetes Engine (GKE) atau GKE Enterprise.
Komponen Migrate to Containers CLI
Modernisasi menggunakan Migrate to Containers CLI mencakup tiga langkah: Transformasi, Deployment workload, dan Pemeliharaan.
Transformasi -- CLI Migrate to Containers digunakan untuk mengubah komponen aplikasi berbasis VM menjadi komponen aplikasi berbasis container yang siap di-deploy. Proses ini mencakup lima fase:
Salin -- Menyalin sistem file mesin target
ke mesin lokal.
Analyze -- Menganalisis sistem file untuk membuat
rencana migrasi.
Edit -- Mengedit rencana untuk mengubah output
migrasi agar sesuai dengan kebutuhan Anda.
Generate -- Buat artefak seperti file Docker, konteks Docker, file deployment Kubernetes, dan konfigurasi Skaffold.
Memigrasikan data -- Menyalin file data ke dalam volume persisten. Tindakan ini bersifat opsional.
Deployment workload -- Anda dapat men-deploy workload container yang Dimigrasikan di cluster GKE atau GKE Enterprise mana pun yang memenuhi persyaratan minimum. Artefak migrasi dapat mencakup satu atau beberapa Dockerfile,
satu atau beberapa spesifikasi deployment Kubernetes, dan file konfigurasi Skaffold.
Pemeliharaan -- Setelah memigrasikan workload container, Anda biasanya
melakukan operasi pengoptimalan dan pemeliharaan. Konten workload yang diekstrak
dan Dockerfile yang dihasilkan dapat diintegrasikan dalam pipeline CI/CD
untuk pemeliharaan berbasis image yang efisien.
[[["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 to Containers CLI architecture\n======================================\n\nThis page provides a high-level description of how Migrate to Containers CLI\ntransforms your applications residing on virtual machine (VM) instances into\nartifacts that you can use to deploy your application components from the\nsource environment to a target cluster on [Google Kubernetes Engine (GKE)](/kubernetes-engine)\nor [GKE Enterprise](/anthos).\n\nMigrate to Containers CLI components\n------------------------------------\n\nModernization using Migrate to Containers CLI spans across three steps: Transformation,\nWorkload deployment, and Maintenance.\n\n1. **Transformation** -- Migrate to Containers CLI is used to transform a VM-based\n application component into a container-based application component ready to\n be deployed. This spans across five phases:\n\n 1. **Copy** -- Copy the file system of the target machine to the local machine.\n 2. **Analyze** -- Analyze the file system to create a migration plan.\n 3. **Edit** -- Edit the plan to modify the migration outputs to fit your needs.\n 4. **Generate** -- Generate artifacts such as Docker files, Docker contexts, Kubernetes deployment files and Skaffold configuration.\n 5. **Migrate data** -- Copy the data files into persistent volumes. This is optional.\n2. **Workload deployment** -- You can deploy Migrated container workloads on\n any GKE or GKE Enterprise cluster meeting the minimum\n requirements. The migration artifacts can include one or more Dockerfiles,\n one or more Kubernetes deployment specs, and a Skaffold configuration file.\n\n3. **Maintenance** -- After you migrate container workloads, you typically\n perform optimization and maintenance operations. The extracted workload\n content and the generated Dockerfile can be integrated in a CI/CD pipeline\n for efficient image-based maintenance.\n\nWhat's next\n-----------\n\n- Learn about [reviewing compatible OS, workloads, and Kubernetes versions](/migrate/containers/docs/m2c-cli/compatible-components).\n- Learn how to [discover, collect, and assess VMware VMs for migration](/migrate/containers/docs/mcdc-vmware-quickstart).\n- Learn how to [migrate a VM](/migrate/containers/docs/migrate-vm)."]]
