From 5d35fd58004e4e2cfffab67def59923229ff7a2e Mon Sep 17 00:00:00 2001 From: CFS Docs Date: Thu, 21 May 2020 17:23:41 +0000 Subject: [PATCH] Arthur Berger: Adding SE and public gateway info (#5571) --- cs_clusters.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/cs_clusters.md b/cs_clusters.md index e986f5a08..73dcd4ab8 100644 --- a/cs_clusters.md +++ b/cs_clusters.md @@ -2,7 +2,7 @@ copyright: years: 2014, 2020 -lastupdated: "2020-05-20" +lastupdated: "2020-05-21" keywords: kubernetes, iks, clusters, worker nodes, worker pools @@ -636,6 +636,8 @@ Use the {{site.data.keyword.cloud_notm}} CLI or the {{site.data.keyword.cloud_no Create your single zone or multizone VPC Generation 2 compute cluster by using the {{site.data.keyword.cloud_notm}} console. {: shortdesc} + + 1. Make sure that you complete the prerequisites to [prepare your account](#cluster_prepare) and decide on your [cluster setup](#prepare_cluster_level). 2. [Create a Virtual Private Cloud (VPC) on generation 2 compute](https://cloud.ibm.com/vpc/provision/vpc){: external} with a subnet that is located in the VPC zone where you want to create the cluster. * Verify that the banner at the beginning of the new VPC page is set to **Gen 2 compute**. If **Gen 1 compute** is set, click **Switch to Gen 2 compute**. @@ -648,7 +650,7 @@ Create your single zone or multizone VPC Generation 2 compute cluster by using t 3. Enter a name for your subnet and select the name of the VPC that you created. 4. Select the location and zone where you want to create the subnet. 5. Specify the number of IP addresses to create. VPC subnets provide IP addresses for your worker nodes and load balancer services in the cluster, so [create a VPC subnet with enough IP addresses](/docs/containers?topic=containers-vpc-subnets#vpc_basics_subnets), such as 256. You cannot change the number of IPs that a VPC subnet has later. If you enter a specific IP range, do not use the following reserved ranges: `172.16.0.0/16`, `172.18.0.0/16`, `172.19.0.0/16`, and `172.20.0.0/16`. - 6. Choose if you want to attach a public network gateway to your subnet. A public network gateway is required when you want your cluster to access public endpoints, such as a public URL of another app, or an {{site.data.keyword.cloud_notm}} service that supports public service endpoints only. Make sure to review the [VPC networking basics](/docs/containers?topic=containers-plan_clusters#plan_vpc_basics) to understand when a public network gateway is required and how you can set up your cluster to limit public access to one or more subnets only. + 6. Choose if you want to attach a public network gateway to your subnet. A public network gateway is required when you want your cluster to access public endpoints, such as a public URL of another app. Make sure to review the [VPC networking basics](/docs/containers?topic=containers-plan_clusters#plan_vpc_basics) to understand when a public network gateway is required and how you can set up your cluster to limit public access to one or more subnets only. 7. Click **Create subnet**. 4. To allow any traffic requests to apps that you deploy on your worker nodes, modify the VPC's default security group. 1. From the [Virtual private cloud dashboard](https://cloud.ibm.com/vpc-ext/network/vpcs){: external}, click the name of the **Default Security Group** for the VPC that you created.