What happened?

kubeadm reset does not delete the iptables/ipvs/ipset entries, created by kubeadm init. Part of the entries are created by kube-proxy and can be cleaned by kube-proxy --cleanup. Others are created by kubelet. See also kubernetes/kubeadm#2587 .

• add a method to kubelet to delete all iptables/ipvs/ipset entries created by it, so that kubeadm reset can revert the effect of kubeadm init.

Copy of kubernetes/kubelet#32.

What did you expect to happen?

kubelet shall have means to delete the iptables, it has created.

How can we reproduce it (as minimally and precisely as possible)?

.

Anything else we need to know?

No response

Kubernetes version

1.22

Cloud provider

Me

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)