Thanks again! Jeffrey. I have submit the SRU request: https://lists.ubuntu.com/archives/kernel-team/2019-August/103191.html
** Description changed: + == SRU Justification == + VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes, + it will be great to enable the support in KVM kernels. + + == Fix == + Enable the CONFIG_VXLAN in the config file. + CONFIG_NET_UDP_TUNNEL=m and other configs were added automatically with + updateconfigs. + + CONFIG_OPENVSWITCH_VXLAN supprt was excluded intentionally as this is + not requested (and to reduce the binary size). + + == Test == + Test kernels could be found here: + https://people.canonical.com/~phlin/kernel/lp-1811819-vxlan/ + + Kernel smoke tested. + User has also verified that all the patched kernels are working as + expected. + + == Regression Potentail == + Low, this enables the support for VXLAN module on KVM kernels, we might + see some related bugs in the future. Since we already have this in the + generic kernel so the impact should be small. + + + == Original Bug Report == The kernel built with this packages does have VXLAN compiled. It would be nice if this could be fixed since VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes. $ grep -i vxlan /boot/config-4.4.0-1039-kvm # CONFIG_VXLAN is not set When running a kubernetes cluster with Flannel with this image: - $ kubectl logs kube-flannel-ds-amd64-jfkc8 -n kube-system --kubeconfig=case1-admin.conf + $ kubectl logs kube-flannel-ds-amd64-jfkc8 -n kube-system --kubeconfig=case1-admin.conf I0116 11:35:34.176962 1 main.go:475] Determining IP address of default interface I0116 11:35:34.177231 1 main.go:488] Using interface with name ens3 and address 10.32.192.14 I0116 11:35:34.177259 1 main.go:505] Defaulting external address to interface address (10.32.192.14) I0116 11:35:34.191358 1 kube.go:131] Waiting 10m0s for node controller to sync I0116 11:35:34.273844 1 kube.go:294] Starting kube subnet manager I0116 11:35:35.274075 1 kube.go:138] Node controller sync successful I0116 11:35:35.274106 1 main.go:235] Created subnet manager: Kubernetes Subnet Manager - node-1-case1 I0116 11:35:35.274113 1 main.go:238] Installing signal handlers I0116 11:35:35.274233 1 main.go:353] Found network config - Backend type: vxlan I0116 11:35:35.274292 1 vxlan.go:120] VXLAN config: VNI=1 Port=0 GBP=false DirectRouting=false E0116 11:35:35.275803 1 main.go:280] Error registering network: operation not supported I0116 11:35:35.275860 1 main.go:333] Stopping shutdownHandler... ** Changed in: linux-kvm (Ubuntu Bionic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-kvm (Ubuntu Disco) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-kvm (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu Disco) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1811819 Title: please include the kernel module VXLAN Status in linux-kvm package in Ubuntu: In Progress Status in linux-kvm source package in Xenial: In Progress Status in linux-kvm source package in Bionic: In Progress Status in linux-kvm source package in Disco: In Progress Bug description: == SRU Justification == VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes, it will be great to enable the support in KVM kernels. == Fix == Enable the CONFIG_VXLAN in the config file. CONFIG_NET_UDP_TUNNEL=m and other configs were added automatically with updateconfigs. CONFIG_OPENVSWITCH_VXLAN supprt was excluded intentionally as this is not requested (and to reduce the binary size). == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1811819-vxlan/ Kernel smoke tested. User has also verified that all the patched kernels are working as expected. == Regression Potentail == Low, this enables the support for VXLAN module on KVM kernels, we might see some related bugs in the future. Since we already have this in the generic kernel so the impact should be small. == Original Bug Report == The kernel built with this packages does have VXLAN compiled. It would be nice if this could be fixed since VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes. $ grep -i vxlan /boot/config-4.4.0-1039-kvm # CONFIG_VXLAN is not set When running a kubernetes cluster with Flannel with this image: $ kubectl logs kube-flannel-ds-amd64-jfkc8 -n kube-system --kubeconfig=case1-admin.conf I0116 11:35:34.176962 1 main.go:475] Determining IP address of default interface I0116 11:35:34.177231 1 main.go:488] Using interface with name ens3 and address 10.32.192.14 I0116 11:35:34.177259 1 main.go:505] Defaulting external address to interface address (10.32.192.14) I0116 11:35:34.191358 1 kube.go:131] Waiting 10m0s for node controller to sync I0116 11:35:34.273844 1 kube.go:294] Starting kube subnet manager I0116 11:35:35.274075 1 kube.go:138] Node controller sync successful I0116 11:35:35.274106 1 main.go:235] Created subnet manager: Kubernetes Subnet Manager - node-1-case1 I0116 11:35:35.274113 1 main.go:238] Installing signal handlers I0116 11:35:35.274233 1 main.go:353] Found network config - Backend type: vxlan I0116 11:35:35.274292 1 vxlan.go:120] VXLAN config: VNI=1 Port=0 GBP=false DirectRouting=false E0116 11:35:35.275803 1 main.go:280] Error registering network: operation not supported I0116 11:35:35.275860 1 main.go:333] Stopping shutdownHandler... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1811819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
