Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Migra e implementa aplicaciones en clústeres de GKE Autopilot
A fin de implementar las cargas de trabajo de contenedores migradas en clústeres de GKE Autopilot, usa el mismo procedimiento para migrar las cargas de trabajo que usas en la arquitectura existente.
Los únicos cambios son los siguientes:
Debes configurar v2kServiceManager como true en el plan de migración antes de generar los artefactos del contenedor.
Debes revisar el nuevo archivo services-config.yaml y realizar las modificaciones en los servicios de inicialización. Consulta Usa services-config.yaml.
Por ejemplo, en una migración llamada “my-migration”, haz lo siguiente:
migctl migration get my-migration
Edita el plan de migración descargado, my-migration.yaml, en un editor de texto.
Verifica el administrador de servicios mejorado de Linux. La marca v2kServiceManager se configura como true de forma predeterminada. Sin embargo, si Migrate to Containers detecta un servicio del sistema que no es compatible con el administrador de servicios, recibirás una alerta y la marca v2kServiceManager se establecerá en false.
Cuando la marca es false, la migración usará un entorno de ejecución heredado que admita el servicio.
La siguiente alerta se proporciona junto con el servicio no compatible:
Service is not supported by v2k service manager, therefore legacy runtime
will be used instead of v2k service manager, and migrated workload would
not fit running on Autopilot clusters of Cloudrun.
Cuando se encuentra un servicio no compatible, también puedes configurar de forma manual la marca como true.
En esta instancia, puedes optar por mantener el servicio no compatible en la imagen generada en la que no se ejecuta o puedes excluir el servicio si lo quitas del plan de migración.
Para habilitar el administrador de servicios nuevo, restablece la marca a true:
Edita el archivo services-config.yaml nuevo para configurar las propiedades de inicialización del contenedor. Guarda el archivo y vuelve a compilar tu imagen de contenedor para aplicar los cambios.
Ejemplo: Implementa el contenedor de la guía de inicio rápido en un clúster de Autopilot
Usa la guía de guía de inicio rápido actual para migrar un contenedor que contiene un servidor web simple y, luego, implementarlo en un clúster de Autopilot. Los únicos cambios que debes realizar en el proceso de inicio rápido son los siguientes:
En el paso 3 de Migra la VM, en el que revisas el plan de migración, configura v2kServiceManager como true en el plan de migración y, luego, guarda el plan:
Si usas archivos CRD para controlar la migración, edita la CRD de AppXGenerateArtifactsFlow a fin de establecer v2kServiceManager en true. Consulta Personaliza un plan de migración a fin de obtener más información sobre el uso de archivos CRD para controlar la migración.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[],[],null,["# Migrate and deploy applications to GKE Autopilot clusters\n=========================================================\n\nTo deploy your migrated container workloads to GKE Autopilot clusters,\nyou use the same procedure to migrate your workloads as you use for the existing architecture.\nThe only changes are that:\n\n- You have to set `v2kServiceManager` to `true` in the migration plan\n before you generate the container artifacts.\n\n- You have to review the new `services-config.yaml` file and make any edits to the\n initialization services. See [Using services-config.yaml](/migrate/containers/docs/services-config).\n\nTo perform a migration:\n\n1. [Install Migrate to Containers version 1.15.0](/migrate/containers/docs/install-overview).\n\n2. [Add a migration source](/migrate/containers/docs/adding-a-migration-source) and [create a migration](/migrate/containers/docs/creating-a-migration)\n as you do today with the existing runtime.\n\n3. [Customize your migration plan](/migrate/containers/docs/customizing-a-migration-plan) as necessary.\n\n | **Note:** Prior to Migrate to Containers 1.10, use of the enhanced Linux service manager was disabled by default. If you are using Migrate to Containers 1.9 or older, you should have `v2kServiceManager` set to `true` in your migration plan (`my-migration.yaml`). If the enhanced Linux service manager is disabled for you, check your `services.yaml` file for comments about services that may not work with your new runtime. If you would like to include any of the disabled services, contact your support channel.\n 1. Download the migration plan. The migration plan is represented by\n [AppXGenerateArtifactsFlow](https://github.com/GoogleCloudPlatform/migrate-to-containers/blob/main/references/crds/m2c-crds.md#appxgenerateartifactsflow).\n\n For example, for a migration named \"my-migration\": \n\n ```\n migctl migration get my-migration\n ```\n 2. Open the downloaded migration plan, `my-migration.yaml`, in a text editor.\n\n 3. Verify the enhanced Linux service manager. The `v2kServiceManager` flag is\n set to `true` by default. However, if Migrate to Containers\n detects a system service that is not supported by the service\n manager, you will be alerted and the `v2kServiceManager` flag will be set to `false`.\n When the flag is `false` the migration will use a legacy runtime which supports your\n service.\n\n The following alert is provided alongside the unsupported service: \n\n ```\n Service is not supported by v2k service manager, therefore legacy runtime\n will be used instead of v2k service manager, and migrated workload would\n not fit running on Autopilot clusters of Cloudrun.\n ```\n\n When an unsupported service is found, you can also choose to manually set the flag to `true`.\n In this instance, you can either choose to keep the unsupported service on the generated image\n where it may not run or you can exclude the service by removing it from the migration plan.\n\n To enable the new service manager, reset the flag to `true`: \n\n ```yaml\n v2kServiceManager: true\n ```\n 4. Perform any other customizations necessary for your migration as described\n in [Customize the migration plan](/migrate/containers/docs/customizing-a-migration-plan).\n\n 5. When your edits are complete, save the edited file.\n\n 6. Upload the edited migration plan:\n\n ```\n migctl migration update my-migration --main-config my-migration.yaml\n ```\n4. [Generate](/migrate/containers/docs/executing-a-migration) and [review the migration artifacts](/migrate/containers/docs/review-deployment-files)\n as you do today with the existing runtime.\n\n5. Edit the new `services-config.yaml` file to configure the initialization properties\n of the container. Save the file and rebuild your container image to apply the changes.\n\n See [Using services-config.yaml](/migrate/containers/docs/services-config) for more.\n6. [Deploy the container to a GKE Autopilot cluster](/migrate/containers/docs/deploying-to-target-cluster)\n using `kubectl`:\n\n ```\n kubectl apply -f deployment_spec.yaml\n ```\n\n### Example: Deploying the Quickstart container on an Autopilot cluster\n\nUse the current [Quickstart](/migrate/containers/docs/quickstart) guide to migrate a container containing\na simple web server and then deploy it on an Autopilot cluster. The only changes\nthat you have to make to the Quickstart process are:\n\n1. In Step 3 of [Migrating the VM](/migrate/containers/docs/quickstart#migrating_the_vm), where you review\n the migration plan, set `v2kServiceManager` to `true` in the migration plan\n and then save the plan:\n\n ```yaml\n \n v2kServiceManager: true\n ```\n2. In the [Deploying the migrated workload](/migrate/containers/docs/quickstart#deploying_the_migrated_workload) section,\n create and connect to a GKE Autopilot cluster before you deploy the container:\n\n 1. Create a GKE Autopilot cluster:\n\n ```\n gcloud container clusters create-auto \"CLUSTER_NAME\"\n --project \"PROJECT_NAME\" --region \"REGION\" --release-channel \"regular\"\n --subnetwork \"projects/PROJECT_NAME/regions/us-central1/subnetworks/default\"\n ```\n 2. Connect to the cluster:\n\n ```\n gcloud container clusters get-credentials CLUSTER_NAME \n --zone REGION --project PROJECT_NAME \n ```\n 3. Deploy the container as described in the\n [Deploying the migrated workload](/migrate/containers/docs/quickstart#deploying_the_migrated_workload) section.\n\n### Changes to the AppXGenerateArtifactsFlow CRD\n\nIf you are using CRD files to control your migration, edit the [AppXGenerateArtifactsFlow](https://github.com/GoogleCloudPlatform/migrate-to-containers/blob/main/references/crds/m2c-crds.md#appxgenerateartifactsflow) CRD\nto set `v2kServiceManager` to `true`. See [Customizing a migration plan](/migrate/containers/docs/customizing-a-migration-plan#crd)\nfor more on using CRD files to control migration.\n\nWhat's next\n-----------\n\n- Learn how to [deploy containers to Cloud Run](/migrate/containers/docs/deploy-run)."]]