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 etwa 14 Stunden ago

Ted G. · Reviewed 4 Tage ago

Branko J. · Reviewed 4 Tage ago

Bruno C. · Reviewed 5 Tage ago

Pedro L. · Reviewed 5 Tage ago

João P. · Reviewed 5 Tage ago

Ricardo N. · Reviewed 5 Tage ago

Alexandre P. · Reviewed 5 Tage ago

Richard S. · Reviewed 5 Tage ago

Kartik A. · Reviewed 6 Tage ago

Kartik A. · Reviewed 6 Tage 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 Tage ago

Aaryan C. · Reviewed 7 Tage ago

Kim N. · Reviewed 7 Tage 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 8 Tage 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 8 Tage ago

Christian B. · Reviewed 9 Tage ago

Ramsey T. · Reviewed 9 Tage ago

Lee C. · Reviewed 11 Tage ago

utaiwut k. · Reviewed 11 Tage ago

Drew C. · Reviewed 13 Tage ago

nice

Armando M. · Reviewed 17 Tage ago

Oleg S. · Reviewed 17 Tage ago

Michael G. · Reviewed 18 Tage 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 23 Tage ago