Explorer l'optimisation des coûts pour les machines virtuelles GKE avis

Raihan Akbar R. · Examiné il y a 2 mois

Rizky F. · Examiné il y a 2 mois

Dilpreet G. · Examiné il y a 2 mois

Sagar S. · Examiné il y a 2 mois

Tazkia D. · Examiné il y a 2 mois

Shubham G. · Examiné il y a 2 mois

Prakyat S. · Examiné il y a 2 mois

Devanshi L. · Examiné il y a 2 mois

Harsha V. · Examiné il y a 2 mois

Umang S. · Examiné il y a 2 mois

Satyam V. · Examiné il y a 2 mois

Sahil K. · Examiné il y a 2 mois

hasini C. · Examiné il y a 2 mois

NURUL ANNISA A. · Examiné il y a 2 mois

Krishna P. · Examiné il y a 2 mois

Moh Ubaidillah R. · Examiné il y a 2 mois

Hamsavalli S. · Examiné il y a 2 mois

fuck

Sajid A. · Examiné il y a 2 mois

Mahender R. · Examiné il y a 2 mois

E Sriram Prasad g. · Examiné il y a 2 mois

Piyush K. · Examiné il y a 2 mois

Kartik G. · Examiné il y a 2 mois

Good

GHELANI t. · Examiné il y a 2 mois

Taufik Nur T. · Examiné il y a 2 mois

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 2 mois