Configurer un cluster Kubernetes privé avis
72046 avis
Edjin Jerney P. · Examiné il y a 9 jours
Yamini N. · Examiné il y a 9 jours
Jan R. · Examiné il y a 9 jours
RAVIKUMAR M. · Examiné il y a 9 jours
Emerson S. · Examiné il y a 9 jours
Manish S. · Examiné il y a 9 jours
Anderson L. · Examiné il y a 9 jours
Gonzalo H. · Examiné il y a 9 jours
Rodrigo O. · Examiné il y a 9 jours
Uade I. · Examiné il y a 9 jours
Hoang T. · Examiné il y a 9 jours
Damodar K. · Examiné il y a 9 jours
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. · Examiné il y a 9 jours
Ashish J. · Examiné il y a 9 jours
Isuru L. · Examiné il y a 9 jours
Sankavi S. · Examiné il y a 9 jours
Sergio A. · Examiné il y a 10 jours
申 佐. · Examiné il y a 10 jours
sowmya p. · Examiné il y a 10 jours
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. · Examiné il y a 10 jours
Dmytro P. · Examiné il y a 10 jours
Sampath S. · Examiné il y a 10 jours
Thiago M. · Examiné il y a 10 jours
Fernando C. · Examiné il y a 10 jours
Jeffrey L. · Examiné il y a 10 jours
Nous ne pouvons pas certifier que les avis publiés proviennent de consommateurs qui ont acheté ou utilisé les produits. Les avis ne sont pas vérifiés par Google.