AHYBRID081 Configuring a multi-cluster mesh with Anthos Service Mesh のレビュー
読み込んでいます...
一致する結果は見つかりませんでした。

AHYBRID081 Configuring a multi-cluster mesh with Anthos Service Mesh のレビュー

3706 件のレビュー

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.

Mansuri Samir · 2年以上前にレビュー済み

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.

Mansuri Samir · 2年以上前にレビュー済み

No cluster resources!!! Cannot continue.

Jannasch Jens · 2年以上前にレビュー済み

Roy Ankur · 2年以上前にレビュー済み

John Daviding · 2年以上前にレビュー済み

The Kubernetes west can't run.

Madinaveitia Aitor · 2年以上前にレビュー済み

Gray Ashton · 2年以上前にレビュー済み

Gray Ashton · 2年以上前にレビュー済み

singh shikhar · 2年以上前にレビュー済み

Ciancio Stefano · 2年以上前にレビュー済み

cluster didn't run due to low resources allocation

Ciftci Umit · 2年以上前にレビュー済み

Sambyal Rahul · 2年以上前にレビュー済み

pathetic. Second cluster is not even deployed and ready at the beginning of lab EDITED: Works on retry on another cluster.

Bishnoi Sandeep · 2年以上前にレビュー済み

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.

Gledhill Paul · 2年以上前にレビュー済み

pathetic. Second cluster is not even deployed and ready at the beginning of lab

Bishnoi Sandeep · 2年以上前にレビュー済み

Completed

Pitchai Dhanasekar · 2年以上前にレビュー済み

Ciancio Stefano · 2年以上前にレビュー済み

Bintang Muhammad · 2年以上前にレビュー済み

Mishra Shikha · 2年以上前にレビュー済み

MONTI DORIANA · 2年以上前にレビュー済み

Syed Imran · 2年以上前にレビュー済み

Murialdo Franck · 2年以上前にレビュー済み

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

Rathi Ankit · 2年以上前にレビュー済み

Varela Ávila Claudia · 2年以上前にレビュー済み

I think the west was not configured correctly it is currently failing.

Ando Kelsey · 2年以上前にレビュー済み

公開されたレビューが、製品を購入または使用した人によるものであることは保証されません。Google はこれらのレビューの検証を行っていません。