Skip to content

Commit 818d45a

Browse files
committed
address planning formatting
1 parent 02c73cc commit 818d45a

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

content/series/k8s-cilium-ipv6/part1.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -29,16 +29,16 @@ The most basic lab scenario to create a Kubernetes cluster contains 1 control pl
2929

3030
Let's assume `2001:db8::/48` as the parent block which we will break down into smaller chunks of /56 prefixes. I have found this online [subnetting calculator](https://www.cidr.eu/en/calculator) to be of great help for address planning. A `/48` gives us `2^8 = 256 x /56` prefixes and each `/56` gives us `256 x /64` subnets. We want to stick to best practices outlined in RFC 7421, RFC 8504 hence we are going to treat /64 as the network boundary. We will be using different non overlapping /64 subnets for addressing our nodes, pods, services, gateway/ingress addresses etc. though our most immediate need is an address block for our cluster nodes. Let's allocate the first /56 prefix i.e `2001:db8::/56` to address all our cluster nodes.
3131

32-
While there is no such hard rule, it is a good practice to keep control plane nodes and worker nodes contained in their own respective Layer3 boundaries which provides some degree of network isolation and logical separation which helps keep the overall network design clean.
32+
While there is no such hard rule, it is a good practice to keep control plane nodes and worker nodes contained in their own respective Layer3 boundaries which provides some degree of network isolation as well as logical separation to keep the overall design clean.
33+
In part 3 of this series I will cover more about address planning for various Kubernetes components (pods, services, ingress, egress etc.), but the following is the bare minimum need to get underlying infrastructure setup
3334

3435
```sh
35-
2001:db8::/56 # node addressing pool
36-
|
37-
|-- 2001:db8::/64 # control nodes
38-
|-- 2001:db8:0:1::/64 # worker nodes
39-
|-- 2001:db8:0:2::/64 # reserved
40-
41-
..snipped..
36+
2001:db8::/48 # parent block
37+
|-- 2001:db8::/56 # node address pool
38+
\-- 2001:db8::/64 # control nodes
39+
\-- 2001:db8:0:1::/64 # worker nodes
40+
\-- 2001:db8:0:2::/64 # reserved
41+
...
4242
```
4343

4444
### DNS64 and NAT64

0 commit comments

Comments
 (0)