Opinie (Hello Node Kubernetes)

Ramses Isaac A. · Sprawdzono prawie 6 lat temu

done!

Aedah A. · Sprawdzono prawie 6 lat temu

Muy bueno

Javier C. · Sprawdzono prawie 6 lat temu

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

Kirill K. · Sprawdzono prawie 6 lat temu

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. · Sprawdzono prawie 6 lat temu

Irvi A. · Sprawdzono prawie 6 lat temu

Viranita J. · Sprawdzono prawie 6 lat temu

Denys G. · Sprawdzono prawie 6 lat temu

Caleb F. · Sprawdzono prawie 6 lat temu

Mark C. · Sprawdzono prawie 6 lat temu

Abimael D. · Sprawdzono prawie 6 lat temu

Rasha G. · Sprawdzono prawie 6 lat temu

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. · Sprawdzono prawie 6 lat temu

Amanda J. · Sprawdzono prawie 6 lat temu

Pedro S. · Sprawdzono prawie 6 lat temu

Nesrine B. · Sprawdzono prawie 6 lat temu

Balamurugan s. · Sprawdzono prawie 6 lat temu

satisfied

Mohamed E. · Sprawdzono prawie 6 lat temu

Joris S. · Sprawdzono prawie 6 lat temu

shiju d. · Sprawdzono prawie 6 lat temu

Torsten D. · Sprawdzono prawie 6 lat temu

thank's google

Belalia M. · Sprawdzono prawie 6 lat temu

Vipul K. · Sprawdzono prawie 6 lat temu

Christian V. · Sprawdzono prawie 6 lat temu

Simon T. · Sprawdzono prawie 6 lat temu