Menyiapkan Cluster Kubernetes Pribadi Ulasan
72046 ulasan
Edjin Jerney P. · Diulas 9 hari lalu
Yamini N. · Diulas 9 hari lalu
Jan R. · Diulas 9 hari lalu
RAVIKUMAR M. · Diulas 9 hari lalu
Emerson S. · Diulas 9 hari lalu
Manish S. · Diulas 9 hari lalu
Anderson L. · Diulas 9 hari lalu
Gonzalo H. · Diulas 9 hari lalu
Rodrigo O. · Diulas 9 hari lalu
Uade I. · Diulas 9 hari lalu
Hoang T. · Diulas 9 hari lalu
Damodar K. · Diulas 9 hari lalu
Lab: GSP178 – Setting up a Private Kubernetes Cluster The lab instructs students to use zone us-west8-a (Task 1: gcloud config set compute/zone us-west8-a, export ZONE=us-west8-a), but this zone does not exist in Google Cloud. Running gcloud config set compute/zone us-west8-a itself warns "us-west8-a is not a valid zone." Creating the GKE cluster fails with PERMISSION_DENIED: Permission denied on 'locations/us-west8-a' (or it may not exist), and gcloud container get-server-config --zone=us-west8-a fails with reason LOCATION_POLICY_VIOLATED. I also checked the project's effective constraints/gcp.resourceLocations org policy, and it only whitelists us-west8, us-west8-a/b/c as zonal locations (alongside unrelated multi-region values like us, europe, global). Since us-west8 isn't a real region, there is no valid zone available to complete Task 2 or later tasks in this project (qwiklabs-gcp-03-18f9cab742bb). This looks like a provisioning bug where a placeholder region token failed to get substituted with a real region for this specific lab session/project. Could you please check the lab template's region-assignment logic?
Monty v. · Diulas 9 hari lalu
Ashish J. · Diulas 9 hari lalu
Isuru L. · Diulas 9 hari lalu
Sankavi S. · Diulas 9 hari lalu
Sergio A. · Diulas 10 hari lalu
申 佐. · Diulas 10 hari lalu
sowmya p. · Diulas 10 hari lalu
Lab: GSP178 – Setting up a Private Kubernetes Cluster The lab instructs students to use zone us-west8-a (Task 1: gcloud config set compute/zone us-west8-a, export ZONE=us-west8-a), but this zone does not exist in Google Cloud. Running gcloud config set compute/zone us-west8-a itself warns "us-west8-a is not a valid zone." Creating the GKE cluster fails with PERMISSION_DENIED: Permission denied on 'locations/us-west8-a' (or it may not exist), and gcloud container get-server-config --zone=us-west8-a fails with reason LOCATION_POLICY_VIOLATED. I also checked the project's effective constraints/gcp.resourceLocations org policy, and it only whitelists us-west8, us-west8-a/b/c as zonal locations (alongside unrelated multi-region values like us, europe, global). Since us-west8 isn't a real region, there is no valid zone available to complete Task 2 or later tasks in this project (qwiklabs-gcp-03-18f9cab742bb). This looks like a provisioning bug where a placeholder region token failed to get substituted with a real region for this specific lab session/project. Could you please check the lab template's region-assignment logic?
Monty v. · Diulas 10 hari lalu
Dmytro P. · Diulas 10 hari lalu
Sampath S. · Diulas 10 hari lalu
Thiago M. · Diulas 10 hari lalu
Fernando C. · Diulas 10 hari lalu
Jeffrey L. · Diulas 10 hari lalu
Kami tidak dapat memastikan bahwa ulasan yang dipublikasikan berasal dari konsumen yang telah membeli atau menggunakan produk terkait. Ulasan tidak diverifikasi oleh Google.