Hello Node Kubernetes Rezensionen

I wasn't able to see the changes made in the server.js file reflected in the deployed container.

Yashas R. · Vor fast 6 Jahre überprüft

Ashish J. · Vor fast 6 Jahre überprüft

Link to https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml not working

Priit U. · Vor fast 6 Jahre überprüft

Ashish N. · Vor fast 6 Jahre überprüft

graphical user interface documentation was out of date.

Frank H. · Vor fast 6 Jahre überprüft

Mihir B. · Vor fast 6 Jahre überprüft

秀之 生. · Vor fast 6 Jahre überprüft

Rahul H. · Vor fast 6 Jahre überprüft

Ezequiel S. · Vor fast 6 Jahre überprüft

The https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml link return 404. One option is the use the following link instead https://raw.githubusercontent.com/kubernetes/dashboard/master/aio/deploy/recommended/kubernetes-dashboard.yaml

Michael Sevelsted C. · Vor fast 6 Jahre überprüft

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. · Vor fast 6 Jahre überprüft

Karthik K. · Vor fast 6 Jahre überprüft

Dane H. · Vor fast 6 Jahre überprüft

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

Wes W. · Vor fast 6 Jahre überprüft

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. · Vor fast 6 Jahre überprüft

Alexander D. · Vor fast 6 Jahre überprüft

Boy L. · Vor fast 6 Jahre überprüft

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 . · Vor fast 6 Jahre überprüft

Mukesh G. · Vor fast 6 Jahre überprüft

将弘 菊. · Vor fast 6 Jahre überprüft

Louis B. · Vor fast 6 Jahre überprüft

Yi-Chan T. · Vor fast 6 Jahre überprüft

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. · Vor fast 6 Jahre überprüft

Rakesh G. · Vor fast 6 Jahre überprüft

Nicholas B. · Vor fast 6 Jahre überprüft