Hi Everyone.. I have a question regarding upgrading our k3s setup from v1.34.1 to 1.35.5 we are following the standard setup process of upgrade where in we are stopping the k3s process, running the kill all command and then replacing the k3s binary to /usr/local/bin and k3s-airgap-images-amd64.tar /var/lib/rancher/k3s/agent/images/ but after we restart the k3s process back.. we are seeing that the k3s is coming back with the old version v1.34.1 only and not the upgraded version.. we have tried the upgrade with 1.34.8, 1.35.4 and 1.35.5 and all have come back with the same results.. any idea where we are going wrong? or what's that we need to do differently? We have followed the same approach for upgrade since last few times and has worked fine, but we are having this issues this time.. Can you please help with what can be done to get this cluster upgraded? Any help would be highly appreciated.. PLS HELP!!

There is nothing built in to k3s that will do what you are describing. Either you're replacing the wrong binary, or you have something else in place that is overwriting it again with the old version.

Where can i find whats overwriting it again with old version @creamy-pencil-82913

you’re going to have to figure that out on your own. I have no idea what you might be running that would be doing that.

We arent using rancher-provisioned nodes.. these are traditional linux nodes with k3s installed on them..