Using Role-based Access Control in Kubernetes Engine Reviews

满 丁. · Reviewed ما يقرب من 6 سنوات ago

Martin L. · Reviewed ما يقرب من 6 سنوات ago

mantapu

eka agus s. · Reviewed ما يقرب من 6 سنوات ago

Parth S. · Reviewed ما يقرب من 6 سنوات ago

Nicolas D. · Reviewed ما يقرب من 6 سنوات ago

Olaf B. · Reviewed ما يقرب من 6 سنوات ago

Valeriya L. · Reviewed ما يقرب من 6 سنوات ago

Needed more time to complete.

Venkatesh S. · Reviewed ما يقرب من 6 سنوات ago

Pawel K. · Reviewed ما يقرب من 6 سنوات ago

Alberto V. · Reviewed ما يقرب من 6 سنوات ago

Alberto V. · Reviewed ما يقرب من 6 سنوات ago

Raffaele P. · Reviewed ما يقرب من 6 سنوات ago

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

Prayas M. · Reviewed ما يقرب من 6 سنوات ago

ok

geoff w. · Reviewed ما يقرب من 6 سنوات 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 ما يقرب من 6 سنوات ago

Gaius H. · Reviewed حوالي 6 سنوات ago

Pushpendra A. · Reviewed حوالي 6 سنوات ago

Michael W. · Reviewed حوالي 6 سنوات ago

Zdenka S. · Reviewed حوالي 6 سنوات 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 حوالي 6 سنوات ago

Nick G. · Reviewed حوالي 6 سنوات ago

Ghanshyam P. · Reviewed حوالي 6 سنوات ago

suraj m. · Reviewed حوالي 6 سنوات ago