Hello Node Kubernetes avaliações

Viktor M. · Revisado há over 7 years

Vitaliy N. · Revisado há over 7 years

Tried multiple times including just copying the work and it failed each time

mimi m. · Revisado há over 7 years

Frederic V. · Revisado há over 7 years

Perfect!

Ahmed A. · Revisado há over 7 years

Lucas F. · Revisado há over 7 years

Wo K. · Revisado há over 7 years

Martin R. · Revisado há over 7 years

Santiago C. · Revisado há over 7 years

Kelvin Y. · Revisado há over 7 years

good

Mr. Venkata Harsha(Venkata J) J. · Revisado há over 7 years

Uriel C. · Revisado há over 7 years

Not enough time to complete all the steps.

Ebony P. · Revisado há over 7 years

On Kuberneties module after entering this command Create a cluster with two n1-standard-1 nodes (this will take a few minutes to complete): gcloud container clusters create hello-world \ --num-nodes 2 \ --machine-type n1-standard-1 \ --zone us-central1-a got this error WARNING: Starting in 1.12, new clusters will have basic authentication disabled by default. Basic authentication can be enabled (or disabled) manually using the `--[no-]enable-basic-auth` flag.WARNING: Starting in 1.12, new clusters will not have a client certificate issued. You can manually enable (or disable) the issuance of the client certificate using the `--[no-]issue-client-certificate` 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`.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).

He R. · Revisado há over 7 years

Good

wayne g. · Revisado há over 7 years

ok

Medard D. · Revisado há over 7 years

Eleanor M. · Revisado há over 7 years

Eleanor M. · Revisado há over 7 years

Time Ran out

Aritra S. · Revisado há over 7 years

Macc H. · Revisado há over 7 years

houssem eddine k. · Revisado há over 7 years

Julio D. · Revisado há over 7 years

Samuel O. · Revisado há over 7 years

Alfred K. · Revisado há over 7 years