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

Raihan Akbar R. · Revisado há 10 days

Rizky F. · Revisado há 10 days

Dilpreet G. · Revisado há 10 days

Sagar S. · Revisado há 10 days

Tazkia D. · Revisado há 10 days

Shubham G. · Revisado há 10 days

Prakyat S. · Revisado há 10 days

Devanshi L. · Revisado há 10 days

Harsha V. · Revisado há 10 days

Umang S. · Revisado há 10 days

Satyam V. · Revisado há 10 days

Sahil K. · Revisado há 10 days

hasini C. · Revisado há 10 days

NURUL ANNISA A. · Revisado há 10 days

Krishna P. · Revisado há 10 days

Moh Ubaidillah R. · Revisado há 10 days

Hamsavalli S. · Revisado há 10 days

fuck

Sajid A. · Revisado há 10 days

Mahender R. · Revisado há 10 days

Sriram prasad g. · Revisado há 10 days

Piyush K. · Revisado há 10 days

Kartik G. · Revisado há 10 days

Good

GHELANI t. · Revisado há 10 days

Taufik Nur T. · Revisado há 10 days

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á 10 days