Hello Node Kubernetes avis

I had a couple of issues with this lab: Issue 1: when creating pods, I mistakenly created "hello-world" instead of "hello-node". when trying to validate my progress, it didn't work, so I checked and created a pod named "hello-node" and my progress was validated. the issue is that the last validation didn't go through even when Ii followed all the steps. in the end, I deleted the other service/pod "hello-word", and afterwards the progress validation worked. Issue 2: When creating the UI of Kubernetes (optional step at the end), instead of getting a UI, I got back JSON objects (the output of the API of the UI ?). these JSON objects contain a list of paths. Here is how it looks like: { "paths": [ "/apis", "/apis/", "/apis/apiextensions.k8s.io", "/apis/apiextensions.k8s.io/v1beta1", "/healthz", "/healthz/etcd", "/healthz/ping", "/healthz/poststarthook/generic-apiserver-start-informers", "/healthz/poststarthook/start-apiextensions-controllers", "/healthz/poststarthook/start-apiextensions-informers", "/metrics", "/openapi/v2", "/swagger-2.0.0.json", "/swagger-2.0.0.pb-v1", "/swagger-2.0.0.pb-v1.gz", "/swagger.json", "/swaggerapi", "/version" ] } I am not sure whether I made a mistake somewhere, or it is related to a new update (of Kubernetes or the UI of Kubernetes).

Iheb K. · Examiné il y a plus de 7 ans

Very poorly explained

Juan C. · Examiné il y a plus de 7 ans

Jai P. · Examiné il y a plus de 7 ans

Rafael L. · Examiné il y a plus de 7 ans

Wira R. · Examiné il y a plus de 7 ans

Padmakar K. · Examiné il y a plus de 7 ans

Rajeev R. · Examiné il y a plus de 7 ans

Sivakumar C. · Examiné il y a plus de 7 ans

Michael A. · Examiné il y a plus de 7 ans

Snehal J. · Examiné il y a plus de 7 ans

Very good

Jithesh Philip J. · Examiné il y a plus de 7 ans

AUXILIA BRIDGET M. · Examiné il y a plus de 7 ans

ANTHONY M. · Examiné il y a plus de 7 ans

Time was too short.

Sunil D. · Examiné il y a plus de 7 ans

Royce S. · Examiné il y a plus de 7 ans

Arpit J. · Examiné il y a plus de 7 ans

Ajay P. · Examiné il y a plus de 7 ans

용진 임. · Examiné il y a plus de 7 ans

Arulmurugan S. · Examiné il y a plus de 7 ans

Only had one minor problem... rather than creating my cluster in us-central1-a, I used us-east1-b since it was closer to me. None of the "checks" ran successfully, and I didn't understand until later in the lab that it REALLY wanted us-central1-a. Once I tore down the cluster and moved it to the correct region, it worked fine. You may want to add a comment about not changing the region.

Jeff W. · Examiné il y a plus de 7 ans

Karim S. · Examiné il y a plus de 7 ans

Very!

Kim Z. · Examiné il y a plus de 7 ans

Simon P. · Examiné il y a plus de 7 ans

I had to login in again after losing the connection and then I could not activate the cloud shell in GCP console.

Mark N. · Examiné il y a plus de 7 ans

Jon T. · Examiné il y a plus de 7 ans