Setting up a Private Kubernetes Cluster Reviews

Edjin Jerney P. · Reviewed 9 gün ago

Yamini N. · Reviewed 9 gün ago

Jan R. · Reviewed 9 gün ago

RAVIKUMAR M. · Reviewed 9 gün ago

Emerson S. · Reviewed 9 gün ago

Manish S. · Reviewed 9 gün ago

Anderson L. · Reviewed 9 gün ago

Gonzalo H. · Reviewed 9 gün ago

Rodrigo O. · Reviewed 9 gün ago

Uade I. · Reviewed 9 gün ago

Hoang T. · Reviewed 9 gün ago

Damodar K. · Reviewed 9 gün ago

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. · Reviewed 9 gün ago

Ashish J. · Reviewed 9 gün ago

Isuru L. · Reviewed 9 gün ago

Sankavi S. · Reviewed 9 gün ago

Sergio A. · Reviewed 10 gün ago

申 佐. · Reviewed 10 gün ago

sowmya p. · Reviewed 10 gün ago

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. · Reviewed 10 gün ago

Dmytro P. · Reviewed 10 gün ago

Sampath S. · Reviewed 10 gün ago

Thiago M. · Reviewed 10 gün ago

Fernando C. · Reviewed 10 gün ago

Jeffrey L. · Reviewed 10 gün ago