Como usar o controle de acesso baseado em função no Kubernetes Engine avaliações

满 丁. · Revisado há almost 6 years

Martin L. · Revisado há almost 6 years

mantapu

eka agus s. · Revisado há almost 6 years

Parth S. · Revisado há almost 6 years

Nicolas D. · Revisado há almost 6 years

Olaf B. · Revisado há almost 6 years

Valeriya L. · Revisado há almost 6 years

Needed more time to complete.

Venkatesh S. · Revisado há almost 6 years

Pawel K. · Revisado há almost 6 years

Alberto V. · Revisado há almost 6 years

Alberto V. · Revisado há almost 6 years

Raffaele P. · Revisado há almost 6 years

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

Prayas M. · Revisado há almost 6 years

ok

geoff w. · Revisado há 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. · Revisado há almost 6 years

Gaius H. · Revisado há about 6 years

Pushpendra A. · Revisado há about 6 years

Michael W. · Revisado há about 6 years

Zdenka S. · Revisado há 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. · Revisado há about 6 years

Nick G. · Revisado há about 6 years

Ghanshyam P. · Revisado há about 6 years

suraj m. · Revisado há about 6 years