Using Role-based Access Control in Kubernetes Engine Reviews

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. · Reviewed almost 7 years ago

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. · Reviewed almost 7 years ago

Chris B. · Reviewed almost 7 years ago

Ramsey T. · Reviewed almost 7 years ago

Lee C. · Reviewed almost 7 years ago

utaiwut k. · Reviewed almost 7 years ago

Drew C. · Reviewed almost 7 years ago

nice

Armando M. · Reviewed about 7 years ago

Oleg S. · Reviewed about 7 years ago

Michael G. · Reviewed about 7 years ago

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. · Reviewed about 7 years ago

gff

Suresh T. · Reviewed about 7 years ago

Duncan H. · Reviewed about 7 years ago

Pablo L. · Reviewed about 7 years ago

近藤洋平 近. · Reviewed about 7 years ago

Jacob W. · Reviewed about 7 years ago

rajathithan r. · Reviewed about 7 years ago

Jason C. · Reviewed about 7 years ago

Steven A. · Reviewed about 7 years ago

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. · Reviewed about 7 years ago

George H. · Reviewed about 7 years ago

Wim V. · Reviewed about 7 years ago

Vivek Prasanna M. · Reviewed about 7 years ago

Loris S. · Reviewed about 7 years ago

Sukesh H. · Reviewed about 7 years ago