You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I try to create a vcluster with --kubernetes-version 1.27 in a host cluster running K8s 1.30.4, the --kubernetes-version 1.27 flag seems ignored. Nothing is shown in the logs either. The final vcluster k8s version ends up as 1.30.4.
What did you expect to happen?
This was working fine on 0.20. I was expecting it to work the same?
How can we reproduce it (as minimally and precisely as possible)?
$ k3d cluster create # right now it creates a 1.30.4 cluster
$ vcluster create --kubernetes-version 1.27 felipe17:02:45 info Creating namespace vcluster-felipe17:02:45 info Chart not embedded: "open chart/vcluster-0.21.1.tgz: file does not exist", pulling from helm repository.17:02:45 info Create vcluster felipe...17:02:45 info execute command: helm upgrade felipe https://charts.loft.sh/charts/vcluster-0.21.1.tgz --create-namespace --kubeconfig /tmp/899677600 --namespace vcluster-felipe --install --repository-config='' --values /tmp/314540931117:02:47 done Successfully created virtual cluster felipe in namespace vcluster-felipe17:02:55 info Waiting for vcluster to come up...17:03:04 info vcluster is waiting, because vcluster pod felipe-0 has status: Init:1/317:03:14 info vcluster is waiting, because vcluster pod felipe-0 has status: Init:2/317:03:34 done vCluster is up and running17:03:34 info Starting background proxy container...17:03:46 done Switched active kube context to vcluster_felipe_vcluster-felipe_k3d-k3s-default- Use `vcluster disconnect` to return to your previous kube context- Use `kubectl get namespaces` to access the vcluster
$ vcluster connect felipe -- kubectl version17:05:08 done vCluster is up and runningClient Version: v1.31.3Kustomize Version: v5.4.2Server Version: v1.30.4
What happened?
If I try to create a vcluster with
--kubernetes-version 1.27
in a host cluster running K8s1.30.4
, the--kubernetes-version 1.27
flag seems ignored. Nothing is shown in the logs either. The final vcluster k8s version ends up as1.30.4
.What did you expect to happen?
This was working fine on 0.20. I was expecting it to work the same?
How can we reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
No response
Host cluster Kubernetes version
vcluster version
VCluster Config
N/A
The text was updated successfully, but these errors were encountered: