Kubernetes Basics v1.6 Reviews

Kevin V. · Reviewed over 6 years ago

Sunil P. · Reviewed over 6 years ago

The certificates are outdated, so you get a warning in your browser when you try to access to site

Peter D. · Reviewed over 6 years ago

Eitan A. · Reviewed over 6 years ago

Needs update some features gave warning will be deprecated please review again.

Daniel Z. · Reviewed over 6 years ago

Amila F. · Reviewed over 6 years ago

Justin N. · Reviewed over 6 years ago

Roque R. · Reviewed over 6 years ago

Jitender K. · Reviewed over 6 years ago

Rafael F. · Reviewed over 6 years ago

ravisrip r. · Reviewed over 6 years ago

Unable to create cluster - lack of permissions google5262355_student@cloudshell:~/orchestrate-with-kubernetes/kubernetes (qwiklabs-gcp-208dc57c6c01687b)$ gcloud container clusters create bootcamp --num-nodes 5 --scopes "https://www.googleapis.com/auth/projecthosting,storage-rw" WARNING: In October 2019, node auto-upgrade will be enabled by default for newly created clusters and node pools. To disable it, use the `--no-enable-autoupgrade` flag. 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`. WARNING: Your Pod address range (`--cluster-ipv4-cidr`) can accommodate at most 1008 node(s). 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. ERROR: (gcloud.container.clusters.create) ResponseError: code=403, message=Required "container.clusters.create" permission(s) for "projects/qwiklabs-gcp-208dc57c6c01687b". See https://cloud.google.com/kubernetes-engine/docs/troubleshooting#gke_service_account_deleted for more info. google5262355_student@cloudshell:~/orchestrate-with-kubernetes/kubernetes (qwiklabs-gcp-208dc57c6c01687b)$

Adam B. · Reviewed over 6 years ago

Sushil K. · Reviewed over 6 years ago

Somewhat helpful. But it assumed I know more than I do.

AJ C. · Reviewed over 6 years ago

Dalwinder S. · Reviewed over 6 years ago

Paul J. · Reviewed over 6 years ago

Denys v. · Reviewed over 6 years ago

labs had problems with the zone and the check list didn't got updated , im retrying on us-east1-b

Thiago D. · Reviewed over 6 years ago

Amrish K. · Reviewed over 6 years ago

Priti S. · Reviewed over 6 years ago

If one commits a mistake, there are no steps to follow here. Luckily I've had experience with kubectl commands and know my way around, but I'm learning more on a deeper level.

Miguel V. · Reviewed over 6 years ago

将司 酒. · Reviewed over 6 years ago

Toshiaki O. · Reviewed over 6 years ago

Tyler B. · Reviewed over 6 years ago

Azhar M. · Reviewed over 6 years ago