Hello Node Kubernetes avaliações

Michael S. · Revisado há over 7 years

intensive and interesting :)

Andrey G. · Revisado há over 7 years

Scott Y. · Revisado há over 7 years

c

See Chun C. · Revisado há over 7 years

Charles A. · Revisado há over 7 years

Rafael N. · Revisado há over 7 years

no se puede completar

Ignacio T. · Revisado há over 7 years

ちょっとつまづいてしまいました。

創一 有. · Revisado há over 7 years

Allen B. · Revisado há over 7 years

Sajan K. · Revisado há over 7 years

KENNEDY, M. · Revisado há over 7 years

Vincent F. · Revisado há over 7 years

Nirmalendu M. · Revisado há over 7 years

great

BISEN, D. · Revisado há over 7 years

The token I generated wasn't valid...

Chris H. · Revisado há over 7 years

satisfied

wendy o. · Revisado há over 7 years

Shabbir S. · Revisado há over 7 years

権治 中. · Revisado há over 7 years

Hussein S. · Revisado há over 7 years

Rejith B. · Revisado há over 7 years

joy n. · Revisado há over 7 years

Satisfied. Token to get into Kubernetes dashboard was not accepted.

Ronald P. · Revisado há over 7 years

Several steps when executed did not appear exactly as the lab said. "You should now be able to reach the service by pointing your browser to this address: http://<EXTERNAL_IP>:8080" I substitute the IP but it did not work. "This is the output you should see:" deployment "hello-node" scaled What I actually saw: deployment.extensions "hello-node" scaled "This is the output you should see:" deployment "hello-node" edited What I actually saw: deployment.extensions "hello-node" edited Expected: NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE hello-node 4 4 4 4 1h Actual: NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE hello-node 4 5 3 2 19m [This value is OK, but what about the others?] Finally, in the optional section, the Kubernetes Dashboard did not accept the token that was generated. I tried it several times.

Peter J. · Revisado há over 7 years

Fine

Michael D. · Revisado há over 7 years

Naveen Kumar E. · Revisado há over 7 years