Public bug reported:

To use kube-router as part of a kubernetes install, it requires kernel
module CONFIG_NETFILTER_XT_SET build it makes use of the 'set' module in
iptables.

Otherwise, since this kernel module is not built as a module nor
included in the kernel itself, iptables complains:

root@prod-controller1:~# cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS"

root@prod-controller1:~# /sbin/iptables -t nat -A POSTROUTING -m set 
--match-set kube-router-pod-subnets src -m set ! --match-set 
kube-router-pod-subnets dst -m set ! --match-set kube-router-node-ips dst -j 
MASQUERADE --wait
iptables: No chain/target/match by that name.

root@prod-controller1:/boot# grep XT_SET config-$(uname -r)
# CONFIG_NETFILTER_XT_SET is not set


To fix this situation, I would kindly request that CONFIG_NETFILTER_XT_SET be 
incldued, at minimum, as a module in the kvm kernel.

Thanks,


Kube-router code that shows the iptables parameters using the 'set' module:
https://github.com/cloudnativelabs/kube-router/blob/00824cd84b862d73dbdf984477178cca9bce9166/pkg/controllers/routing/pod_egress.go#L13

** Affects: linux-kvm (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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/1843051

Title:
  please include kernel module CONFIG_NETFILTER_XT_SET

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  To use kube-router as part of a kubernetes install, it requires kernel
  module CONFIG_NETFILTER_XT_SET build it makes use of the 'set' module
  in iptables.

  Otherwise, since this kernel module is not built as a module nor
  included in the kernel itself, iptables complains:

  root@prod-controller1:~# cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS"

  root@prod-controller1:~# /sbin/iptables -t nat -A POSTROUTING -m set 
--match-set kube-router-pod-subnets src -m set ! --match-set 
kube-router-pod-subnets dst -m set ! --match-set kube-router-node-ips dst -j 
MASQUERADE --wait
  iptables: No chain/target/match by that name.

  root@prod-controller1:/boot# grep XT_SET config-$(uname -r)
  # CONFIG_NETFILTER_XT_SET is not set

  
  To fix this situation, I would kindly request that CONFIG_NETFILTER_XT_SET be 
incldued, at minimum, as a module in the kvm kernel.

  Thanks,

  
  Kube-router code that shows the iptables parameters using the 'set' module:
  
https://github.com/cloudnativelabs/kube-router/blob/00824cd84b862d73dbdf984477178cca9bce9166/pkg/controllers/routing/pod_egress.go#L13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1843051/+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

Reply via email to