Hello Node Kubernetes avis

Ayman A. · Examiné il y a plus de 6 ans

Finally completed this lab after creating the case in your support center and get a satisfied answer from your support team.

Alap M. · Examiné il y a plus de 6 ans

Wei Chiang L. · Examiné il y a plus de 6 ans

Jorge O. · Examiné il y a plus de 6 ans

Rodrigo J. · Examiné il y a plus de 6 ans

Juan Carlos P. · Examiné il y a plus de 6 ans

Ramses Isaac A. · Examiné il y a plus de 6 ans

done!

Aedah A. · Examiné il y a plus de 6 ans

Muy bueno

Javier C. · Examiné il y a plus de 6 ans

At the end of the lab cloud start lagging so I can finish optional sections

Kirill K. · Examiné il y a plus de 6 ans

There was warning saying "WARNING: `gcloud docker` will not be supported for Docker client versions above 18.03." May be gcloud docker command needs to be updated. And multiple warnings while creating the cluster 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-i p-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 endp oints 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 --sco pes). 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). Optional Dashboard part did not work. There were lots of error message on the screen. Overall experience was good, finished 1min before the end-time. Other session had lot of extra time.

Sushanth Bobby L. · Examiné il y a plus de 6 ans

Irvi A. · Examiné il y a plus de 6 ans

Viranita J. · Examiné il y a plus de 6 ans

Denys G. · Examiné il y a plus de 6 ans

Caleb F. · Examiné il y a plus de 6 ans

Mark C. · Examiné il y a plus de 6 ans

Abimael D. · Examiné il y a plus de 6 ans

Rasha G. · Examiné il y a plus de 6 ans

Wooow!! I'm so proud of what I've been able to sock in this tutorial. Feedback: Time seemed to be a limiting factor when it came to tying commands to understand what was going on.

Dominic M. · Examiné il y a plus de 6 ans

Amanda J. · Examiné il y a plus de 6 ans

Pedro S. · Examiné il y a plus de 6 ans

Nesrine B. · Examiné il y a plus de 6 ans

Balamurugan s. · Examiné il y a plus de 6 ans

satisfied

Mohamed E. · Examiné il y a plus de 6 ans

Joris S. · Examiné il y a plus de 6 ans