Hello Node Kubernetes avaliações

The instruction for creating the dashboard service is incorrect, the new instruction should be: kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v1.10.1/src/deploy/recommended/kubernetes-dashboard.yaml

David S. · Revisado há almost 7 years

Karthik K. · Revisado há almost 7 years

Dane H. · Revisado há almost 7 years

https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml <-- url reference sin lab as optional is broken.

Wes W. · Revisado há almost 7 years

I would've liked more time to review this very content-heavy lab. I felt very rushed and sped through the lab because I did not want to waste 7 credits.

Lindsey F. · Revisado há almost 7 years

Alexander D. · Revisado há almost 7 years

Boy L. · Revisado há almost 7 years

consegui fazer todas etapas, porém o painel gráfico do Kubernetes (parte opcional) não apareceu a parte de visualização gráfica no browser para colocar o token, apenas isso apareceu como resposta a URL: https://8081-dot-5241713-dot-devshell.appspot.com/ui: { "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" ] } -------------- :/

Polyana Pimenta . · Revisado há almost 7 years

Mukesh G. · Revisado há almost 7 years

将弘 菊. · Revisado há almost 7 years

Louis B. · Revisado há almost 7 years

Yi-Chan T. · Revisado há almost 7 years

I didn't understand many of the commands, but followed along in a monkey-see, monkey-do sort of way. There was a problem which meant the deployed thing (pod/app/cluster/deployment—who knows?) didn't work: CrashLoopBackOff, so most of the executed shell commands which I did afterwards produced unexpected results. Why is it kubectl get deployments, kubectl get pods, kubectl get services and not kubectl GET logs? Sample shell outputs: hello-node-65f987b6c8-65qxw 0/1 CrashLoopBackOff 6 7m google1882610_student@cloudshell:~ (qwiklabs-gcp-c68c7881eb5d84f8)$ kubectl get logs google1882610_student@cloudshell error: the server doesn't have a resource type "logs" google1882610_student@cloudshell:~ (qwiklabs-gcp-c68c7881eb5d84f8)$ kubectl logs google1882610_student@cloudshell Error from server (NotFound): pods "google1882610_student@cloudshell" not found google1882610_student@cloudshell:~ (qwiklabs-gcp-c68c7881eb5d84f8)$ kubectl logs hello-node-65g987b6c8-65qxw Error from server (NotFound): pods "hello-node-65g987b6c8-65qxw" not found google1882610_student@cloudshell:~ (qwiklabs-gcp-c68c7881eb5d84f8)$ kubectl logs hello-node-65f987b6c8-65qxw container_linux.go:247: starting container process caused "exec: \"kubectl\": executable file not found in $PATH" google1882610_student@cloudshell:~ (qwiklabs-gcp-c68c7881eb5d84f8)$ google1882610_student@cloudshell:~ (qwiklabs-gcp-c68c7881eb5d84f8)$ kubectl get services NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE hello-node LoadBalancer 10.31.252.0 35.232.242.169 8080:32328/TCP 54s kubernetes ClusterIP 10.31.240.1 <none> 443/TCP 16m This page isn’t working 35.232.242.169 didn’t send any data. ERR_EMPTY_RESPONSE kubectl scale deployment hello-node --replicas=4 google1882610_student@cloudshell:~ (qwiklabs-gcp-c68c7881eb5d84f8)$ kubectl get pods NAME READY STATUS RESTARTS AGE hello-node-65f987b6c8-65qxw 0/1 CrashLoopBackOff 8 19m hello-node-65f987b6c8-7pxjc 0/1 CrashLoopBackOff 4 2m hello-node-65f987b6c8-g72jf 0/1 CrashLoopBackOff 4 2m hello-node-65f987b6c8-rnbxd 0/1 CrashLoopBackOff 4 2m google1882610_student@cloudshell:~ (qwiklabs-gcp-c68c7881eb5d84f8)$ kubectl get deployments NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE hello-node 4 5 2 0 28m

Gary M. · Revisado há almost 7 years

Rakesh G. · Revisado há almost 7 years

Nicholas B. · Revisado há almost 7 years

Yi-Chan T. · Revisado há almost 7 years

Shivam S. · Revisado há almost 7 years

Great intro, I learned a lot!

Matthew M. · Revisado há almost 7 years

There are several places that need to be updated. Here is just one example of unexpected output. google1877689_student@cloudshell:~ (qwiklabs-gcp-d1de7b2c08ed561a)$ gcloud container clusters create hello-world --num-nodes 2 --machine-type n1-standard-1 --zone us-central1-a WARNING: Starting in 1.12, new clusters will have basic authentication disabled by default. Basic authentication can be enabled (or disabled) manually using the `--[no-]enable-basic-auth` flag. WARNING: Starting in 1.12, new clusters will not have a client certificate issued. You can manually enable (or disable) the issuance of the client certificate using the `--[no-]issue-client-certificate` flag. WARNING: Currently VPC-native is not the default mode during cluster creation. In the future, this will become the default mode and can be disabled using `--no-enable-ip-alias` flag. Use `--[no-]enable-ip-alias` flag to suppress this warning. WARNING: Starting in 1.12, default node pools in new clusters will have their legacy Compute Engine instance metadata endpoints disabled by default. To create a cluster with legacy instance metadata endpoints disabled in the default node pool, run `clusters create` with the flag `--metadata disable-legacy-endpoints=true`. This will enable the autorepair feature for nodes. Please see https://cloud.google.com/kubernetes-engine/docs/node-auto-repair for more information on node autorepairs. WARNING: Starting in Kubernetes v1.10, new clusters will no longer get compute-rw and storage-ro scopes added to what is specified in --scopes (though the latter will remain included in the default --scopes). To use these scopes, add them explicitly to --scopes. To use the new behavior, set container/new_scopes_behavior property (gcloud config set container/new_scopes_behavior true). Creating cluster hello-world in us-central1-a...done.

Kristian J. · Revisado há almost 7 years

Adarsh B. · Revisado há almost 7 years

Miriam M. · Revisado há almost 7 years

good but the link for the dashboard is outdated

Angel V. · Revisado há almost 7 years

The additional optional section is incorrect. The commands did not work and I was not able to use the Dash Board. Please make necessary corrections.

Ramesh M. · Revisado há almost 7 years

Daniel D. · Revisado há almost 7 years

Stanislav S. · Revisado há almost 7 years