By dropping support for setting up k3s 1.20 to 1.23, we can make notable simplifications to this action. If someone needs to test k8s 1.23 still, they can still fall back on v3 of this action - as we would now release v4 with this merged as breaking.
Maintaining support for k8s 1.23 still is quite extreme, as k8s 1.24 in end of january no longer supported by GKE, EKS, or AKS for example, and k8s 1.29 is out.
PR 3/5 from #93 that was broken apart.
By dropping support for setting up k3s 1.20 to 1.23, we can make notable simplifications to this action. If someone needs to test k8s 1.23 still, they can still fall back on v3 of this action - as we would now release v4 with this merged as breaking.
Maintaining support for k8s 1.23 still is quite extreme, as k8s 1.24 in end of january no longer supported by GKE, EKS, or AKS for example, and k8s 1.29 is out.