Opinie (Setting up a Private Kubernetes Cluster)
72046 opinii
Edjin Jerney P. · Sprawdzono 9 dni temu
Yamini N. · Sprawdzono 9 dni temu
Jan R. · Sprawdzono 9 dni temu
RAVIKUMAR M. · Sprawdzono 9 dni temu
Emerson S. · Sprawdzono 9 dni temu
Manish S. · Sprawdzono 9 dni temu
Anderson L. · Sprawdzono 9 dni temu
Gonzalo H. · Sprawdzono 9 dni temu
Rodrigo O. · Sprawdzono 9 dni temu
Uade I. · Sprawdzono 9 dni temu
Hoang T. · Sprawdzono 9 dni temu
Damodar K. · Sprawdzono 9 dni temu
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. · Sprawdzono 9 dni temu
Ashish J. · Sprawdzono 9 dni temu
Isuru L. · Sprawdzono 9 dni temu
Sankavi S. · Sprawdzono 9 dni temu
Sergio A. · Sprawdzono 10 dni temu
申 佐. · Sprawdzono 10 dni temu
sowmya p. · Sprawdzono 10 dni temu
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. · Sprawdzono 10 dni temu
Dmytro P. · Sprawdzono 10 dni temu
Sampath S. · Sprawdzono 10 dni temu
Thiago M. · Sprawdzono 10 dni temu
Fernando C. · Sprawdzono 10 dni temu
Jeffrey L. · Sprawdzono 10 dni temu
Nie gwarantujemy, że publikowane opinie pochodzą od konsumentów, którzy dane produkty kupili lub ich używali. Google nie weryfikuje opinii.