Migrate to Containers: Qwik Start Reviews

Nobel T. · Reviewed over 5 years ago

Guillermo M. · Reviewed over 5 years ago

Marcio O. · Reviewed over 5 years ago

Florent C. · Reviewed over 5 years ago

Yusuke N. · Reviewed over 5 years ago

Eduardo A. · Reviewed over 5 years ago

Scott K. · Reviewed over 5 years ago

Sheng C. · Reviewed over 5 years ago

Jinwook B. · Reviewed over 5 years ago

reena v. · Reviewed over 5 years ago

Need an update of the instruction

Chris F. · Reviewed over 5 years ago

Fail to migrate

Chris F. · Reviewed over 5 years ago

Chris F. · Reviewed over 5 years ago

MOHIT A. · Reviewed over 5 years ago

I would love to see this lab expanded by adding disks attached to VM that also need migration.

Takito (Hiram) C. · Reviewed over 5 years ago

There are some errors in command parameters and object names

Janusz S. · Reviewed over 5 years ago

jaehong l. · Reviewed over 5 years ago

Done. 1) migctl source create ce migration-source --project $DEVSHELL_PROJECT_ID --zone us-central1-a > No need --zone us-central1-a 2) migctl migration get-artifacts my-migration > deployment_spec.yaml file will not have service (Type=LoadBalancer). So, I added "my-service" as LoadBalancer type to get 50 points. apiVersion: v1 kind: Service metadata: name: my-service spec: selector: app: source-vm ports: - protocol: TCP port: 80 targetPort: 80 type: LoadBalancer 3) As VM image name is "source-vm". So, development name in deployment_spec.yaml file is "source-vm". $ kubectl apply -f deployment_spec.yaml deployment.apps/source-vm created service/source-vm created service/my-service created

Surachart O. · Reviewed over 5 years ago

Ryan O. · Reviewed over 5 years ago

Mitsuhiko N. · Reviewed over 5 years ago

Luiz F. · Reviewed over 5 years ago

Chelsie D. · Reviewed over 5 years ago

Lab's a bit buggy. Had to attempt 6 times to finally complete. Stucks on migration part.

Mayank M. · Reviewed over 5 years ago

Fauzan Prabowo S. · Reviewed over 5 years ago

ryuya m. · Reviewed over 5 years ago