menu

Using Role-based Access Control in Kubernetes Engine

Go to Lab

237 评论

Kartik A. · 评论大約一小時之前

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. · 评论大約 14 小時之前

Aaryan C. · 评论一天之前

Kim N. · 评论一天之前

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. · 评论2 天之前

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. · 评论2 天之前

Christian B. · 评论4 天之前

Ramsey T. · 评论4 天之前

Lee C. · 评论5 天之前

utaiwut k. · 评论5 天之前

Drew C. · 评论7 天之前

nice

Armando M. · 评论11 天之前

Oleg S. · 评论11 天之前

Michael G. · 评论12 天之前

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. · 评论17 天之前

gff

Suresh T. · 评论19 天之前

Duncan H. · 评论20 天之前

Pablo L. · 评论20 天之前

近藤洋平 近. · 评论20 天之前

Jacob W. · 评论22 天之前

rajathithan r. · 评论22 天之前

Jason C. · 评论23 天之前

Steven A. · 评论24 天之前

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. · 评论26 天之前

LIYU H. · 评论26 天之前