关于“探索如何讓 GKE 虛擬機器發揮最佳成本效益”的评价

Anderson B. · 评论over 3 years之前

Oleksii T. · 评论over 3 years之前

Rodrigo G. · 评论over 3 years之前

when connecting to pod 1 to send the traffic it is giving error kubectl exec -it pod-1 -- sh error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "c55de94bc76544700270c2ebc4fc84cb76ca68896e5ac6d7962a0fa3efff7014": OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown

Mayur G. · 评论over 3 years之前

Łukasz S. · 评论over 3 years之前

Rajat S. · 评论over 3 years之前

final submit doesnt work properly

Олексій О. · 评论over 3 years之前

Handhika Y. · 评论over 3 years之前

Eduardo N. · 评论over 3 years之前

Roland Aldrick John G. · 评论over 3 years之前

Viacheslav M. · 评论over 3 years之前

Ardhi H. · 评论over 3 years之前

Muhammad R. · 评论over 3 years之前

Someone who completed this lab, please guide me how you did that. I am not able to complete Task 3

Mohammad K. · 评论over 3 years之前

Ilyasa P. · 评论over 3 years之前

1: "kubectl exec -it pod-1 -- sh" does not work to pod-1 unless you change image from hello-app:2.0 to node-hello:1.0 2: within pod-1 ping to pod-2 does only work on standard port, not on 8080

Axel E. · 评论over 3 years之前

MARIO P. · 评论over 3 years之前

Антон Г. · 评论over 3 years之前

Richard W. · 评论over 3 years之前

MARIO P. · 评论over 3 years之前

good

Jagadish V. · 评论over 3 years之前

Satish V. · 评论over 3 years之前

This lab is not working properly. student_01_6d9af8e9e98a@cloudshell:~ (qwiklabs-gcp-00-d9686af4adac)$ kubectl get pod pod-1 pod-2 --output wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES pod-1 1/1 Running 0 79s 10.60.1.5 gke-regional-demo-default-pool-64c10e37-lhp9 <none> <none> pod-2 1/1 Running 0 56s 10.60.0.4 gke-regional-demo-default-pool-405c734f-3gq1 <none> <none> student_01_6d9af8e9e98a@cloudshell:~ (qwiklabs-gcp-00-d9686af4adac)$ kubectl exec -it pod-1 -- sh error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "8b1be01f8ee65ba1e67cf856cfa9bb420ec4e1c13d4d7645621d1ccfe03b662d": OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown student_01_6d9af8e9e98a@cloudshell:~ (qwiklabs-gcp-00-d9686af4adac)$

suresh r. · 评论over 3 years之前

Erick C. · 评论over 3 years之前