Skip to main content

Network

··2 mins Draft
This document is currently just a placeholder; it has yet to be written.
Please wait for it to be updated.

System Overview

Traffic Assumptions #

IDProtocolPortsNote
1IPtcp/8201All nodes within a Vault cluster will require inter-node communications on the cluster addresses using a dedicated port.
2IPtcp/443All Consul nodes will require dedicated TLS certificates, issued by Vault, to provide trusted internal communications.
3IPtcp/8300
tcp/8301
tcp/8302
All nodes within a Consul cluster will require inter-node communications on the cluster addresses using dedicated ports.
4IPtcp/443All etcd nodes will require dedicated TLS certificates, issued by Vault, to provide trusted internal communications.
5IPtcp/2380All notes with an etcd cluster will require inter-node communications on the cluster addresses using a dedicated port.
6IPtcp/2379All Kubernetes Controller nodes will require access to etcd as a client to store configuration and locks for distirbuted tasks.
7IPtcp/443All Kubernetes Controller nodes will require dedicated TLS certificates, issued by Vault, to provide trusted internal communications.
8IPtcp/6443
tcp/10250
All Kubernetes Worker and Storage nodes will require access to the Kubernetes API and Kubelet API
9VXLANn/aAll Storage nodes in the Kubernetes cluster will require inter-pod communications for the processing of data and replication of block devices.
10VXLANn/aAll Worker nodes in the Kubernetes cluster will require the ability to request and mount Persistant Volumes within the cluster.
11IPtcp/443All Worker nodes in the Kubernetes cluster will require access to Vault to retrieve certificates, secrets, and dynamic or static credentails.
12IPtcp/44
udp/8600
All Worker nodes in the Kubernetes cluster will require access to Consul to retrieve configurations settings and service discovery.
13IPtcp/3260
tcp/3263
tcp/3265
All Worker nodes in the Kubernetes cluster will require access to the iSCSI service on the Synology Network Attached Storage.

Network Configuration #

NetworkVLANIPv4 CIDRIPv6 CIDR
kub3-nat6430172.23.30.0/242a02:8010:8006:3a30::/64
kub3-services31172.23.31.0/242a02:8010:8006:3a31::/64
kub3-nodes32172.23.32.0/242a02:8010:8006:3a32::/64
kub3-prod-bridgend-01a-adminBGP172.23.40.0/242a02:8010:8006:3a40::/64
kub3-prod-bridgend-01a-worker41172.23.41.0/242a02:8010:8006:3a41::/64
kub3-prod-bridgend-01b-admin42172.23.42.0/242a02:8010:8006:3a42::/64
kub3-prod-bridgend-01b-worker43172.23.43.0/242a02:8010:8006:3a43::/64
kub3-prod-bridgend-01c-admin44172.23.44.0/242a02:8010:8006:3a44::/64
kub3-prod-bridgend-01c-worker45172.23.45.0/242a02:8010:8006:3a45::/64
kub3-prod-bridgend-01a-services40172.23.48.0/232a02:8010:8006:3a48::/64
kub3-dev-bridgend-01a-admin50172.23.50.0/242a02:8010:8006:3a50::/64
kub3-dev-bridgend-01a-worker51172.23.51.0/242a02:8010:8006:3a51::/64
kub3-dev-bridgend-01b-admin52172.23.52.0/242a02:8010:8006:3a52::/64
kub3-dev-bridgend-01b-worker53172.23.53.0/242a02:8010:8006:3a53::/64
kub3-dev-bridgend-01c-admin54172.23.54.0/242a02:8010:8006:3a54::/64
kub3-dev-bridgend-01c-worker55172.23.55.0/242a02:8010:8006:3a55::/64
kub3-dev-bridgend-01a-servicesBGP172.23.58.0/232a02:8010:8006:3a58::/64

Firewall Configuration #