Tolerations: k edit command, and unexpected toleration in k describe

Kubernetes
#1

(1) In Taints and Tolerations lab, I created pod bee first. Then I I used k edit command to input the tolerance specification. I ran :wq! after the changes, but got message edit cancelled, no changes made. Is this because pods, once created, cannot be updated/modified? They have to be deleted and then deployed again with updated config?

Once I was able to succesfully deploy bee on node-01, k describe pod showed tolerations as “node.kubernetes.io/not-ready:NoExecute op=Exists” and node.kubernetes.io/unreachable:NoExecute op=Exists"; I do not see the tolerations I had specified in the yml file when creating the pod. Any ideas why would that be? The correct tolerance is there for sure, else the pod would not have deployed on node-01:

controlplane ~ :heavy_multiplication_x: k get pods -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
bee 1/1 Running 0 8m16s 172.17.1.7 node01

#2

Yep. Almost nothing in a pod can be edited once it’s created.

As for the additional tolerations: some are added automatically to prevent pods from being reaped or shutdown too quickly. This is a relatively recent changer to how things work.