Balanceamento de carga do Kubernetes v1.5 avaliações

Ivanna P. · Revisado há over 6 years

Tris S. · Revisado há over 6 years

Pawan H. · Revisado há over 6 years

Albert W. · Revisado há over 6 years

Rafeliya K. · Revisado há over 6 years

Setyobudi S. · Revisado há over 6 years

i love GKE,

Aushafy S. · Revisado há over 6 years

Łukasz W. · Revisado há over 6 years

Evans Nzube M. · Revisado há over 6 years

Eko H. · Revisado há over 6 years

Hiroaki S. · Revisado há over 6 years

健一 青. · Revisado há over 6 years

Hartina N. · Revisado há over 6 years

Nice

Misbahul A. · Revisado há over 6 years

Drew N. · Revisado há over 6 years

Nicola P. · Revisado há over 6 years

Michael E. · Revisado há over 6 years

Vishal I. · Revisado há over 6 years

Cam i. · Revisado há over 6 years

There is a problem with this lab - TASK 5 and TASK 6 succeed with Warnings, because of which "Check my Score" stops at 10/15, and it insists tasks were not completed. Enclosed please find results of the three commands (task 5 and task 6), followed by your "Check my score" saying tasks were not completed. This needs to be fixed please... # ============ TASK 5 ================ student_e0434708dcd6@cloudshell:~ (qwiklabs-gcp--e3c9d1708a30)$ gcloud container clusters create $CLUSTER_NAME --zone $MY_ZONE WARNING: In October 2019, node auto-upgrade will be enabled by default for newly created clusters and node pools. To disable it, use the `--no-enable-autoupgrade` flag. WARNING: Currently VPC-native is not the default mode during cluster creation. In the future, this will become the default mode and can be disabled using `--no-enable-ip-alias` flag. Use `--[no-]enable-ip-alias` flag to suppress this warning. WARNING: Starting in 1.12, default node pools in new clusters will have their legacy Compute Engine instance metadata endpoints disabled by default. To create a cluster with legacy instance metadata endpoints disabled in the default node pool, run `clusters create` with the flag `--metadata disable-legacy-endpoints=true`. WARNING: Your Pod address range (`--cluster-ipv4-cidr`) can accommodate at most 1008 node(s). This will enable the autorepair feature for nodes. Please see https://cloud.google.com/kubernetes-engine/docs/node-auto-repair for more information on node autorepairs. Creating cluster httploadbalancer in us-central1-a... Cluster is being health-checked (master is healthy)...done. Created [https://container.googleapis.com/v1/projects/qwiklabs-gcp--e3c9d1708a30/zones/us-central1-a/clusters/httploadbalancer]. To inspect the contents of your cluster, go to: https://console.cloud.google.com/kubernetes/workload_/gcloud/us-central1-a/httploadbalancer?project=qwiklabs-gcp--e3c9d1708a30 kubeconfig entry generated for httploadbalancer. NAME LOCATION MASTER_VERSION MASTER_IP MACHINE_TYPE NODE_VERSION NUM_NODES STATUS httploadbalancer us-central1-a 1.13.10-gke.0 35.225.101.253 n1-standard-1 1.13.10-gke.0 3 RUNNING # ============ TASK 6 ================ student_e0434708dcd6@cloudshell:~ (qwiklabs-gcp--e3c9d1708a30)$ kubectl run nginx --image=nginx --port=80 kubectl run --generator=deployment/apps.v1 is DEPRECATED and will be removed in a future version. Use kubectl run --generator=run-pod/v1 or kubectl create instead. deployment.apps/nginx created student_e0434708dcd6@cloudshell:~ (qwiklabs-gcp--e3c9d1708a30)$ kubectl expose deployment nginx --target-port=80 --type=NodePort service/nginx exposed # =============== progress check after task 5 and task 6 ================= Create the Kubernetes cluster for HTTP load balancing It doesn't look like you've completed this step yet. Try again.

Paul F. · Revisado há over 6 years

Michael F. · Revisado há over 6 years

Goood

Claudio Q. · Revisado há over 6 years

great lab

Robert B. · Revisado há over 6 years

Alex Y. · Revisado há over 6 years

Alex Y. · Revisado há over 6 years