Kubespray doesn't work for jetson xavier agx and nx

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
1

I am trying to create a kubernetes cluster with kubespray.
I have run it as per the document but I get the following error.
What should I do in this case?

TASK [kubernetes/node : Modprobe Kernel Module for IPVS] ***********************************************

changed: [node2] => (item=ip_vs)

changed: [node1] => (item=ip_vs)

changed: [node2] => (item=ip_vs_rr)

changed: [node1] => (item=ip_vs_rr)

failed: [node2] (item=ip_vs_wrr) => {"ansible_loop_var": "item", "changed": false, "item": "ip_vs_wrr", "msg": "modprobe: FATAL: Module ip_vs_wrr not found in directory /lib/modules/4.9.253-tegra\n", "name": "ip_vs_wrr", "params": "", "rc": 1, "state": "present", "stderr": "modprobe: FATAL: Module ip_vs_wrr not found in directory /lib/modules/4.9.253-tegra\n", "stderr_lines": ["modprobe: FATAL: Module ip_vs_wrr not found in directory /lib/modules/4.9.253-tegra"], "stdout": "", "stdout_lines": []}

failed: [node1] (item=ip_vs_wrr) => {"ansible_loop_var": "item", "changed": false, "item": "ip_vs_wrr", "msg": "modprobe: FATAL: Module ip_vs_wrr not found in directory /lib/modules/4.9.253-tegra\n", "name": "ip_vs_wrr", "params": "", "rc": 1, "state": "present", "stderr": "modprobe: FATAL: Module ip_vs_wrr not found in directory /lib/modules/4.9.253-tegra\n", "stderr_lines": ["modprobe: FATAL: Module ip_vs_wrr not found in directory /lib/modules/4.9.253-tegra"], "stdout": "", "stdout_lines": []}

failed: [node2] (item=ip_vs_sh) => {"ansible_loop_var": "item", "changed": false, "item": "ip_vs_sh", "msg": "modprobe: FATAL: Module ip_vs_sh not found in directory /lib/modules/4.9.253-tegra\n", "name": "ip_vs_sh", "params": "", "rc": 1, "state": "present", "stderr": "modprobe: FATAL: Module ip_vs_sh not found in directory /lib/modules/4.9.253-tegra\n", "stderr_lines": ["modprobe: FATAL: Module ip_vs_sh not found in directory /lib/modules/4.9.253-tegra"], "stdout": "", "stdout_lines": []}

failed: [node1] (item=ip_vs_sh) => {"ansible_loop_var": "item", "changed": false, "item": "ip_vs_sh", "msg": "modprobe: FATAL: Module ip_vs_sh not found in directory /lib/modules/4.9.253-tegra\n", "name": "ip_vs_sh", "params": "", "rc": 1, "state": "present", "stderr": "modprobe: FATAL: Module ip_vs_sh not found in directory /lib/modules/4.9.253-tegra\n", "stderr_lines": ["modprobe: FATAL: Module ip_vs_sh not found in directory /lib/modules/4.9.253-tegra"], "stdout": "", "stdout_lines": []}

■executed command

ansible-playbook -i inventory/mycluster/hosts.yml --become --become-user=root cluster.yml -u ubuntu -kK

■document
https://docs.nvidia.com/networking/m/view-rendered-page.action?abstractPageId=19818992

3

Hi,

Could you check if Kubespray support Jetson (aarch64) environment first?
Thanks.

4

Thank you for your reply.

There is no official mention of this.
There is a kernel driver for ipvs on linux, but ip_vs_wrr is not provided.
It may needs a kernel build.
It seems to be related to tegra.

5

Hi,

Thanks for your information.

We try to reproduce this issue internally.
Could you share which JetPack version do you use?

Thanks.

6

Thank you very much.
Below is the version of Jetpack.

sudo apt show nvidia-jetpack
...
Package: nvidia-jetpack
Version: 4.6.2-b5
Priority: standard
Section: metapackages
7

Hi,

Sorry that some information wants to confirm further.
Do you have a Mellanox card connected, which is the requirement in the hardware spec:

  • Hardware
    All servers used during deployment have the same hardware specification and equipped with a Mellanox ConnectX network card.

Thanks.

8

Sorry.
I do not have a Mellanox ConnectX network card.
The network card I am using is the standard internal one.
I am connected via wi-fi.

9

Hi,

Sorry that the document is tested under the Mellanox ConnectX network card.
We don’t have too much experience on the use case as yous.

There is another related topic about Kubernetes.
Maybe you can check it to see if any idea.

Thanks.

10

Thank you very much.

12

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.