From 004100bd30a54f8886fbbc4d452c6e21a3d3ffa1 Mon Sep 17 00:00:00 2001 From: Nilesh Londhe Date: Sat, 18 Nov 2017 20:55:28 -0800 Subject: [PATCH] fixing a typo in CIDR --- 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 d81202d..7fca2ba 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: