You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using remove-node.yml to remove the node, I expect the node to revert to the state it was in when we initially installed it. However, static pods and DaemonSet pod containers are left on the node. When we try to reuse the node, I encounter a port already in use error with Nginx. We need to ssh into that node and kill the containerd-shim-v2 process to solve it.
What did you expect to happen?
The remove-node.yml should perform the same behavior as reset.yml.
Add a step to force all containers to stop.
How can we reproduce it (as minimally and precisely as possible)?
Use cluster.yml to install a cluster with nginx-proxy installed.
Use remove-node.yml to remove one of the worker nodes.
Then, use scale.yml to scale the same node back into the cluster.
What happened?
When using
remove-node.yml
to remove the node, I expect the node to revert to the state it was in when we initially installed it. However, static pods and DaemonSet pod containers are left on the node. When we try to reuse the node, I encounter aport already in use
error with Nginx. We need to ssh into that node and kill the containerd-shim-v2 process to solve it.What did you expect to happen?
The
remove-node.yml
should perform the same behavior asreset.yml
.Add a step to force all containers to stop.
How can we reproduce it (as minimally and precisely as possible)?
Use
cluster.yml
to install a cluster withnginx-proxy
installed.Use
remove-node.yml
to remove one of the worker nodes.Then, use
scale.yml
to scale the same node back into the cluster.OS
Version of Ansible
ansible [core 2.16.8]
Version of Python
Python 3.10.12
Version of Kubespray (commit)
7e0a407
Network plugin used
calico
Full inventory with variables
Command used to invoke ansible
See reproduce
Output of ansible run
Anything else we need to know
No response
The text was updated successfully, but these errors were encountered: