This message was deleted.

Within RKE templates there's an option to allow a field to be overrideable. If the field is not overrideable when the template is created the field can't be changed within the cluster. You'll need to create a new template to allow this behavior.

Thanks, @wooden-engine-7388 The only option I had is to create a new revision from the previously created template (disabling the template did not help, why there is no delete option?). In the new revision, I allowed the version override as you have shown above. Then, in the cluster, I changed the template to use the new revision, and only then I could edit the Kubernetes version. This is a horrible UX in my opinion. Why can't I: 1. Delete the template? 2. Untick the "Use an existing RKE Template and revision" in the cluster config? So the cluster will be free from any created templates.

Both templates and template revisions can be deleted as long as they aren't being used for anything else (this includes being used as a default). Sorry you find it confusing but we don't want to delete resources that are being used by something else. These are supposed to be used across multiple clusters so we have to be careful with how the life cycles are managed. Your use case sounds like it would be better served by creating a cluster without an RKE Template. You can do this simply by not selecting a template when creating your cluster.