Using Role-based Access Control in Kubernetes Engine Reviews

No scoring eh? A bit opaque on the roles being created / applied - left to reader to investigate deeper, not likely in time allowed.

Billy G. · Reviewed over 6 years ago

Aaryan C. · Reviewed over 6 years ago

Kim N. · Reviewed over 6 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 over 6 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 over 6 years ago

Chris B. · Reviewed over 6 years ago

Ramsey T. · Reviewed over 6 years ago

Lee C. · Reviewed over 6 years ago

utaiwut k. · Reviewed over 6 years ago

Drew C. · Reviewed over 6 years ago

nice

Armando M. · Reviewed over 6 years ago

Oleg S. · Reviewed over 6 years ago

Michael G. · Reviewed over 6 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 over 6 years ago

gff

Suresh T. · Reviewed over 6 years ago

Duncan H. · Reviewed over 6 years ago

Pablo L. · Reviewed over 6 years ago

近藤洋平 近. · Reviewed over 6 years ago

Jacob W. · Reviewed over 6 years ago

rajathithan r. · Reviewed over 6 years ago

Jason C. · Reviewed over 6 years ago

Steven A. · Reviewed over 6 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 over 6 years ago

George H. · Reviewed over 6 years ago

Wim V. · Reviewed over 6 years ago