From ec9c9ec1d12a8bfb688799b534d23786770e3402 Mon Sep 17 00:00:00 2001 From: mverkruyse Date: Thu, 23 May 2019 17:35:01 -0700 Subject: [PATCH] Update 03-compute-resources.md CIDR range for work nodes is 10.200.0.0/24, not /16 --- 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 bd92c3c..6841d92 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/24`, which supports 254 subnets. Create three compute instances which will host the Kubernetes worker nodes: