rancher / rancher

Complete container management platform
http://rancher.com
Apache License 2.0
23.22k stars 2.94k forks source link

Auto Replace does not work (v2.5.1 on rke) #29754

Closed Negashev closed 3 years ago

Negashev commented 3 years ago

What kind of request is this (question/bug/enhancement/feature request): bug

Steps to reproduce (least amount of steps as possible):

1) install k8s by rke 1.2.1 on one node 2) install rancher 2.5.1 by helm 3) create cluster with hetzner node driver 4) add pool with auto replace node after 1-10 minutes 5) go to hetzner console and stop on node from pool (with auto replace)

Result: Rancher see that kubelet stop, but nothing happend with node in next 30+ minutes

Other details that may be helpful:

I have only one node with k8s for rancher and test cluster with one node for etcd and control panel, and 2 nodes (node pool with auto-replace)

Environment information

Cluster information

v1.19.3

sowmyav27 commented 3 years ago

On 2.4.8

On 2.5.1

mrajashree commented 3 years ago

This happens only on k8s 1.19 clusters, because the node doesn't get the taint node.kubernetes.io/unreachable:NoExecute Could be related to https://github.com/kubernetes/kubernetes/issues/94183 Although that bug description has k8s 1.18.6 as the version, whereas it does work on k8s 1.18.10

sowmyav27 commented 3 years ago

On 2.5-head commit id: a90aa3ca and master-head commit id: b7e8c0d3