Mempelajari Pengoptimalan Biaya untuk Virtual Machine GKE Ulasan

Raihan Akbar R. · Diulas 10 hari lalu

Rizky F. · Diulas 10 hari lalu

Dilpreet G. · Diulas 10 hari lalu

Sagar S. · Diulas 10 hari lalu

Tazkia D. · Diulas 10 hari lalu

Shubham G. · Diulas 10 hari lalu

Prakyat S. · Diulas 10 hari lalu

Devanshi L. · Diulas 10 hari lalu

Harsha V. · Diulas 10 hari lalu

Umang S. · Diulas 10 hari lalu

Satyam V. · Diulas 10 hari lalu

Sahil K. · Diulas 10 hari lalu

hasini C. · Diulas 10 hari lalu

NURUL ANNISA A. · Diulas 10 hari lalu

Krishna P. · Diulas 10 hari lalu

Moh Ubaidillah R. · Diulas 10 hari lalu

Hamsavalli S. · Diulas 10 hari lalu

fuck

Sajid A. · Diulas 10 hari lalu

Mahender R. · Diulas 10 hari lalu

Sriram prasad g. · Diulas 10 hari lalu

Piyush K. · Diulas 10 hari lalu

Kartik G. · Diulas 10 hari lalu

Good

GHELANI t. · Diulas 10 hari lalu

Taufik Nur T. · Diulas 10 hari lalu

The lab content is useful, but the validator and documentation appear to be outdated. I completed all required steps successfully: - Regional GKE cluster created - Pods deployed and traffic simulated - VPC Flow Logs enabled - Logging Sink created - BigQuery dataset and export completed - Flow logs available in BigQuery - Pods successfully moved to the same node However, Task 3 never passed. The validator kept showing: "Please run the desired query and check the frequent traffic between different zones." The lab documentation references: jsonPayload.dest_instance.zone jsonPayload.dest_instance.vm_name but the current VPC Flow Logs schema no longer contains the dest_instance field, causing the documented query to fail. I spent several hours troubleshooting and repeated the lab three times even though the infrastructure was configured correctly. Please update the lab instructions and validator to match the current VPC Flow Logs schema.

VIncentius I. · Diulas 10 hari lalu