关于“Using Role-based Access Control in Kubernetes Engine”的评价

The "make validate" step preempts later lab activities by running kubectl operations on the cluster, which means that later steps have the wrong information.

Henry B. · 已于 almost 7 years前审核

The "make validate" step preempts later lab activities by running kubectl operations on the cluster, which means that later steps have the wrong information.

Henry B. · 已于 almost 7 years前审核

Chris B. · 已于 almost 7 years前审核

Ramsey T. · 已于 almost 7 years前审核

Lee C. · 已于 almost 7 years前审核

utaiwut k. · 已于 almost 7 years前审核

Drew C. · 已于 almost 7 years前审核

nice

Armando M. · 已于 almost 7 years前审核

Oleg S. · 已于 almost 7 years前审核

Michael G. · 已于 almost 7 years前审核

This lab doesn't work. The first time through "make create," one of the VMs failed with a connection refused. After tearing down the systems, the second "make create" could not create the GKE cluster.

Kevin K. · 已于 almost 7 years前审核

gff

Suresh T. · 已于 almost 7 years前审核

Duncan H. · 已于 almost 7 years前审核

Pablo L. · 已于 almost 7 years前审核

近藤洋平 近. · 已于 almost 7 years前审核

Jacob W. · 已于 almost 7 years前审核

rajathithan r. · 已于 almost 7 years前审核

Jason C. · 已于 almost 7 years前审核

Steven A. · 已于 almost 7 years前审核

There are several inconsistencies in scenario 1 and 2. The expected lab result from commands differs from what is actually given. It seems the terraform script have already provisioned user serviceaccounts/namespaces etc. that the lab script assume have not been provisioned.

Cato F. · 已于 almost 7 years前审核

George H. · 已于 almost 7 years前审核

Wim V. · 已于 almost 7 years前审核

Vivek Prasanna M. · 已于 almost 7 years前审核

Loris S. · 已于 almost 7 years前审核

Sukesh H. · 已于 almost 7 years前审核