I have a weird issue that has me puzzled. I upgraded a node to the newest release v0.20.4-k3s1r0. I did this by updating the upgrade plan yaml with the new tag and let upgrade controller do its thing. The node upgraded as expected and all was well, until this morning. Sometime last night the node reverted back to the v0.19.5-rc.1 release and came up cordoned. I uncordoned the node and the pods all started but it is definitely back on the v0.19.5-rc.1 release. The upgrade plan yaml is still showing the v0.20 tag and the plan itself (kubectl describe plan -n k3os-system k3os-latest) is also showing the v0.20 tag. Any ideas on what might be happening here?