menu

Using Role-based Access Control in Kubernetes Engine

Go to Lab

218 Reviews

Jacob W. · Reviewed about 8 hours ago

rajathithan r. · Reviewed 1 day ago

Jason C. · Reviewed 2 days ago

Steven A. · Reviewed 3 days 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 5 days ago

LIYU H. · Reviewed 5 days ago

Wim V. · Reviewed 5 days ago

Vivek Prasanna M. · Reviewed 5 days ago

Loris S. · Reviewed 6 days ago

Sukesh H. · Reviewed 7 days ago

Kameswar A. · Reviewed 8 days ago

good lab, I've some trouble with my internet connection, but I can recover my prev job.

Carlos A F. · Reviewed 9 days ago

KAKARAPARTHI G. · Reviewed 11 days ago

Alessandro R. · Reviewed 11 days ago

good

Alekya K. · Reviewed 11 days ago

Thien P. · Reviewed 12 days ago

good lab, I've some trouble with my internet connection, but I can recover my prev job.

Carlos A F. · Reviewed 13 days ago

Viacheslav S. · Reviewed 15 days ago

Kenji S. · Reviewed 16 days ago

Hans K. · Reviewed 16 days ago

ChangNam G. · Reviewed 16 days ago

KEERTHI REDDY A. · Reviewed 17 days ago

Koh W. · Reviewed 17 days ago

This lab did not work at all. I had the make create fail without any clear way to follow up. When I ran make validate, it created the rest of the resources the lab asked me to do later. The make teardown also failed with an inscrutable error. Got almost nothing out of this lab other than a strong suspicion of Kubernetes and GCP

Bryan E. · Reviewed 17 days ago

Ariel F. · Reviewed 18 days ago