Configuring Google Kubernetes Engine (GKE) Networking Reviews

Raul M. · Reviewed almost 6 years ago

Salvador Guillermo C. · Reviewed almost 6 years ago

Mariana B. · Reviewed almost 6 years ago

Paulina C. · Reviewed almost 6 years ago

Alan A. · Reviewed almost 6 years ago

Angelica G. · Reviewed almost 6 years ago

Nestor C. · Reviewed almost 6 years ago

Good

Alejandro S. · Reviewed almost 6 years ago

Alan A. · Reviewed almost 6 years ago

Juan L. · Reviewed almost 6 years ago

Ismail H. · Reviewed almost 6 years ago

the instructions you have for the lab "Configuring Google Kubernetes Engine (GKE) Networking" does not match up what is visible on the GCP console for Kubernetes instructions Set up a private cluster On the Navigation menu (8c24be286e75dbe7.png), click Kubernetes Engine > Clusters. Click Create cluster. Name the cluster private-cluster. Select us-central1-a as the zone. Enter 2 in Number of nodes section. Click the Availability, networking, security, and additional features to expand the advanced settings section. In the Networking section, select Enable VPC-native (using alias IP) In the Network security section, select Private cluster and select Access master using its external IP address. Deselect Enable master authorized networks. This setting allows you to define the range of addresses that can access the cluster master externally. When this checkbox is not selected, you can access kubectl only from within the GCP network. In this lab, you will only access kubectl through the GCP network but you will modify this setting later. For Master IP Range, enter 172.16.0.0/28. Note: This step assumes that you don't have this range assigned to a subnet. Check VPC Networks in the GCP Console, and select a different range if necessary. Behind the scenes, GCP uses VPC peering to connect the VPC of the cluster master with your default VPC network. Click Create. what is the eta to fix the instructions to work with the latest Kubernetes console view to complete this lab?

Ramsey T. · Reviewed almost 6 years ago

Martijn E. · Reviewed almost 6 years ago

Jerry C. · Reviewed almost 6 years ago

Vishnukarthik L. · Reviewed almost 6 years ago

Ben P. · Reviewed almost 6 years ago

Hasang S. · Reviewed almost 6 years ago

Falyush F. · Reviewed almost 6 years ago

Petrus F. · Reviewed almost 6 years ago

Shusmita P. · Reviewed almost 6 years ago

Sreekanth N. · Reviewed almost 6 years ago

Arndt R. · Reviewed almost 6 years ago

Ashok R. · Reviewed almost 6 years ago

Julio B. · Reviewed almost 6 years ago

Sonu K. · Reviewed almost 6 years ago