Opinie (Using Role-based Access Control in Kubernetes Engine)

Hima A. · Sprawdzono około 6 lat temu

Sreenivas M. · Sprawdzono około 6 lat temu

Tan W. · Sprawdzono około 6 lat temu

Madhu C. · Sprawdzono około 6 lat temu

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. · Sprawdzono około 6 lat temu

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. · Sprawdzono około 6 lat temu

German G. · Sprawdzono ponad 6 lat temu

This lab does not work, I contacted the support and no one responded, terrible experience.

Piotr W. · Sprawdzono ponad 6 lat temu

This lab does not work, I contacted the support and no one responded, terrible experience.

Piotr W. · Sprawdzono ponad 6 lat temu

Aliaksandr S. · Sprawdzono ponad 6 lat temu

Lisandro V. · Sprawdzono ponad 6 lat temu

Christopher A. · Sprawdzono ponad 6 lat temu

mike k. · Sprawdzono ponad 6 lat temu

mike k. · Sprawdzono ponad 6 lat temu

Hemant K. · Sprawdzono ponad 6 lat temu

Arif D. · Sprawdzono ponad 6 lat temu

Was not having enough time to complete the teardown scripts

Niran V. · Sprawdzono ponad 6 lat temu

Joslyn J. · Sprawdzono ponad 6 lat temu

Adrian N. · Sprawdzono ponad 6 lat temu

Filip M. · Sprawdzono ponad 6 lat temu

Mahesh E. · Sprawdzono ponad 6 lat temu

Mohamed A. · Sprawdzono ponad 6 lat temu

Repo needs updating

Carlin S. · Sprawdzono ponad 6 lat temu

Arif D. · Sprawdzono ponad 6 lat temu

RACHABATTUNI S. · Sprawdzono ponad 6 lat temu