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

Anton S. · Revisado há over 7 years

Duc Huy D. · Revisado há over 7 years

Praveen B. · Revisado há over 7 years

Michael R. · Revisado há over 7 years

Garrett T. · Revisado há over 7 years

Michael L. · Revisado há over 7 years

aditya y. · Revisado há over 7 years

1

Darren L. · Revisado há over 7 years

Ivan P. · Revisado há over 7 years

Brian M. · Revisado há over 7 years

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`. 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. WARNING: Starting in Kubernetes v1.10, new clusters will no longer get compute-rw and storage-ro scopes added to what is specified in --scopes (though the latter will remain included in the default --scopes). To use these scopes, add them explicitly to --scopes. To use the new behavior, set container/new_scopes_behavior property (gcloud config set container/new_scopes_behavior true). ERROR: (gcloud.container.clusters.create) ResponseError: code=409, message=Already exists: projects/qwiklabs-gcp-3bf6a6a3eb2093a2/zones/us-central1-a/clusters/httploadbalancer. google2439691_student@cloudshell:~ (qwiklabs-gcp-3bf6a6a3eb2093a2)$ kubectl run nginx --image=nginx --port= error: failed to discover supported resources: Get http://localhost:8080/apis/extensions/v1beta1: dial tcp 127.0.0.1:8080: getsockopt: connection refused google2439691_student@cloudshell:~ (qwiklabs-gcp-3bf6a6a3eb2093a2)$ kubectl run nginx --image=nginx --port=80 error: failed to discover supported resources: Get http://localhost:8080/apis/extensions/v1beta1: dial tcp 127.0.0.1:8080: getsockopt: connection refused google2439691_student@cloudshell:~ (qwiklabs-gcp-3bf6a6a3eb2093a2)$ kubectl expose deployment nginx --target-port=80 --type=NodePort The connection to the server localhost:8080 was refused - did you specify the right host or port? google2439691_student@cloudshell:~ (qwiklabs-gcp-3bf6a6a3eb2093a2)$

Eddie B. · Revisado há over 7 years

Jason D. · Revisado há over 7 years

Ravi P. · Revisado há over 7 years

Sankara K. · Revisado há over 7 years

Marcos A. · Revisado há over 7 years

SIVAKUMAR M. · Revisado há over 7 years

Smita K. · Revisado há over 7 years

Chetan S. · Revisado há over 7 years

Athuljith A. · Revisado há over 7 years

Oliver K. · Revisado há over 7 years

Alexander P. · Revisado há over 7 years

Erik L. · Revisado há over 7 years

Kichoon L. · Revisado há over 7 years

Problems with Kubernetes Clusters not having enough vm instances in the region and then inability to use other regions.

Sathish H. · Revisado há over 7 years

Ockert P. · Revisado há over 7 years