From 4de0d62cef34fd8859966e16513c9d90dca88a2d Mon Sep 17 00:00:00 2001 From: Ajay Chenampara Date: Thu, 9 Jul 2020 16:44:25 -0400 Subject: [PATCH] Subnet info fix. A /16 supports 256 /24 subnets. --- docs/03-compute-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/03-compute-resources.md b/docs/03-compute-resources.md index a30c520..fc5f487 100644 --- a/docs/03-compute-resources.md +++ b/docs/03-compute-resources.md @@ -118,7 +118,7 @@ done Each worker instance requires a pod subnet allocation from the Kubernetes cluster CIDR range. The pod subnet allocation will be used to configure container networking in a later exercise. The `pod-cidr` instance metadata will be used to expose pod subnet allocations to compute instances at runtime. -> The Kubernetes cluster CIDR range is defined by the Controller Manager's `--cluster-cidr` flag. In this tutorial the cluster CIDR range will be set to `10.200.0.0/16`, which supports 254 subnets. +> The Kubernetes cluster CIDR range is defined by the Controller Manager's `--cluster-cidr` flag. In this tutorial the cluster CIDR range will be set to `10.200.0.0/16`, which supports 256 /24 subnets. Create three compute instances which will host the Kubernetes worker nodes: