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

Lee N. · Sprawdzono ponad 6 lat temu

Marcin T. · Sprawdzono ponad 6 lat temu

Adi P. · Sprawdzono ponad 6 lat temu

Karen I. · Sprawdzono ponad 6 lat temu

Wesley Goi -. · Sprawdzono ponad 6 lat temu

cuong t. · Sprawdzono ponad 6 lat temu

FARID A. · Sprawdzono ponad 6 lat temu

林昭賢林. · Sprawdzono ponad 6 lat temu

Mohammed Azfar .. · Sprawdzono ponad 6 lat temu

Narendra M. · Sprawdzono ponad 6 lat temu

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. · Sprawdzono ponad 6 lat temu

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. · Sprawdzono ponad 6 lat temu

Dennis J. · Sprawdzono ponad 6 lat temu

Adarsh K. · Sprawdzono ponad 6 lat temu

Gustavo R. · Sprawdzono ponad 6 lat temu

Monique V. · Sprawdzono ponad 6 lat temu

Dipak P. · Sprawdzono ponad 6 lat temu

Hima A. · Sprawdzono ponad 6 lat temu

Sreenivas M. · Sprawdzono ponad 6 lat temu

Tan W. · Sprawdzono ponad 6 lat temu

Madhu C. · Sprawdzono ponad 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 ponad 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 ponad 6 lat temu