Deploying GKE Autopilot Clusters from Cloud Shell Reviews

BHEEMANENI GNAPIKA CHOWDARY P. · Reviewed over 1 year ago

Claudiu B. · Reviewed over 1 year ago

Bangkit Anom Sedhayu C. · Reviewed over 1 year ago

BHEEMANENI GNAPIKA CHOWDARY P. · Reviewed over 1 year ago

Mochammad Fikri Chaerul Chalik Ramdhan C. · Reviewed over 1 year ago

HARSHITHA A N I. · Reviewed over 1 year ago

Archana B. · Reviewed over 1 year ago

USELESS

Alif Rendina P. · Reviewed over 1 year ago

Luthfi M. · Reviewed over 1 year ago

Daniel L. · Reviewed over 1 year ago

Muhammad Aqlifa Ikramulah C. · Reviewed over 1 year ago

Komang Bayu Lobi Hartawan C. · Reviewed over 1 year ago

Vaibhavi K. · Reviewed over 1 year ago

PALTHYA SONALIKA P. · Reviewed over 1 year ago

Y O. · Reviewed over 1 year ago

Patrick Ian L. · Reviewed over 1 year ago

Daniel Adrian B. · Reviewed over 1 year ago

Muhammad Ageng Zayem Wahid C. · Reviewed over 1 year ago

Andrii Z. · Reviewed over 1 year ago

Pratama Adri Wiguna C. · Reviewed over 1 year ago

Zidhan M. · Reviewed over 1 year ago

Abdelrahman K. · Reviewed over 1 year ago

At some point in the lab, this sample output is show: > gke_qwiklabs-gcp-03-71cc24186b4d_us-central1_autopilot-cluster-1 and then it says: > PROJECT_ID is your project ID. This information is the same as the information in the current-context property of the kubeconfig file. The mention to `PROJECT_ID` seems to expect the output to have been something like this instead: > gke_PROJECT_ID_us-central1_autopilot-cluster-1

Manuel R. · Reviewed over 1 year ago

Joshua P. · Reviewed over 1 year ago

Reah A. · Reviewed over 1 year ago