Opinie (Hello Node Kubernetes)

Mukhesh Babu Y. · Sprawdzono ponad 2 lata temu

MANIKANDAN C. · Sprawdzono ponad 2 lata temu

this time it worked without issues on creating the cluster for task 3

Christopher J. · Sprawdzono ponad 2 lata temu

Cluster creation failed

Carlos Daniel O. · Sprawdzono ponad 2 lata temu

Will have to take this again - Task 3, creation of cluster ran for +30 minutes (stuck at 64% for 20 minutes and then got to 67%). Received this error in closing seconds of lab duration: Google Compute Engine: Not all instances running in IGM after 35m21.482936924s. Expected 2, running 0, transitioning 2. Current errors: [GCE_STOCKOUT]: Instance 'gke-hello-world-default-pool-2e12fe49-wwhl' creation failed: The zone 'projects/qwiklabs-gcp-04-f0735aaf2b24/zones/us-central1-a' does not have enough resources available to fulfill the request. Try a different zone, or try again later.; [GCE_STOCKOUT]: Instance 'gke-hello-world-default-pool-2e12fe49-xsxg' creation failed: The zone 'projects/qwiklabs-gcp-04-f0735aaf2b24/zones/us-central1-a' does not have enough resources available to fulfill the request. Try a different zone, or try again later. This is very disappointing... I would hope that no credits are used by my org for this failed attempt or quota attempts are added to my quota attempt. Would prefer to give 0 stars.

Christopher J. · Sprawdzono ponad 2 lata temu

(三浦尊臣) m. · Sprawdzono ponad 2 lata temu

Cluster creation is taking more time than expected, Task 3 should be move to Task 1 as this takes longer times.

Nicolas P. · Sprawdzono ponad 2 lata temu

no muy poco tiempo, taller con algunos procesos fallidos e imcompleto.

Fernando H. · Sprawdzono ponad 2 lata temu

error al crear el closuter

Leonidas A. · Sprawdzono ponad 2 lata temu

Federico A. · Sprawdzono ponad 2 lata temu

good

Vivek P. · Sprawdzono ponad 2 lata temu

Ivan E. · Sprawdzono ponad 2 lata temu

VAIBHAV S. · Sprawdzono ponad 2 lata temu

Sumukha B. · Sprawdzono ponad 2 lata temu

Kunjan R. · Sprawdzono ponad 2 lata temu

Deebika V. · Sprawdzono ponad 2 lata temu

Victor T. · Sprawdzono ponad 2 lata temu

Nice Lab

Hardik P. · Sprawdzono ponad 2 lata temu

Abhidnya K. · Sprawdzono ponad 2 lata temu

to worst , due to below error i am not able to complete this lab. student_01_9395be89549b@cloudshell:~ (qwiklabs-gcp-02-e06c9ddd0206)$ kubectl get deployments E0922 22:06:06.032390 1098 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused E0922 22:06:06.033606 1098 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused E0922 22:06:06.034265 1098 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused E0922 22:06:06.035808 1098 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused E0922 22:06:06.037149 1098 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused The connection to the server localhost:8080 was refused - did you specify the right host or port? student_01_9395be89549b@cloudshell:~ (qwiklabs-gcp-02-e06c9ddd0206)$

427704 4. · Sprawdzono ponad 2 lata temu

Martin K. · Sprawdzono ponad 2 lata temu

Vova H. · Sprawdzono ponad 2 lata temu

Andrii T. · Sprawdzono ponad 2 lata temu

Iteye O. · Sprawdzono ponad 2 lata temu

Gabriele R. · Sprawdzono ponad 2 lata temu