Subnetting
In the Shturval platform, when creating a cluster, the following are highlighted by default:
- pod subnet: 172.16.0.0/16
- service subnet: 10.96.0.0/12
The subnet range can be changed to suit your needs. It is recommended to check ranges for intersections before creating a cluster. To determine whether pod and service subnets overlap in an initialized cluster, see Checking subnet overlap.
Subnets of pods and services are located in the general overlay network of the cluster. The subnetwork of pods and services is deployed only within the cluster and does not intersect with other clusters or your corporate network. In fact, even if the pod/service subnet matches your corporate one, the pods will not have access to services outside the cluster.
By default, clusters allow all incoming and outgoing traffic. To manage network policies the Shturval platform uses Cilium (CNI).
On each cluster node, a separate subnet is allocated from the common subnet of pods. If outbound traffic is allowed in a cluster, by default all outbound traffic will originate from the node’s IP. You can configure a dedicated IP address or network interface for individual namespaces by configuring Egress parameters on the namespace page.
Incoming traffic to the cluster by default comes to the cluster’s Ingress IP address. To allocate an IP address for the namespace, configure Ingress parameters on the namespace page.
Subnets used
Example of using subnets
