kubernetes version changed when stop/start Colima

[prune998]

Description

Reproducing:

• start colima with a specific k8s version using colima start --edit and set version to v1.25.0-rc1+k3s1 or colima start --kubernetes-version v1.25.0-rc1+k3s1
• Validate the version in the config file:

grep "  version"  ~/.colima/default/colima.yaml
  version: v1.25.0-rc1+k3s1

k version
...
Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.0-rc1+k3s1", ...

• stop colima with colima stop
• restart colima without any change to the config with colima start
• version is changed to default v1.23.6+k3s1 you can see this in the logs:

❯ colima start
INFO[0000] starting colima
INFO[0000] runtime: containerd+k3s
INFO[0000] preparing network ...                         context=vm
INFO[0000] starting ...                                  context=vm
INFO[0030] provisioning ...                              context=containerd
INFO[0030] starting ...                                  context=containerd
INFO[0036] provisioning ...                              context=kubernetes
INFO[0036] version changed to v1.23.6+k3s1, downloading and installing ...  context=kubernetes  <-----------
INFO[0048] loading oci images ...                        context=kubernetes
INFO[0056] starting ...                                  context=kubernetes
INFO[0068] done

❯ grep "  version"  ~/.colima/default/colima.yaml
  version: v1.23.6+k3s1

Version

Colima Version:

❯ colima version
colima version 0.4.4
git commit: 8bb1101a861a8b6d2ef6e16aca97a835f65c4f8f

runtime: containerd
arch: x86_64
client: v0.20.0
server: v1.5.8

kubernetes
Client Version: v1.25.0
Kustomize Version: v4.5.7
Server Version: v1.23.6+k3s1

Lima Version:

❯ limactl -v
limactl version 0.11.3

Qemu Version: na

Operating System

• [X] macOS Intel
• [ ] macOS M1
• [ ] Linux

Reproduction Steps

colima start --kubernetes-version v1.25.0-rc1+k3s1
INFO[0000] starting colima
INFO[0000] runtime: containerd+k3s
INFO[0000] preparing network ...                         context=vm
INFO[0000] starting ...                                  context=vm
INFO[0030] provisioning ...                              context=containerd
INFO[0030] starting ...                                  context=containerd
INFO[0036] provisioning ...                              context=kubernetes
INFO[0036] downloading and installing ...                context=kubernetes
INFO[0047] loading oci images ...                        context=kubernetes
INFO[0055] starting ...                                  context=kubernetes
INFO[0061] updating config ...                           context=kubernetes
INFO[0062] Switched to context "colima".                 context=kubernetes
INFO[0062] done


grep "  version"  ~/.colima/default/colima.yaml
  version: v1.25.0-rc1+k3s1

colima stop
INFO[0000] stopping colima
INFO[0000] stopping ...                                  context=kubernetes
INFO[0001] stopping ...                                  context=containerd
INFO[0003] stopping ...                                  context=vm
INFO[0007] done


colima start
INFO[0000] starting colima
INFO[0000] runtime: containerd+k3s
INFO[0000] preparing network ...                         context=vm
INFO[0000] starting ...                                  context=vm
INFO[0030] provisioning ...                              context=containerd
INFO[0030] starting ...                                  context=containerd
INFO[0036] provisioning ...                              context=kubernetes
INFO[0036] version changed to v1.23.6+k3s1, downloading and installing ...  context=kubernetes
INFO[0048] loading oci images ...                        context=kubernetes
INFO[0057] starting ...                                  context=kubernetes
INFO[0063] done


grep "  version"  ~/.colima/default/colima.yaml
  version: v1.23.6+k3s1

Expected behaviour

I would expect the K8s version to stay the same after a stop/start I would expect that Colima will not change the default profile after its creation and editing

Additional context

No response