关于“Migrate to Containers: Qwik Start”的评价

Guillermo M. · 评论over 4 years之前

Marcio O. · 评论over 4 years之前

Florent C. · 评论over 4 years之前

Yusuke N. · 评论over 4 years之前

Eduardo A. · 评论over 4 years之前

Scott K. · 评论over 4 years之前

Sheng C. · 评论over 4 years之前

Jinwook B. · 评论over 4 years之前

reena v. · 评论over 4 years之前

Need an update of the instruction

Chris F. · 评论over 4 years之前

Fail to migrate

Chris F. · 评论over 4 years之前

Chris F. · 评论over 4 years之前

MOHIT A. · 评论over 4 years之前

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

Takito (Hiram) C. · 评论over 4 years之前

There are some errors in command parameters and object names

Janusz S. · 评论over 4 years之前

jaehong l. · 评论over 4 years之前

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. · 评论over 4 years之前

Ryan O. · 评论over 4 years之前

Mitsuhiko N. · 评论over 4 years之前

Luiz F. · 评论over 4 years之前

Chelsie D. · 评论over 4 years之前

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

Mayank M. · 评论over 4 years之前

Fauzan Prabowo S. · 评论over 4 years之前

ryuya m. · 评论over 4 years之前

Bandita12 B. · 评论over 4 years之前