Opiniones sobre Hello Node Kubernetes

Jill J. · Se revisó hace casi 6 años

Haksung K. · Se revisó hace casi 6 años

Lia Y. · Se revisó hace casi 6 años

good

지연 장. · Se revisó hace casi 6 años

it is good for me because before i listen this study, i can't understand about cluster. but after this study, i can understand about that. thanks for study!

김 병. · Se revisó hace casi 6 años

No clear instructions

Hussain A. · Se revisó hace casi 6 años

Bumbae K. · Se revisó hace casi 6 años

devanshu d. · Se revisó hace casi 6 años

Mortaja A. · Se revisó hace casi 6 años

No clear instructions

Hussain A. · Se revisó hace casi 6 años

very good

Mukesh V. · Se revisó hace casi 6 años

Gérôme G. · Se revisó hace casi 6 años

little deep . Need to simplify and break in to peaces

sujith k. · Se revisó hace casi 6 años

Willian S. · Se revisó hace casi 6 años

docker push command does not work if the docker instance is stopped beforehand. Results in error message saying not found: The push refers to repository [gcr.io/gwiklabs-gcp-80f9c4179dd3322f/hello-node] tag does not exist: gcr.io/gwiklabs-gcp-80f9c4179dd3322f/hello-node:v1 creating the clusters via gcloud does not work. Results in warning and error messages. Had to create it via the console. 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) theissuance 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 creat e a cluster with legacy instance metadata endpoints disabled in the default node pool, run`clusters create` with the flag `--metadata disable-legacy-endpoint s=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 a utorepairs. 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 la tter 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_b ehavior property (gcloud config set container/new_scopes_behavior true). ERROR: (gcloud.container.clusters.create) ResponseError: code=404, message=Not found: gwiklabs-gcp-80f9c4179dd3322f creating a pod does not work: kubectl run hello-node --image=gcr.io/gwiklabs-gcp-80f9 c4179dd3322f/hello-node:v1 --port=8080 error: failed to discover supported resources: couldn't get version/kind; json parse error: json: cannot unmarshal string i nto Go value of type struct { APIVersion string "json:\"apiVersion,omitempty\""; Kind string "json:\"kind,omitempty\"" } All in all this lab was a pain.

Taka C. · Se revisó hace casi 6 años

주현 이. · Se revisó hace casi 6 años

YONGHYUN K. · Se revisó hace casi 6 años

Fabrizio P. · Se revisó hace casi 6 años

I face prolem with pod < I need some help here

Reem A. · Se revisó hace casi 6 años

Good

Youngsun L. · Se revisó hace casi 6 años

Kwon S. · Se revisó hace casi 6 años

Rami M. · Se revisó hace casi 6 años

Jiwon Y. · Se revisó hace casi 6 años

difficult

光顕 中. · Se revisó hace casi 6 años

Woojin N. · Se revisó hace casi 6 años