Hello Node Kubernetes Reviews

I had some errors authenticating with the token into the dashboard, had to try a few times. Also it seems like something went wrong with my deployment, it says only some of my pods and replica sets are working, and I got this error: "Failed to pull image "gcr.io/qwiklabs-gcp-f1f5ff9b05481daf/hello-node:v2": rpc error: code = Unknown desc = Error response from daemon: manifest for gcr.io/qwiklabs-gcp-f1f5ff9b05481daf/hello-node:v2 not found"

Brendan W. · Reviewed almost 7 years ago

Stephan B. · Reviewed almost 7 years ago

Venkat V. · Reviewed almost 7 years ago

Victor Z. · Reviewed almost 7 years ago

Anthony R. · Reviewed almost 7 years ago

Pavlo S. · Reviewed almost 7 years ago

Sa M. · Reviewed almost 7 years ago

couldnt get the pushed docker image to execute

Arnstein V. · Reviewed almost 7 years ago

Elaine G. · Reviewed almost 7 years ago

Valeria I. · Reviewed almost 7 years ago

Amiri G. · Reviewed almost 7 years ago

Viacheslav P. · Reviewed almost 7 years ago

Good

Youdong K. · Reviewed almost 7 years ago

great

Martin M. · Reviewed almost 7 years ago

Tommy H. · Reviewed almost 7 years ago

羿賢 呂. · Reviewed almost 7 years ago

Ashley W. · Reviewed almost 7 years ago

Puneeth R. · Reviewed almost 7 years ago

ABHISHEK Y. · Reviewed almost 7 years ago

SIVARAMA PRASAD P. · Reviewed almost 7 years ago

Fermin B. · Reviewed almost 7 years ago

Shivam G. · Reviewed almost 7 years ago

Another fun Kubernetes lab :) There seems to be a bit of a mix up; in "Roll out an upgrade to your service", the instructions given are: docker build -t gcr.io/qwiklabs-gcp-d074f24e372a57fa/hello-node:v2 . docker push gcr.io/qwiklabs-gcp-d074f24e372a57fa/hello-node:v1 The push instruction seems to be incorrect; it will push v1 to the container registry, but not v2. This will cause rolling updates to fail when editing the deployment to look for image v2 instead of v1.

Ting C. · Reviewed almost 7 years ago

Mariusz A. · Reviewed almost 7 years ago

Ben W. · Reviewed almost 7 years ago