Using Role-based Access Control in Kubernetes Engine avis

Lee N. · Examiné il y a plus de 6 ans

Marcin T. · Examiné il y a plus de 6 ans

Adi P. · Examiné il y a plus de 6 ans

Karen I. · Examiné il y a plus de 6 ans

Wesley Goi -. · Examiné il y a plus de 6 ans

cuong t. · Examiné il y a plus de 6 ans

FARID A. · Examiné il y a plus de 6 ans

林昭賢林. · Examiné il y a plus de 6 ans

Mohammed Azfar .. · Examiné il y a plus de 6 ans

Narendra M. · Examiné il y a plus de 6 ans

I'm running into an issue retrieving the latest_node_version (errors on line 19 and 90 of main.tf) when running make create, which means I'm unable to complete the deployment.

David M. · Examiné il y a plus de 6 ans

I do twice time this lab with encountered 2 errors : Error: Error retrieving available container cluster versions: Get https://container.googleapis.com/v1beta1/projects/qwiklabs-gcp-00-00eb0d00f0f3/locations/us-central1-a/serverConfig?alt=json&prettyPrint=false: Get http://169.254.169.254/computeMetadata/v1/instance/service-accounts/default/token?scopes=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcompute%2Chttps%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcloud-platform%2Chttps%3A%2F%2Fwww.googleapis.com%2Fauth%2Fndev.clouddns.readwrite%2Chttps%3A%2F%2Fwww.googleapis.com%2Fauth%2Fdevstorage.full_control: dial tcp 169.254.169.254:80: i/o timeout on main.tf line 19, in data "google_container_engine_versions" "on-prem": 19: data "google_container_engine_versions" "on-prem" { Error: Error running command 'gcloud compute scp --project qwiklabs-gcp-00-017fdd29d477 --zone us-central1-a --recurse modules/instance/manifests gke-tutorial-owner:': exit status 1. Output: ssh: connect to host 35.226.105.92 port 22: Connection timed out lost connection ERROR: (gcloud.compute.scp) [/usr/bin/scp] exited with return code [1]. So i tried the 3th time, and it's succeeded !

Eryk H. · Examiné il y a plus de 6 ans

Dennis J. · Examiné il y a plus de 6 ans

Adarsh K. · Examiné il y a plus de 6 ans

Gustavo R. · Examiné il y a plus de 6 ans

Monique V. · Examiné il y a plus de 6 ans

Dipak P. · Examiné il y a plus de 6 ans

Hima A. · Examiné il y a plus de 6 ans

Sreenivas M. · Examiné il y a plus de 6 ans

Tan W. · Examiné il y a plus de 6 ans

Madhu C. · Examiné il y a plus de 6 ans

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. · Examiné il y a plus de 6 ans

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. · Examiné il y a plus de 6 ans