Open everflux opened 1 year ago
Thank you for reporting this. I am going to update the provider and release a new version soon.
P.S: this should have been reported in the CAPI provider repo - loft-sh/cluster-api-provider-vcluster, but we can leave it here this time.
@matskiv is something blocking the release, anything that can be contributed?
I didn't get to release this due to other priorities at the time, and right now I don't work on this project so I don't have any updates I can provide.
@everflux Could you test using the latest release v0.2.0-alpha.1
to see if this is fixed?
@deniseschannon How do I test the release v0.2.0-alpha.1
? I tried executing following commands, but I get the errors shown below.
clusterctl init --infrastructure=vcluster:v0.2.0-alpha.1
Fetching providers Error: invalid provider metadata: version v0.2.0-alpha.1 for the provider cluster-api-provider-vcluster-system/infrastructure-vcluster does not match any release series
clusterctl init --infrastructure=vcluster:v0.2.0
Fetching providers Error: failed to get provider components for the "vcluster:v0.2.0" provider: failed to read "infrastructure-components.yaml" from provider's repository "infrastructure-vcluster": release not found for version v0.2.0, please retry later or set "GOPROXY=off" to get the current stable release: 404 Not Found
clusterctl init --infrastructure=vcluster:v0.2.0-alpha.1
@nathanielkeeler Your first command clusterctl init --infrastructure=vcluster:v0.2.0-alpha.1
was absolutely correct. The current minor version bump to 0.2 was not reflected in the attached metadata.yaml file. So clusterctl could not find a suiting match for the given version. Can you please try again.
UPDATE: We recently released v0.2.0-alpha.2, which contains an important bug fix. Feel free to use that.
What happened?
Creating a cluster with kubernetes version 1.26 results in cluster version 1.24.
Input
Log snippet
What did you expect to happen?
vcluster uses 1.26
How can we reproduce it (as minimally and precisely as possible)?
Create a cluster with version 1.26
Anything else we need to know?
The cluster was using vcluster 0.13.1 and was upgraded later.
clusterctl version clusterctl version: &version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.5", GitCommit:"58770484dee6c99c10e32c06652e9f9643f78e9e", GitTreeState:"clean", BuildDate:"2023-03-02T15:57:13Z", GoVersion:"go1.19.6", Compiler:"gc", Platform:"linux/amd64"}
The vcluster controller pod uses the following images
docker.io/loftsh/cluster-api-provider-vcluster:0.1.3 gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0
There is no newer image on dockerhub https://hub.docker.com/r/loftsh/cluster-api-provider-vcluster/tags
Host cluster Kubernetes version
Host cluster Kubernetes distribution
vlcuster version
Vcluster Kubernetes distribution(k3s(default)), k8s, k0s)
OS and Arch