Using Role-based Access Control in Kubernetes Engine Reviews
19606 reviews
Tan W. · Reviewed almost 6 years ago
Madhu C. · Reviewed almost 6 years ago
This lab is very difficult to accomplish. I spent a considerable amount of time across multiple attempts to finally get this working. Just to get the initial environment created requires making three - possibly four - changes in the main.tf file: - line 20, change 'zone' to 'location' - line 87, change 'zone' to 'location' - line 132, add a new line after line 132 and add 'enable_private_endpoint = false' - maybe optional, in the resource "google_container_cluster" add the following timeouts arguments: ... timeouts { create = "60m" update = "60m" delete = "60m" } ... Once those were complete, I was finally able to create the initial GKE cluster environment. The information and exercises presented are valuable. It demonstrates how RBAC affects access to resources in GCP and GKE. It also demonstrates the impact of misconfigured RBAC rules. If only it was not so painful to complete this lab though!
Alex T. · Reviewed almost 6 years ago
This lab is very difficult to accomplish. I spent a considerable amount of time across multiple attempts to finally get this working. Just to get the initial environment created requires making three - possibly four - changes in the main.tf file: - line 20, change 'zone' to 'location' - line 87, change 'zone' to 'location' - line 132, add a new line after line 132 and add 'enable_private_endpoint = false' - maybe optional, in the resource "google_container_cluster" add the following timeouts arguments: ... timeouts { create = "60m" update = "60m" delete = "60m" } ... Once those were complete, I was finally able to create the initial GKE cluster environment.
Alex T. · Reviewed almost 6 years ago
German G. · Reviewed almost 6 years ago
This lab does not work, I contacted the support and no one responded, terrible experience.
Piotr W. · Reviewed almost 6 years ago
This lab does not work, I contacted the support and no one responded, terrible experience.
Piotr W. · Reviewed almost 6 years ago
Aliaksandr S. · Reviewed almost 6 years ago
Lisandro V. · Reviewed almost 6 years ago
Christopher A. · Reviewed almost 6 years ago
mike k. · Reviewed almost 6 years ago
mike k. · Reviewed almost 6 years ago
Hemant K. · Reviewed almost 6 years ago
Arif D. · Reviewed almost 6 years ago
Was not having enough time to complete the teardown scripts
Niran V. · Reviewed almost 6 years ago
Joslyn J. · Reviewed almost 6 years ago
Adrian N. · Reviewed almost 6 years ago
Filip M. · Reviewed almost 6 years ago
Mahesh E. · Reviewed almost 6 years ago
Mohamed A. · Reviewed almost 6 years ago
Repo needs updating
Carlin S. · Reviewed almost 6 years ago
Arif D. · Reviewed almost 6 years ago
RACHABATTUNI S. · Reviewed almost 6 years ago
Arif D. · Reviewed almost 6 years ago
Franciszek B. · Reviewed almost 6 years ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.