menu

Using Role-based Access Control in Kubernetes Engine

Go to Lab

247 Reviews

This lab had some issues with completing. It looks like you have to change provider.tf and downgrade the version from 2.17.0 to 2.12.0 provider "google" { project = var.project zone = var.zone version = "~> 2.12.0" }

Ted G. · Reviewed 4 minutes ago

Ted G. · Reviewed 3 days ago

Branko J. · Reviewed 3 days ago

Bruno C. · Reviewed 4 days ago

Pedro L. · Reviewed 4 days ago

João P. · Reviewed 4 days ago

Ricardo N. · Reviewed 4 days ago

Alexandre P. · Reviewed 4 days ago

Richard S. · Reviewed 4 days ago

Kartik A. · Reviewed 5 days ago

Kartik A. · Reviewed 5 days ago

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. · Reviewed 6 days ago

Aaryan C. · Reviewed 6 days ago

Kim N. · Reviewed 7 days ago

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. · Reviewed 7 days ago

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. · Reviewed 7 days ago

Christian B. · Reviewed 9 days ago

Ramsey T. · Reviewed 9 days ago

Lee C. · Reviewed 10 days ago

utaiwut k. · Reviewed 11 days ago

Drew C. · Reviewed 12 days ago

nice

Armando M. · Reviewed 16 days ago

Oleg S. · Reviewed 16 days ago

Michael G. · Reviewed 17 days ago

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. · Reviewed 22 days ago