Como explorar a otimização de custos para máquinas virtuais do GKE avaliações

Raihan Akbar R. · Revisado há 2 months

Rizky F. · Revisado há 2 months

Dilpreet G. · Revisado há 2 months

Sagar S. · Revisado há 2 months

Tazkia D. · Revisado há 2 months

Shubham G. · Revisado há 2 months

Prakyat S. · Revisado há 2 months

Devanshi L. · Revisado há 2 months

Harsha V. · Revisado há 2 months

Umang S. · Revisado há 2 months

Satyam V. · Revisado há 2 months

Sahil K. · Revisado há 2 months

hasini C. · Revisado há 2 months

NURUL ANNISA A. · Revisado há 2 months

Krishna P. · Revisado há 2 months

Moh Ubaidillah R. · Revisado há 2 months

Hamsavalli S. · Revisado há 2 months

fuck

Sajid A. · Revisado há 2 months

Mahender R. · Revisado há 2 months

E Sriram Prasad g. · Revisado há 2 months

Piyush K. · Revisado há 2 months

Kartik G. · Revisado há 2 months

Good

GHELANI t. · Revisado há 2 months

Taufik Nur T. · Revisado há 2 months

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. · Revisado há 2 months