search

kubernetes-sigs / vsphere-csi-driver

vSphere storage Container Storage Interface (CSI) plugin
https://docs.vmware.com/en/VMware-vSphere-Container-Storage-Plug-in/index.html
Apache License 2.0
295 stars 177 forks source link

Release-3.3 branch images unavailable, GCR repo deleted while master branch uses different repos #3054

Open devopsInterviews opened 2 days ago

devopsInterviews commented 2 days ago

/kind bug

What happened:

On the release-3.3 branch, the images use: image: gcr.io/cloud-provider-vsphere/csi/release/syncer:v3.3.1

On the master branch, the images have changed.

When trying to pull from the release branch, the repo shows as deleted and the image cannot be downloaded.

What you expected to happen:

The images should be available to pull from the release branch.

How to reproduce it (as minimally and precisely as possible):

Attempt to pull the release branch images.

Anything else we need to know?:

How is it possible for the release version to not work while the master has different repos?

Environment:

csi-vsphere version: v3.3.1 Kubernetes version: 1.30.4 vSphere version: 7.3 OS (e.g. from /etc/os-release): Ubuntu 24.04

embik commented 2 days ago

Related/same issue: #3053

devopsInterviews commented 2 days ago

Thanks @embik, I'll wait for an update

devopsInterviews commented 1 day ago

@embik Is there any update? Are you part of the vmware team? Or from a different project?

embik commented 1 day ago

@devopsInterviews hey, not affiliated, sorry for the confusion. I just wanted to create a reference to the other issue for visibility. We're also "just" consumers of the CSI driver, we don't have more information than what's on Slack / these two GitHub issues.

devopsInterviews commented 1 day ago

Thanks @embik Do you know if someone from the official maintainers is aware of this problem? By the way, I'll be glad to hear how did you manage to solve it from your side.

embik commented 1 day ago

@devopsInterviews I don't know if anyone is aware, sorry. We solved this problem for our users by publishing self-built versions of the images: https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/3053#issuecomment-2356689962

devopsInterviews commented 1 day ago

Thanks for the quick responses @embik ! One last question, how were you able to mirror the images if the repo has been deleted (or you had those images on your local endpoints?). Do you plan to upload more tags to there?

I saw on the master branch that there is this location now: us-central1-docker.pkg.dev/k8s-staging-images/csi-vsphere/ci/driver:latest

But it only consists the lastest if this somehow helps you (I don't know how there is a difference between the master branch and the release tags and who maintains it. Even more weird why no one says anything about this).

embik commented 1 day ago

As mentioned on that comment, these images are self-built, i.e. we checked out release tags from code and built the images.

bork91 commented 1 day ago

https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/3053#issuecomment-2358131718

devopsInterviews commented 1 day ago

Thanks @bork91, Unfortunately I need this for new clusters. Do you happen to know the maintainers of this repo?

devopsInterviews commented 17 hours ago

@divyenpatel It looks like you did some related commits, do you know to tell what happened to the legacy images? And what can we do to solve it?

aditya-tanwar commented 17 hours ago

unfortunately , even us-central1-docker.pkg.dev/k8s-staging-images/csi-vsphere/ci/driver:latest is showing not found while deploying

devopsInterviews commented 16 hours ago

@aditya-tanwar It seems you are right.. So there is no official location for the images now. Does anyone knows something?? We can not deploy new clusters!!

aditya-tanwar commented 15 hours ago

@aditya-tanwar It seems you are right..

So there is no official location for the images now.

Does anyone knows something?? We can not deploy new clusters!!

@devopsInterviews
What i did is basically updated the images showing errors with the mirrors located in quay.io

Refer to this -> https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/3053#issuecomment-2356689962

Here you fill find mirror links for the images that are not accessible for me syncer and driver containers were causing problem and i updated the images

As of now what you can do is from the repo pick up the vanilla manifest and update the syncer and driver images with quay.io ones as mentioned in the above link that way you will have a running deployment , till the time we wait for verified images from the owner/team

Darth-Weider commented 4 hours ago

unfortunately , even us-central1-docker.pkg.dev/k8s-staging-images/csi-vsphere/ci/driver:latest is showing not found while deploying

I think you need a GCP account to access the image.