Networking requirements
In-cluster networking
Chef 360 Platform’s embedded cluster uses Calico as its built-in network provider. Calico is a layer 3 container networking solution that routes packets to pods.
For more information about in-cluster networking, see Container Network Interface (CNI).
Note
Controller-worker communication
k0s supports deploying an isolated control plane, which can prevent an IP route between controller nodes and the pod network. To provide the communication required by conformance tests, k0s deploys the Konnectivity service to proxy traffic from the API server into worker nodes. This lets Chef 360 Platform provide all Kubernetes API functionality while keeping the control plane isolated from worker nodes.
Note
Required ports and protocols
The required k0s ports and protocols for multi-node deployments are listed in embedded cluster requirements.
iptables
The iptables command supports legacy and nftables modes.
k0s automatically detects the mode and prefers nftables.
To check which mode k0s uses, run:
ls -lah /var/lib/k0s/bin/
The iptables symlink target shows which mode k0s selected.
k0s uses the same logic as other Kubernetes components. To verify that all components use the same mode, run:
kube-proxy:
nsenter -t $(pidof kube-proxy) -m iptables -Vkube-router:
nsenter -t $(pidof kube-router) -m /sbin/iptables -VCalico:
nsenter -t $(pidof -s calico-node) -m iptables -V
Different iptables versions have known incompatibility issues.
k0s ships an iptables version that interoperates with the other Kubernetes components it ships with. If other tools, such as firewalls, use iptables on your hosts, a version mismatch between the host’s iptables and the version shipped with k0s and its Kubernetes components can cause networking issues.
Firewalld
If you’re using firewalld on your hosts, configure it to use the same FirewallBackend as Chef 360 Platform and the other Kubernetes components. Otherwise, networking issues can occur.
Use the following tested network configuration as an example:
[root@rhel-test ~]# firewall-cmd --list-all
public (active)
target: default
icmp-block-inversion: no
interfaces: eth0
sources: 10.244.0.0/16 10.96.0.0/12
services: cockpit dhcpv6-client ssh
ports: 80/tcp 6443/tcp 8132/tcp 10250/tcp 179/tcp 179/udp
protocols:
forward: no
masquerade: yes
forward-ports:
source-ports:
icmp-blocks:
rich rules: