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

满 丁. · 已于 almost 6 years前审核

Martin L. · 已于 almost 6 years前审核

mantapu

eka agus s. · 已于 almost 6 years前审核

Parth S. · 已于 almost 6 years前审核

Nicolas D. · 已于 almost 6 years前审核

Olaf B. · 已于 almost 6 years前审核

Valeriya L. · 已于 almost 6 years前审核

Needed more time to complete.

Venkatesh S. · 已于 almost 6 years前审核

Pawel K. · 已于 almost 6 years前审核

Alberto V. · 已于 almost 6 years前审核

Alberto V. · 已于 almost 6 years前审核

Raffaele P. · 已于 almost 6 years前审核

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

Prayas M. · 已于 almost 6 years前审核

ok

geoff w. · 已于 almost 6 years前审核

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. · 已于 almost 6 years前审核

Gaius H. · 已于 about 6 years前审核

Pushpendra A. · 已于 about 6 years前审核

Michael W. · 已于 about 6 years前审核

Zdenka S. · 已于 about 6 years前审核

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. · 已于 about 6 years前审核

Nick G. · 已于 about 6 years前审核

Ghanshyam P. · 已于 about 6 years前审核

suraj m. · 已于 about 6 years前审核