mirror of https://github.com/k3s-io/k3s
![]() RequiredIPVSKernelModulesAvailable warning confuses users suggesting that the IPVS proxier will not be used, which is not always the case. Made the warning message less confusing: [WARNING RequiredIPVSKernelModulesAvailable]: The IPVS proxier may not be used because the following required kernel modules are not loaded: [ip_vs_rr ip_vs_wrr ip_vs_sh] or no builtin kernel ipvs support was found: map[ip_vs_wrr:{} ip_vs_sh:{} nf_conntrack_ipv4:{} ip_vs:{} ip_vs_rr:{}]. However, these modules may be loaded automatically by kube-proxy for you if they are available on your system. To verify IPVS support: Run "lsmod | grep 'ip_vs\|nf_conntrack'" and verify each of the above modules are listed. If they are not listed, you can use the following methods to load them: 1. For each missing module run 'modprobe $modulename' (e.g., 'modprobe ip_vs', 'modprobe ip_vs_rr', ...) 2. If 'modprobe $modulename' returns an error, you will need to install the missing module support for your kernel. Fixes: kubernetes/kubeadm#975 |
||
---|---|---|
.. | ||
api | ||
apis | ||
auth | ||
capabilities | ||
client | ||
cloudprovider | ||
controller | ||
credentialprovider | ||
features | ||
fieldpath | ||
generated | ||
kubeapiserver | ||
kubectl | ||
kubelet | ||
kubemark | ||
master | ||
printers | ||
probe | ||
proxy | ||
quota | ||
registry | ||
routes | ||
scheduler | ||
security | ||
securitycontext | ||
serviceaccount | ||
ssh | ||
util | ||
version | ||
volume | ||
watch/json | ||
windows/service | ||
.import-restrictions | ||
BUILD | ||
OWNERS |