menu

Mengorkestrasi Cloud dengan Kubernetes

Go to Lab

15216 Reviews

Ivan A. · Reviewed 13 menit ago

Surya G. · Reviewed 15 menit ago

Patrick R. · Reviewed 23 menit ago

gcpuser c. · Reviewed 38 menit ago

Kamal S. · Reviewed 44 menit ago

惇 佐. · Reviewed sekitar 2 jam ago

Tatiana D. · Reviewed sekitar 3 jam ago

passwordの入力を求められるあたりがpasswordってどこにあったの?という感じになり無理やり突破しました。

Kaneda J. · Reviewed sekitar 3 jam ago

Marisol J. · Reviewed sekitar 5 jam ago

The last step of the lab didn't work. Doing a "kubectl describe services frontend" revealed that there were no endpoints: kubectl describe services frontend Name: frontend Namespace: default Labels: <none> Annotations: <none> Selector: app=frontend Type: LoadBalancer IP: 10.7.252.94 LoadBalancer Ingress: 34.68.49.126 Port: <unset> 443/TCP TargetPort: 443/TCP NodePort: <unset> 30413/TCP Endpoints: <none> Session Affinity: None External Traffic Policy: Cluster Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal EnsuringLoadBalancer 3m59s service-controller Ensuring load balancer Normal EnsuredLoadBalancer 3m18s service-controller Ensured load balancer Although, this might have been the problem: kubectl describe pods frontend Name: frontend-569465456f-b7642 Namespace: default Priority: 0 PriorityClassName: <none> Node: <none> Labels: app=frontend pod-template-hash=569465456f track=stable Annotations: kubernetes.io/limit-ranger: LimitRanger plugin set: cpu request for container nginx Status: Pending IP: Controlled By: ReplicaSet/frontend-569465456f Containers: nginx: Image: nginx:1.9.14 Port: <none> Host Port: <none> Requests: cpu: 100m Environment: <none> Mounts: /etc/nginx/conf.d from nginx-frontend-conf (rw) /etc/tls from tls-certs (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-phz7b (ro) Conditions: Type Status PodScheduled False Volumes: tls-certs: Type: Secret (a volume populated by a Secret) SecretName: tls-certs Optional: false nginx-frontend-conf: Type: ConfigMap (a volume populated by a ConfigMap) Name: nginx-frontend-conf Optional: false default-token-phz7b: Type: Secret (a volume populated by a Secret) SecretName: default-token-phz7b Optional: false QoS Class: Burstable Node-Selectors: <none> Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s node.kubernetes.io/unreachable:NoExecute for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 7s (x16 over 7m16s) default-scheduler 0/3 nodes are available: 3 Insufficient cpu. Note the "events" at the bottom. Having said all that, I still don't think this lab even came close to touching the surface of using kuberetes. I'm afraid the certification test will go into much more details.

Keith C. · Reviewed sekitar 5 jam ago

Travis J. · Reviewed sekitar 6 jam ago

Mohsin Ali K. · Reviewed sekitar 6 jam ago

Jaroslaw S. · Reviewed sekitar 7 jam ago

Florin U. · Reviewed sekitar 7 jam ago

Adam T. · Reviewed sekitar 8 jam ago

Han C. · Reviewed sekitar 9 jam ago

Emrah B. · Reviewed sekitar 9 jam ago

sam s. · Reviewed sekitar 9 jam ago

Shubham R. · Reviewed sekitar 10 jam ago

Cary B. · Reviewed sekitar 10 jam ago

Craig M. · Reviewed sekitar 11 jam ago

Jun P. · Reviewed sekitar 11 jam ago

Philippe B. · Reviewed sekitar 11 jam ago

Rii Y. · Reviewed sekitar 11 jam ago

Han C. · Reviewed sekitar 11 jam ago