Kubernetes and Linux host requirements
This page describes the Kubernetes and Linux host requirements for the embedded cluster included with Chef 360 Platform. For related requirements, see:
- Embedded cluster requirements: licensing, hardware, storage, port, FQDN, disaster recovery, and firewall requirements.
- Networking requirements: ports and protocols for multi-node clusters.
Kubernetes requirements
The Chef 360 Platform embedded Kubernetes cluster uses k0s as its underlying runtime. The cluster has the same limitations as k0s. When requirements conflict, follow the Chef 360 Platform documentation. For example, k0s has experimental support for Windows, but Chef 360 Platform doesn’t support Windows-based clusters.
Preflight checks verify the system requirements during installation and configuration. Review these requirements before you install the cluster.
External runtime dependencies
Chef 360 Platform packages its k0s distribution as a single binary that includes all required components. The binaries use static linking, so k0s typically needs few external runtime dependencies.
Machine ID
In a multi-node setup, k0s requires each host to have a unique machine ID,
a host identifier that generally remains stable across reboots.
For Linux, k0s reads this ID from the /var/lib/dbus/machine-id or /etc/machine-id files.
If neither file exists, k0s uses a machine ID based on the hostname.
When you run k0s in virtualized or containerized environments, make sure each host has a unique ID, even if you create the hosts from the same image.
Linux requirements
Linux kernel configuration
k0s and Kubernetes need specific Linux kernel features to run Chef 360 Platform worker nodes. Linux kernel versions 4.3 and later include all the required configurations.
During a preflight check, k0s checks the Linux kernel version and shows a warning if it’s below version 3.10. If you’re running an older Linux kernel, your system can still meet the requirements if it has the following features:
CONFIG_CGROUPS: Control Group supportCONFIG_CGROUP_FREEZER: Freezer cgroup subsystemCONFIG_CGROUP_PIDS: PIDs cgroup subsystem kubernetes/kubeadm#2335 (comment)CONFIG_CGROUP_DEVICE: Device controller for cgroupsCONFIG_CPUSETS: Cpuset supportCONFIG_CGROUP_CPUACCT: Simple CPU accounting cgroup subsystemCONFIG_MEMCG: Memory Resource Controller for Control Groups- (optional)
CONFIG_CGROUP_HUGETLB: HugeTLB Resource Controller for Control Groups kubernetes/kubeadm#2335 (comment) CONFIG_CGROUP_SCHED: Group CPU schedulerCONFIG_FAIR_GROUP_SCHED: Group scheduling for SCHED_OTHER kubernetes/kubeadm#2335 (comment)- (optional)
CONFIG_CFS_BANDWIDTH: CPU bandwidth provisioning for FAIR_GROUP_SCHED Enable this option if you enable CPU CFS quota enforcement for containers that specify CPU limits (--cpu-cfs-quota).
- (optional)
- (optional)
CONFIG_BLK_CGROUP: Block IO controller kubernetes/kubernetes#92287 (comment)
CONFIG_NAMESPACES: Namespaces supportCONFIG_UTS_NS: UTS namespaceCONFIG_IPC_NS: IPC namespaceCONFIG_PID_NS: PID namespaceCONFIG_NET_NS: Network namespace
CONFIG_NET: Networking supportCONFIG_INET: TCP/IP networkingCONFIG_NETFILTER: Network packet filtering framework (Netfilter)- (optional)
CONFIG_NETFILTER_ADVANCED: Advanced netfilter configuration CONFIG_NETFILTER_XTABLES: Netfilter Xtables supportCONFIG_NETFILTER_XT_TARGET_REDIRECT: REDIRECT target supportCONFIG_NETFILTER_XT_MATCH_COMMENT: “comment” match support
- (optional)
CONFIG_EXT4_FS: The Extended 4 (ext4) filesystemCONFIG_PROC_FS: /proc file system support
Note
The kernel configuration must be accessible at runtime for k0s to run its pre-flight check.
Enable CONFIG_IKCONFIG_PROC,
and, if enabled as a module, load the modprobe configs module to ensure accessibility.
Control groups (cgroups)
k0s supports both cgroup v1 and cgroup v2.
Required cgroup controllers:
- cpu
- cpuacct
- cpuset
- memory
- devices
- freezer
- pids
Optional cgroup controllers:
containerd and cri-o use blkio to track disk I/O and throttling in both cgroup v1 and v2.
Name service switch limitations
k0s statically links its Linux binaries against musl libc by default, including the binaries on the GitHub releases pages. Static linking lets k0s run across a wide range of Linux environments because it doesn’t require a specific standard C library on the host system. That design means k0s can’t use glibc’s NSS APIs, which require dynamic linking.
This limitation is particularly relevant when a system uses NSS plugins,
such as nss-myhostname,
for resolving network names like localhost.
If your system lacks a dedicated stub resolver that handles localhost DNS queries, k0s encounters issues.
To avoid these issues, activate a stub DNS resolver, such as systemd-resolved, or add localhost entries to the /etc/hosts file:
127.0.0.1 localhost
::1 localhost
External software dependencies
k0s requires the following external tools.
mount/umount
When kubelet sets up pods, it calls the mount binary on the host.
When kubelet destroys pods, it calls umount.
mount and umount are only needed on worker nodes where kubelet runs.
k0s may also use the following external tools in specific circumstances.
containerd and AppArmor
To use containerd with AppArmor, enable AppArmor in the kernel and install the
/sbin/apparmor_parser executable on the host.
Otherwise, containerd disables AppArmor support.
iptables
k0s may run iptables to check for existing rules and determine whether it uses
legacy or nft mode.
If iptables isn’t found, k0s assumes that no existing rules exist.
useradd / adduser
During k0s install, k0s uses the external tool useradd on controllers to
create system user accounts.
If useradd doesn’t exist, k0s falls back to BusyBox’s adduser.
userdel / deluser
k0s reset runs either userdel or deluser to clean up system user
accounts.
modprobe
On k0s worker nodes, k0s executes modprobe to load missing kernel modules.
id
k0s runs the external /usr/bin/id command as a fallback if local user lookup
fails and the host uses NSS.