Calico Open Source 3.33 (latest) documentation
calicoctl node checksystem
This section describes the calicoctl node checksystem command.
Read the calicoctl Overview for a full list of calicoctl commands.
Displaying the help text for 'calicoctl node checksystem' command
Run calicoctl node checksystem --help to display the following help menu for the
command.
Verify that this host meets the system requirements to run a Calico node instance.
Usage:
calicoctl node checksystem [flags]
Examples:
calicoctl node checksystem
Flags:
-h, --help help for checksystem
-f, --kernel-config string Override the Kernel config file location.
Global Flags:
--allow-version-mismatch Allow client and cluster versions mismatch
--context string The name of the kubeconfig context to use
-l, --log-level string Set the log level (panic, fatal, error, warn, info, debug) (default "panic")
Procedure
These are the steps that calicoctl takes to pinpoint what modules are available in your system.
calicoctlchecks the kernel version.- By executing
lsmodit tries to find out what modules are enabled. - Modules without a match in step 2 will be checked against
/lib/modules/<YOUR_KERNEL_VERSION>/modules.depfile. - Modules without a match in step 2 & 3 will be checked against
/lib/modules/<YOUR_KERNEL_VERSION>/modules.builtinfile. - Modules without a match in previous steps will be tested against
kernelconfigfile/usr/src/linux/.config. - Any remaining module will be tested against loaded iptables modules in
/proc/net/ip_tables_matches.
Examples
calicoctl node checksystem
An example response follows.
xt_conntrack OK
xt_u32 OK
WARNING: Unable to detect the xt_set module. Load with `modprobe xt_set`
WARNING: Unable to detect the ipip module. Load with `modprobe ipip`
It is possible to override the kernel-config file using --kernel-config argument. In this case calicoctl will try to resolve the modules against the provided file and skip the default locations.
calicoctl node checksystem --kernel-config /root/MYKERNELFILE