Exploring Cost-optimization for GKE Virtual Machines avis

Raihan Akbar R. · Examiné il y a 10 jours

Rizky F. · Examiné il y a 10 jours

Dilpreet G. · Examiné il y a 10 jours

Sagar S. · Examiné il y a 10 jours

Tazkia D. · Examiné il y a 10 jours

Shubham G. · Examiné il y a 10 jours

Prakyat S. · Examiné il y a 10 jours

Devanshi L. · Examiné il y a 10 jours

Harsha V. · Examiné il y a 10 jours

Umang S. · Examiné il y a 10 jours

Satyam V. · Examiné il y a 10 jours

Sahil K. · Examiné il y a 10 jours

hasini C. · Examiné il y a 10 jours

NURUL ANNISA A. · Examiné il y a 10 jours

Krishna P. · Examiné il y a 10 jours

Moh Ubaidillah R. · Examiné il y a 10 jours

Hamsavalli S. · Examiné il y a 10 jours

fuck

Sajid A. · Examiné il y a 10 jours

Mahender R. · Examiné il y a 10 jours

Sriram prasad g. · Examiné il y a 10 jours

Piyush K. · Examiné il y a 10 jours

Kartik G. · Examiné il y a 10 jours

Good

GHELANI t. · Examiné il y a 10 jours

Taufik Nur T. · Examiné il y a 10 jours

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. · Examiné il y a 10 jours