Restrict tigera-operator tolerations

Francois Eleouetrequested to merge
restrict-tigera-operator-tolerations into main

What does this MR do and why?

Restrict tigera-operator tolerations

They need to be restricted in order to prevent tigera-operator from being scheduled on a node that is being drained

During provisioning we have following taints on nodes:

taints:
  - effect: NoSchedule
    key: node.kubernetes.io/not-ready
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    timeAdded: "2024-07-02T15:02:58Z"

Whereas during upgrades we have:

    taints:
    - effect: NoSchedule
      key: node.kubernetes.io/unschedulable
      timeAdded: "2024-07-02T10:20:01Z"
    - effect: NoSchedule
      key: node.kubernetes.io/unreachable
      timeAdded: "2024-07-02T10:39:12Z"
    - effect: NoExecute
      key: node.kubernetes.io/unreachable
      timeAdded: "2024-07-02T10:39:18Z"

Adding the node.kubernetes.io/unreachable key to the default tolerations should prevent pods from being scheduled during node deletion.

Closes: #1414 (closed)

Merge request reports