Using Role-based Access Control in Kubernetes Engine Reviews

满 丁. · Reviewed almost 6 years ago

Martin L. · Reviewed almost 6 years ago

mantapu

eka agus s. · Reviewed almost 6 years ago

Parth S. · Reviewed almost 6 years ago

Nicolas D. · Reviewed almost 6 years ago

Olaf B. · Reviewed almost 6 years ago

Valeriya L. · Reviewed almost 6 years ago

Needed more time to complete.

Venkatesh S. · Reviewed almost 6 years ago

Pawel K. · Reviewed almost 6 years ago

Alberto V. · Reviewed almost 6 years ago

Alberto V. · Reviewed almost 6 years ago

Raffaele P. · Reviewed almost 6 years ago

Time is not sufficient & Cluster is not setup at 1st attampt

Prayas M. · Reviewed almost 6 years ago

ok

geoff w. · Reviewed almost 6 years ago

even when the steps are completed with the same outcome .. the checking progress cannot be done correctly... Need to redo the lab to complete is a waste of credit

siewli l. · Reviewed almost 6 years ago

Gaius H. · Reviewed about 6 years ago

Pushpendra A. · Reviewed about 6 years ago

Michael W. · Reviewed about 6 years ago

Zdenka S. · Reviewed about 6 years ago

Very interesting lab. `make create` failed with an error while creating one of the VMs when running the lab for the first time. Simply re-running `make create` did not work, restarting the whole lab did the trick. Time is a bit tight with this lab. Also, it would be nice if the user magic with the different VMs (admin, owner, auditor) could be explained. It is not clear why `kubectl` behaves differently on the different VMs.

Andreas H. · Reviewed about 6 years ago

Nick G. · Reviewed about 6 years ago

Ghanshyam P. · Reviewed about 6 years ago

suraj m. · Reviewed about 6 years ago