menu

Using Role-based Access Control in Kubernetes Engine

Go to Lab

237 Revisar

Kartik A. · Avaliado 5 minutos atrás

No scoring eh? A bit opaque on the roles being created / applied - left to reader to investigate deeper, not likely in time allowed.

Billy G. · Avaliado aproximadamente 13 horas atrás

Aaryan C. · Avaliado aproximadamente 24 horas atrás

Kim N. · Avaliado 1 dia atrás

The "make validate" step preempts later lab activities by running kubectl operations on the cluster, which means that later steps have the wrong information.

Henry B. · Avaliado 2 dias atrás

The "make validate" step preempts later lab activities by running kubectl operations on the cluster, which means that later steps have the wrong information.

Henry B. · Avaliado 2 dias atrás

Christian B. · Avaliado 4 dias atrás

Ramsey T. · Avaliado 4 dias atrás

Lee C. · Avaliado 5 dias atrás

utaiwut k. · Avaliado 5 dias atrás

Drew C. · Avaliado 7 dias atrás

nice

Armando M. · Avaliado 11 dias atrás

Oleg S. · Avaliado 11 dias atrás

Michael G. · Avaliado 12 dias atrás

This lab doesn't work. The first time through "make create," one of the VMs failed with a connection refused. After tearing down the systems, the second "make create" could not create the GKE cluster.

Kevin K. · Avaliado 17 dias atrás

gff

Suresh T. · Avaliado 19 dias atrás

Duncan H. · Avaliado 20 dias atrás

Pablo L. · Avaliado 20 dias atrás

近藤洋平 近. · Avaliado 20 dias atrás

Jacob W. · Avaliado 22 dias atrás

rajathithan r. · Avaliado 22 dias atrás

Jason C. · Avaliado 23 dias atrás

Steven A. · Avaliado 24 dias atrás

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. · Avaliado 26 dias atrás

LIYU H. · Avaliado 26 dias atrás