This message was deleted.

no, there is no component downgrade scenario that is supported by upstream Kubernetes. If you want to go back to an old version, you should plan on stopping all nodes in the cluster, downgrading all the k3s binaries, restoring a datastore snapshot taken on that version, and then starting the nodes again. It may (and for very basic patch-level changes probably will) work if you just downgrade the binary and restart, but it’s not supported.

I was trying downgrade from

1.22.8

to

1.20.7

and looks like i broke the cluster (test) and the error is -

Nov 21 10:08:40 test-ins k3s[7171]: time="2022-11-21T10:08:40.368627334Z" level=info msg="Cluster-Http-Server 2022/11/21 10:08:40 http: TLS handshake error from 10.0.0.142:44274: write tcp 10.0.7.88:6443->10.0.0.142:...rite: broken pipe"

yeah… downgrade across two minors and not just a patch release is very unlikely to work right

is it possible to fix it in anyway?

You’re welcome to try, but it’s not something I’ve ever done personally. Kubernetes doesn’t really do downgrades. Why are you trying to do that?