I get the below errors during version upgrades
sudo kubeadm upgrade apply v1.29.0-1.1
[upgrade/versions] kubeadm version: v1.29.0
[upgrade/version] FATAL: the --version argument is invalid due to these errors:
- Specified version to upgrade to "v1.29.0-1.1" is an unstable version and such upgrades weren't allowed via setting the --allow-*-upgrades flags
Can be bypassed if you pass the --force flag
To see the stack trace of this error execute with --v=5 or higher
controlplane ~ 
sudo kubeadm upgrade apply v1.29.0-1.1 --force
[upgrade/config] Making sure the configuration is correct:
[upgrade/config] Reading configuration from the cluster…
[upgrade/config] FYI: You can look at this config file with ‘kubectl -n kube-system get cm kubeadm-config -o yaml’
[preflight] Running pre-flight checks.
[upgrade] Running cluster health checks
[upgrade/version] You have chosen to change the cluster version to “v1.29.0-1.1”
[upgrade/versions] Cluster version: v1.28.0
[upgrade/versions] kubeadm version: v1.29.0
[upgrade/version] Found 1 potential version compatibility errors but skipping since the --force flag is set:
- Specified version to upgrade to "v1.29.0-1.1" is an unstable version and such upgrades weren't allowed via setting the --allow-*-upgrades flags
[upgrade/prepull] Pulling images required for setting up a Kubernetes cluster
[upgrade/prepull] This might take a minute or two, depending on the speed of your internet connectiontime=“2024-03-05T03:33:23-05:00” level=fatal msg=“pulling image: rpc error: code = NotFound desc = failed to pull and unpack image "registry.k8s.io/kube-apiserver:v1.29.0-1.1": failed to resolve reference "registry.k8s.io/kube-apiserver:v1.29.0-1.1": registry.k8s.io/kube-apiserver:v1.29.0-1.1: not found”
.
.
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=...
To see the stack trace of this error execute with --v=5 or higher
Im unable to pull any of 1.29.0-1.1 images