[DEPRECATED] Getting Started with Google Kubernetes Engine - Windows Reviews
957 reviews
Juan Patricio C. · Reviewed over 3 years ago
Muhammad Y. · Reviewed over 3 years ago
1. Deprecated version of GKE in lab. 2. Timer is unfair! Downloading of image, making cluster and windows node taking too much time.
Ілля С. · Reviewed over 3 years ago
Anshari F. · Reviewed over 3 years ago
1. Deprecated version of GKE in lab. 2. Timer is unfair! Downloading of image, making cluster and windows node taking too much time.
Ілля С. · Reviewed over 3 years ago
i have to get help from chat due to this ERROR: (gcloud.container.clusters.create) ResponseError: code=400, message=Master version "1.22.11-gke.400" is unsupported. student_02_033b248b072c@cloudshell:~ (qwiklabs-gcp-01-546057211ec7)$ export CLUSTER_NAME=win-cluster export CLUSTER_VERSION=1.22.11-gke.400 gcloud container clusters create ${CLUSTER_NAME} \ --enable-ip-alias \ --num-nodes=2 \ --cluster-version=${CLUSTER_VERSION} Default change: During creation of nodepools or autoscaling configuration changes for cluster versions greater than 1.24.1-gke.800 a default location policy is applied. For Spot and PVM it defaults to ANY, and for all other VM kinds a BALANCED policy is used. To change the default values use the `--location-policy` flag. Note: The Pod address range limits the maximum size of the cluster. Please refer to https://cloud.google.com/kubernetes-engine/docs/how-to/flexible-pod-cidr to learn how to optimize IP address allocation....so the indications are not updated
Borja C. · Reviewed over 3 years ago
ERROR: (gcloud.container.clusters.create) ResponseError: code=400, message=Master version "1.22.11-gke.400" is unsupported. student_02_033b248b072c@cloudshell:~ (qwiklabs-gcp-01-546057211ec7)$ export CLUSTER_NAME=win-cluster export CLUSTER_VERSION=1.22.11-gke.400 gcloud container clusters create ${CLUSTER_NAME} \ --enable-ip-alias \ --num-nodes=2 \ --cluster-version=${CLUSTER_VERSION} Default change: During creation of nodepools or autoscaling configuration changes for cluster versions greater than 1.24.1-gke.800 a default location policy is applied. For Spot and PVM it defaults to ANY, and for all other VM kinds a BALANCED policy is used. To change the default values use the `--location-policy` flag. Note: The Pod address range limits the maximum size of the cluster. Please refer to https://cloud.google.com/kubernetes-engine/docs/how-to/flexible-pod-cidr to learn how to optimize IP address allocation.
Borja C. · Reviewed over 3 years ago
Marcos B. · Reviewed over 3 years ago
Katarzyna K. · Reviewed over 3 years ago
Alexander V. · Reviewed over 3 years ago
Anton Z. · Reviewed over 3 years ago
complicated lab
Antonio A. · Reviewed over 3 years ago
Евгений К. · Reviewed over 3 years ago
ERROR: (gcloud.container.clusters.create) ResponseError: code=400, message=Master version "1.22.11-gke.400" is unsupported. student_02_033b248b072c@cloudshell:~ (qwiklabs-gcp-01-546057211ec7)$ export CLUSTER_NAME=win-cluster export CLUSTER_VERSION=1.22.11-gke.400 gcloud container clusters create ${CLUSTER_NAME} \ --enable-ip-alias \ --num-nodes=2 \ --cluster-version=${CLUSTER_VERSION} Default change: During creation of nodepools or autoscaling configuration changes for cluster versions greater than 1.24.1-gke.800 a default location policy is applied. For Spot and PVM it defaults to ANY, and for all other VM kinds a BALANCED policy is used. To change the default values use the `--location-policy` flag. Note: The Pod address range limits the maximum size of the cluster. Please refer to https://cloud.google.com/kubernetes-engine/docs/how-to/flexible-pod-cidr to learn how to optimize IP address allocation.
Borja C. · Reviewed over 3 years ago
Dmytro G. · Reviewed over 3 years ago
Барабан С. · Reviewed over 3 years ago
Ramazan K. · Reviewed over 3 years ago
Leonardo L. · Reviewed over 3 years ago
Leonardo L. · Reviewed over 3 years ago
Put a tutorial so we can check de gke version when creating the cluster, it was deprecated when I tried the version in the example
Daniel M. · Reviewed over 3 years ago
Jonathan M. · Reviewed over 3 years ago
Leonardo L. · Reviewed over 3 years ago
Gabriel H. · Reviewed over 3 years ago
The lab is not able to recognize the built image on the windows machine. Apparently related to an error on defining the project configuration on the initialization script.
Andre Luiz P. · Reviewed over 3 years ago
The lab is not able to recognize the built image on the windows machine. Apparently related to an error on defining the project configuration on the initialization script.
Andre Luiz P. · Reviewed over 3 years ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.