From b738f3074a33e104fbcfee1b3decff201f264184 Mon Sep 17 00:00:00 2001 From: Joakim Uddholm Date: Thu, 14 Nov 2019 11:02:30 +0100 Subject: [PATCH] Try to explain CIDR range a bit more when setting up worker compute resources Related to #500 --- 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..de3ad0a 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 later 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 `/24` pod subnets. Create three compute instances which will host the Kubernetes worker nodes: