Como configurar um cluster particular do Kubernetes avaliações
72047 avaliações
Thamizhiniyan C. · Revisado há 9 days
Edjin Jerney P. · Revisado há 9 days
Yamini N. · Revisado há 9 days
Jan R. · Revisado há 9 days
RAVIKUMAR M. · Revisado há 9 days
Emerson S. · Revisado há 9 days
Manish S. · Revisado há 9 days
Anderson L. · Revisado há 9 days
Gonzalo H. · Revisado há 9 days
Rodrigo O. · Revisado há 9 days
Uade I. · Revisado há 9 days
Hoang T. · Revisado há 9 days
Damodar K. · Revisado há 9 days
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. · Revisado há 9 days
Ashish J. · Revisado há 9 days
Isuru L. · Revisado há 9 days
Sankavi S. · Revisado há 10 days
Sergio A. · Revisado há 10 days
申 佐. · Revisado há 10 days
sowmya p. · Revisado há 10 days
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. · Revisado há 10 days
Dmytro P. · Revisado há 10 days
Sampath S. · Revisado há 10 days
Thiago M. · Revisado há 10 days
Fernando C. · Revisado há 10 days
Não garantimos que as avaliações publicadas sejam de consumidores que compraram ou usaram os produtos. As avaliações não são verificadas pelo Google.