Mengelola Kubernetes di Google Cloud: Challenge Lab Ulasan

Sirikwan T. · Diulas 15 hari lalu

Thirupathi S. · Diulas 15 hari lalu

Hyung Sub S. · Diulas 15 hari lalu

TEERAPUT V. · Diulas 15 hari lalu

컨테이너 실행 시간이 소요되어서, 딜레이가 있습니다. 실습 시간이 부족한 것 같습니다.

Eunsoo G. · Diulas 15 hari lalu

Vijak K. · Diulas 15 hari lalu

Kamil Z. · Diulas 15 hari lalu

경 민. · Diulas 15 hari lalu

Yui K. · Diulas 15 hari lalu

10

Caleb Isaí H. · Diulas 15 hari lalu

BOPIT P. · Diulas 15 hari lalu

Task 4 (Logs-based Metric & Alerting): [Status: Grader Issue] Action Taken: Successfully created a Logs-based Metric named pod-image-errors and an Alert Policy named Pod Error Alert. Verification: Confirmed the query textPayload:"InvalidImageName" was capturing logs. The Monitoring dashboard showed the alert "Firing" with a count of 5-6 incidents, crossing the threshold of 0. Impediment: Despite the metric and alert working perfectly in the GCP Console, the Lab Grader consistently returned 0/10 or 5/10, likely due to a strict metadata requirement for the Resource Type (Global vs. Kubernetes Pod) that didn't align with the automated check. Task 6 (Deployment v2 & Service): [Status: Grader/Sync Issue] Action Taken: Built and pushed the v2 image to Artifact Registry. Updated the helloweb deployment to use the v2 tag. Created a LoadBalancer service helloweb-service-34zz on port 8080. Verification: Running kubectl get pods confirmed the v2 image was Running (1/1). Running kubectl get endpoints showed the service was correctly mapped to the Pod's internal IP (10.60.x.x:8080). Impediment: The "Check My Progress" button failed to turn green. This is often caused by a delay in the Load Balancer's external IP propagation or a mismatch in the Grader's expected Label Selectors, even when the Kubernetes resources are technically correct.

pholavit C. · Diulas 15 hari lalu

I was too stressed with the time limit. Hope it gets extended 30 more minutes

Sarvesh S. · Diulas 15 hari lalu

Mohan Kumar G. · Diulas 16 hari lalu

Alejandro V. · Diulas 16 hari lalu

Tejpal A. · Diulas 16 hari lalu

At the end of the lab, my GKE cluster entered provisioning status because us-central1-a likely ran out of resources. "Can't scale up due to the current unavailability of a Compute Engine resource, for example, GPUs or CPUs in the requested zone." I think you don't need to check the cluster status if all other checkpoints have been completed.

Nikita E. · Diulas 16 hari lalu

Patanin P. · Diulas 16 hari lalu

MUKUNDHAN C. · Diulas 16 hari lalu

Mohan Kumar G. · Diulas 16 hari lalu

Mohan Kumar G. · Diulas 16 hari lalu

Alejandro V. · Diulas 16 hari lalu

Panuts M. · Diulas 16 hari lalu

Mohan Kumar G. · Diulas 16 hari lalu

Mike T. · Diulas 16 hari lalu