If you have that strict requirements, after you figured out a solution for your problem, I suggest you start setting up internal mirrors and stop installing straight from the public internet, as to not encounter such problems in the future again. More on reddit.com

Just opened it at https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/ , and the kubeadm reference is at https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm/ More on reddit.com

You are assuming that kubeadm is part of an apt package and that therefore apt-get would know how to remove it. What if your assumption is false? Maybe start with finding out exactly where that kubeadm binary is sitting? which kubeadm This should spit out a path to that binary, maybe something like /usr/bin/kubeadm ... Then try and find out if it is even part of an apt package somewhere somehow: dpkg -S /usr/bin/kubeadm <== replace with the correct path you got from the command above. That command should spit out to which package /usr/bin/kubeadm (please use the correct path) belongs ... if it even belongs to any apt package at all. If it doesn't then dpkg will let you know and throw an error, e.g.: dpkg-query: no path found matching pattern /usr/bin/kubeadm If you get that error then you should check by what other possible means those packages could have been installed. Maybe "Kubernetes" was installed via snap packages?? Check e.g. snap list --all More on reddit.com

Beside the formatting being screwed up (line break are somehow lost): execute one command at a time. Don't do the next command when the previous one throws an error. And this particular gem: cat < More on reddit.com