Opinie (AHYBRID071 Configuring Clusters with Anthos Config Management)

only 1 gke cluster was pre-created! Aborting!

Samir M. · Sprawdzono ponad 2 lata temu

shikhar s. · Sprawdzono ponad 2 lata temu

Task 1, Step 3 is not working

Umit C. · Sprawdzono ponad 2 lata temu

Its not possible to pass the Task1 in point 3.Logs of the session fot more information: apiVersion: v1 Welcome to Cloud Shell! Type "help" to get started. Your Cloud Platform project in this session is set to qwiklabs-gcp-01-8448f2216078. Use “gcloud config set project [PROJECT_ID]” to change to a different project.student_00_79dcf3951326@cloudshell:~ (qwiklabs-gcp-01-8448f2216078)$ export PROJECT_ID=$(gcloud config get-value project)export SHELL_IP=$(curl -s api.ipify.org)export KUBECONFIG=~/.kube/configexport PROJECT_NUMBER=$(gcloud projects describe ${PROJECT_ID} \ --format="value(projectNumber)")gcloud compute firewall-rules create shell-to-onprem \ --network=onprem-k8s-local \ --allow tcp \ --source-ranges $SHELL_IP gsutil cp gs://$PROJECT_ID-kops-onprem/config \ ~/.kube/config Your active configuration is: [cloudshell-27058]Creating firewall...failed.ERROR: (gcloud.compute.firewall-rules.create) Could not fetch resource: - The resource 'projects/qwiklabs-gcp-01-8448f2216078/global/firewalls/shell-to-onprem' already exists Copying gs://qwiklabs-gcp-01-8448f2216078-kops-onprem/config.../ [1 files][ 8.2 KiB/ 8.2 KiB] Operation completed over 1 objects/8.2 KiB. student_00_79dcf3951326@cloudshell:~ (qwiklabs-gcp-01-8448f2216078)$ cat $SHELL_IP cat: 34.140.40.236: No such file or directory student_00_79dcf3951326@cloudshell:~ (qwiklabs-gcp-01-8448f2216078)$ echo $SHELL_IP 34.140.40.236 student_00_79dcf3951326@cloudshell:~ (qwiklabs-gcp-01-8448f2216078)$ gsutil cp gs://$PROJECT_ID-kops-onprem/config \ ~/.kube/config Copying gs://qwiklabs-gcp-01-8448f2216078-kops-onprem/config... / [1 files][ 8.2 KiB/ 8.2 KiB] Operation completed over 1 objects/8.2 KiB. student_00_79dcf3951326@cloudshell:~ (qwiklabs-gcp-01-8448f2216078)$ kubectx onprem.k8s.local Switched to context "onprem.k8s.local". student_00_79dcf3951326@cloudshell:~ (qwiklabs-gcp-01-8448f2216078)$ kubectl get nodes E0315 10:03:10.870240 1399 memcache.go:238] couldn't get current server API group list: Get "https://34.82.178.208/api?timeout=32s": dial tcp 34.82.178.208:443: connect: connection refused E0315 10:03:11.006351 1399 memcache.go:238] couldn't get current server API group list: Get "https://34.82.178.208/api?timeout=32s": dial tcp 34.82.178.208:443: connect: connection refused E0315 10:03:11.141861 1399 memcache.go:238] couldn't get current server API group list: Get "https://34.82.178.208/api?timeout=32s": dial tcp 34.82.178.208:443: connect: connection refused E0315 10:03:11.277416 1399 memcache.go:238] couldn't get current server API group list: Get "https://34.82.178.208/api?timeout=32s": dial tcp 34.82.178.208:443: connect: connection refused E0315 10:03:11.413416 1399 memcache.go:238] couldn't get current server API group list: Get "https://34.82.178.208/api?timeout=32s": dial tcp 34.82.178.208:443: connect: connection refused The connection to the server 34.82.178.208 was refused - did you specify the right host or port? student_00_79dcf3951326@cloudshell:~ (qwiklabs-gcp-01-8448f2216078)$ vim ./.kube/config student_00_79dcf3951326@cloudshell:~ (qwiklabs-gcp-01-8448f2216078)$ kubectl get nodes E0315 10:05:34.697260 1430 memcache.go:238] couldn't get current server API group list: Get "https://35.230.2.199/api?timeout=32s": dial tcp 35.230.2.199:443: connect: connection refused E0315 10:05:34.833560 1430 memcache.go:238] couldn't get current server API group list: Get "https://35.230.2.199/api?timeout=32s": dial tcp 35.230.2.199:443: connect: connection refused E0315 10:05:34.969812 1430 memcache.go:238] couldn't get current server API group list: Get "https://35.230.2.199/api?timeout=32s": dial tcp 35.230.2.199:443: connect: connection refused E0315 10:05:35.106062 1430 memcache.go:238] couldn't get current server API group list: Get "https://35.230.2.199/api?timeout=32s": dial tcp 35.230.2.199:443: connect: connection refused E0315 10:05:35.242874 1430 memcache.go:238] couldn't get current server API group list: Get "https://35.230.2.199/api?timeout=32s": dial tcp 35.230.2.199:443: connect: connection refused The connection to the server 35.230.2.199 was refused - did you specify the right host or port?

Aitor M. · Sprawdzono ponad 2 lata temu

Arshdeep K. · Sprawdzono ponad 2 lata temu

lab does not work. Not able to connect to "on-prem" cluster

Sandeep B. · Sprawdzono ponad 2 lata temu

Piera O. · Sprawdzono ponad 2 lata temu

Stephane L. · Sprawdzono ponad 2 lata temu

Stephane L. · Sprawdzono ponad 2 lata temu

Stephane L. · Sprawdzono ponad 2 lata temu

Stephane L. · Sprawdzono ponad 2 lata temu

Piera O. · Sprawdzono ponad 2 lata temu

Stephane L. · Sprawdzono ponad 2 lata temu

Stephane L. · Sprawdzono ponad 2 lata temu

it's broken. First part is not working. It does ask for credentials for the on-prem cluster

Robert Paul B. · Sprawdzono ponad 2 lata temu

Claudia V. · Sprawdzono ponad 2 lata temu

When running step 3 it is asking for username password .

Shashank R. · Sprawdzono ponad 2 lata temu

Kathrina B. · Sprawdzono ponad 2 lata temu

on-prem cluster is not created

Riccardo P. · Sprawdzono ponad 2 lata temu

Lab didn't work as expected, local gke cluster never was created

Jonathan T. · Sprawdzono ponad 2 lata temu

commands don't work. on prem cluster not authenticated

aziz s. · Sprawdzono ponad 2 lata temu

The commands was not working

Leonardo B. · Sprawdzono ponad 2 lata temu

Raul M. · Sprawdzono ponad 2 lata temu

EMMA B. · Sprawdzono ponad 2 lata temu

Aldo H. · Sprawdzono ponad 2 lata temu