AHYBRID081 Configuring a multi-cluster mesh with Anthos Service Mesh Reviews
3706 reviews
Status: ERROR west Google Compute Engine: Not all instances running in IGM after 35m17.776107087s. Expected 2, running 0, transitioning 2. Current errors: [GCE_STOCKOUT]: Instance 'gke-west-default-pool-3288abf6-343w' creation failed: The zone 'projects/qwiklabs-gcp-01-003e495e23a1/zones/us-west1-b' does not have enough resources available to fulfill the request. Try a different zone, or try again later.; [GCE_STOCKOUT]: Instance 'gke-west-default-pool-3288abf6-m8b4' creation failed: The zone 'projects/qwiklabs-gcp-01-003e495e23a1/zones/us-west1-b' does not have enough resources available to fulfill the request. Try a different zone, or try again later.
Samir M. · Reviewed 2 yıldan fazla ago
Status: ERROR west Google Compute Engine: Not all instances running in IGM after 35m17.776107087s. Expected 2, running 0, transitioning 2. Current errors: [GCE_STOCKOUT]: Instance 'gke-west-default-pool-3288abf6-343w' creation failed: The zone 'projects/qwiklabs-gcp-01-003e495e23a1/zones/us-west1-b' does not have enough resources available to fulfill the request. Try a different zone, or try again later.; [GCE_STOCKOUT]: Instance 'gke-west-default-pool-3288abf6-m8b4' creation failed: The zone 'projects/qwiklabs-gcp-01-003e495e23a1/zones/us-west1-b' does not have enough resources available to fulfill the request. Try a different zone, or try again later.
Samir M. · Reviewed 2 yıldan fazla ago
No cluster resources!!! Cannot continue.
Jens J. · Reviewed 2 yıldan fazla ago
Ankur R. · Reviewed 2 yıldan fazla ago
Daviding J. · Reviewed 2 yıldan fazla ago
The Kubernetes west can't run.
Aitor M. · Reviewed 2 yıldan fazla ago
Ashton G. · Reviewed 2 yıldan fazla ago
Ashton G. · Reviewed 2 yıldan fazla ago
shikhar s. · Reviewed 2 yıldan fazla ago
Stefano C. · Reviewed 2 yıldan fazla ago
cluster didn't run due to low resources allocation
Umit C. · Reviewed 2 yıldan fazla ago
Rahul S. · Reviewed 2 yıldan fazla ago
pathetic. Second cluster is not even deployed and ready at the beginning of lab EDITED: Works on retry on another cluster.
Sandeep B. · Reviewed 2 yıldan fazla ago
The lab seems to be broken at present. On starting the lab and running the "gcloud container clusters list" command. The 'west' cluster shows up as having an error. I've tried restarting the lab 3 times, and it's the same issue each time.
Paul G. · Reviewed 2 yıldan fazla ago
pathetic. Second cluster is not even deployed and ready at the beginning of lab
Sandeep B. · Reviewed 2 yıldan fazla ago
Completed
Dhanasekar P. · Reviewed 2 yıldan fazla ago
Stefano C. · Reviewed 2 yıldan fazla ago
Muhammad B. · Reviewed 2 yıldan fazla ago
Shikha M. · Reviewed 2 yıldan fazla ago
DORIANA M. · Reviewed 2 yıldan fazla ago
Imran S. · Reviewed 2 yıldan fazla ago
Franck M. · Reviewed 2 yıldan fazla ago
There's something wrong with the lab. student_00_fb3aaec3052a@cloudshell:~ (qwiklabs-gcp-03-12405ff48257)$ # create the gateway namespace kubectl create namespace $GATEWAY_NAMESPACE # enable sidecar injection on the gateway namespace kubectl label ns $GATEWAY_NAMESPACE \ istio.io/rev=$(kubectl -n istio-system get pods -l app=istiod -o json | jq -r '.items[0].metadata.labels["istio.io/rev"]') \ --overwrite # Apply the configurations kubectl apply -n $GATEWAY_NAMESPACE \ -f $DIR_PATH/samples/gateways/istio-ingressgateway error: exactly one NAME is required, got 0 See 'kubectl create namespace -h' for help and examples E0310 14:10:33.262475 547 memcache.go:238] couldn't get current server API group list: Get "https://34.82.148.1/api?timeout=32s": dial tcp 34.82.148.1:443: i/o timeout E0310 14:11:03.264180 547 memcache.go:238] couldn't get current server API group list: Get "https://34.82.148.1/api?timeout=32s": dial tcp 34.82.148.1:443: i/o timeout E0310 14:11:33.265366 547 memcache.go:238] couldn't get current server API group list: Get "https://34.82.148.1/api?timeout=32s": dial tcp 34.82.148.1:443: i/o timeout E0310 14:12:03.266266 547 memcache.go:238] couldn't get current server API group list: Get "https://34.82.148.1/api?timeout=32s": dial tcp 34.82.148.1:443: i/o timeout E0310 14:12:33.268170 547 memcache.go:238] couldn't get current server API group list: Get "https://34.82.148.1/api?timeout=32s": dial tcp 34.82.148.1:443: i/o timeout Unable to connect to the server: dial tcp 34.82.148.1:443: i/o timeout E0310 14:13:03.371182 560 memcache.go:238] couldn't get current server API group list: Get "https://34.82.148.1/api?timeout=32s": dial tcp 34.82.148.1:443: i/o timeout E0310 14:13:33.371984 560 memcache.go:238] couldn't get current server API group list: Get "https://34.82.148.1/api?timeout=32s": dial tcp 34.82.148.1:443: i/o timeout F0310 14:13:48.443487 571 cred.go:123] print credential failed with error: Failed to retrieve access token:: failure while executing gcloud, with args [config config-helper --format=json]: exit status 1 E0310 14:13:48.444673 560 memcache.go:238] couldn't get current server API group list: Get "https://34.82.148.1/api?timeout=32s": getting credentials: exec: executable gke-gcloud-auth-plugin failed with exit code 1 F0310 14:14:03.498010 584 cred.go:123] print credential failed with error: Failed to retrieve access token:: failure while executing gcloud, with args [config config-helper --format=json]: exit status 1 E0310 14:14:03.499781 560 memcache.go:238] couldn't get current server API group list: Get "https://34.82.148.1/api?timeout=32s": getting credentials: exec: executable gke-gcloud-auth-plugin failed with exit code 1 F0310 14:14:18.580177 598 cred.go:123] print credential failed with error: Failed to retrieve access token:: failure while executing gcloud, with args [config config-helper --format=json]: exit status 1 E0310 14:14:18.581480 560 memcache.go:238] couldn't get current server API group list: Get "https://34.82.148.1/api?timeout=32s": getting credentials: exec: executable gke-gcloud-auth-plugin failed with exit code 1 Unable to connect to the server: getting credentials: exec: executable gke-gcloud-auth-plugin failed with exit code 1 error: Unexpected args: [/samples/gateways/istio-ingressgateway] See 'kubectl apply -h' for help and examples student_00_fb3aaec3052a@cloudshell:~ (qwiklabs-gcp-03-12405ff48257)$ student_00_fb3aaec3052a@cloudshell:~ (qwiklabs-gcp-03-12405ff48257)$ student_00_fb3aaec3052a@cloudshell:~ (qwiklabs-gcp-03-12405ff48257)$ student_00_fb3aaec3052a@cloudshell:~ (qwiklabs-gcp-03-12405ff48257)$ student_00_fb3aaec3052a@cloudshell:~ (qwiklabs-gcp-03-12405ff48257)$ student_00_fb3aaec3052a@cloudshell:~ (qwiklabs-gcp-03-12405ff48257)$ student_00_fb3aaec3052a@cloudshell:~ (qwiklabs-gcp-03-12405ff48257)$ student_00_fb3aaec3052a@cloudshell:~ (qwiklabs-gcp-03-12405ff48257)$ student_00_fb3aaec3052a@cloudshell:~ (qwiklabs-gcp-03-12405ff48257)$ kubectl apply -n $GATEWAY_NAMESPACE -f $DIR_PATH/samples/gateways/istio-ingressgateway error: Unexpected args: [/samples/gateways/istio-ingressgateway] See 'kubectl apply -h' for help and examples student_00_fb3aaec3052a@cloudshell:~ (qwiklabs-gcp-03-12405ff48257)$ # create the gateway namespace kubectl create namespace $GATEWAY_NAMESPACE # enable sidecar injection on the gateway namespace kubectl label ns $GATEWAY_NAMESPACE \ istio.io/rev=$(kubectl -n istio-system get pods -l app=istiod -o json | jq -r '.items[0].metadata.labels["istio.io/rev"]') \ --overwrite # Apply the configurations kubectl apply -n $GATEWAY_NAMESPACE \ -f $DIR_PATH/samples/gateways/istio-ingressgateway error: exactly one NAME is required, got 0 See 'kubectl create namespace -h' for help and examples E0310 14:15:16.914903 654 memcache.go:238] couldn't get current server API group list: Get "https://34.82.148.1/api?timeout=32s": dial tcp 34.82.148.1:443: i/o timeout E0310 14:15:46.915904 654 memcache.go:238] couldn't get current server API group list: Get "https://34.82.148.1/api?timeout=32s": dial tcp 34.82.148.1:443: i/o timeout E0310 14:16:16.916767 654 memcache.go:238] couldn't get current server API group list: Get "https://34.82.148.1/api?timeout=32s": dial tcp 34.82.148.1:443: i/o timeout
Ankit R. · Reviewed 2 yıldan fazla ago
Claudia V. · Reviewed 2 yıldan fazla ago
I think the west was not configured correctly it is currently failing.
Kelsey A. · Reviewed 2 yıldan fazla ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.