^{Originally posted by jwenjian December 28, 2022}
I am confused about the instance manager pod behavior of node taint, hope anyone can help :)

I have a single node cluster with longhorn installed, then I add a new taint to the node, e.g. k=v:NoSchedule,then I delete the instance manager pod, based on my understanding, the new instance manager pod cannot be scheduled since it has no corresponding toleration.

But the new pod is scheduled and running normally, just like before.

I tried to delete the longhorn ui pod, the new UI pod is in pending status and cannot be scheduled to the node, which is expected.

Is there any other dark tech for the instance manager pods?

BTW, when I describe the instance manager pod, I just found 2 tolerations, none of them is for the new taint:

QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type    Reason   Age   From     Message
  ----    ------   ----  ----     -------
  Normal  Pulled   54m   kubelet  Container image "longhornio/longhorn-instance-manager:v1_20211210" already present on machine
  Normal  Created  54m   kubelet  Created container replica-manager
  Normal  Started  54m   kubelet  Started container replica-manager