关于“Migrate to Containers: Qwik Start”的评价
4229 条评价
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前审核
我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。