k3s icon indicating copy to clipboard operation
k3s copied to clipboard

Upgrading a k3s node with ipvs as kube-proxy-mode renders NodePort unreachable

Open CiraciNicolo opened this issue 3 years ago • 2 comments

Environmental Info: K3s Version: k3s version v1.22.5+k3s1 (405bf79d)

Node(s) CPU architecture, OS, and Version: Linux hostname 3.10.0-1160.49.1.el7.x86_64 #1 SMP Tue Nov 30 15:51:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Cluster Configuration: Single node

Describe the bug: Upgrading a k3s node with ipvs as kube-proxy-mode renders NodePort unreachable

Steps To Reproduce:

  • Installed K3s:
  • Use ipvs as proxy mode
  • Upgrade via UpgradController
  • NodePorts are unreachable with connection failed

Expected behavior: Upgrade a node should not render NodePort unreachable

Actual behavior: NodePort are unreachable

Fix Rebooting the node fixes the issue, using k3s-killall.sh or restarting k3s service DID NOT fix the issue. Is this a known issue?

CiraciNicolo avatar Jan 26 '22 19:01 CiraciNicolo

i have the same problem

vincentchivas avatar Jun 28 '22 02:06 vincentchivas

I suspect this is an upstream issue, or perhaps related to the host OS. We're not doing anything special with kube-proxy.

@vincentchivas are you also on EL7?

brandond avatar Jun 28 '22 23:06 brandond

same issue on ubuntu 22.04 and v1.22.2+k3s2

sigurdblueface avatar Nov 14 '22 15:11 sigurdblueface

I tested with an upgrade from k3s 1.25.6 to 1.26.1 and the NodePort was still reachable after the upgrade.

Command used to install k3s:

curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--disable traefik,metrics-server,--kube-proxy-arg=ipvs-scheduler=lc,proxy-mode=ipvs" sh -s -

thomasferrandiz avatar Feb 27 '23 10:02 thomasferrandiz

Closing, as we cannot reproduce with more recent versions

caroline-suse-rancher avatar Feb 28 '23 22:02 caroline-suse-rancher