We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
/kind bug
What happened: We use an older version of the vsphere-csi driver, i.e. 2.7.0 The image in the corresponding manifest is no longer available: https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/v2.7.0/manifests/vanilla/vsphere-csi-driver.yaml#L270
gcr.io/cloud-provider-vsphere/csi/release/driver:v2.7.0
I know that the registry has moved to registry.k8s.io, but there's really no reference for that version.
The new driver registry path is:
registry.k8s.io/csi-vsphere/driver:v3.3.1
I've tried various possible registry paths for version 2.7.0, but nothing works.
What you expected to happen: Please update the manifests accordingly.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happened:
We use an older version of the vsphere-csi driver, i.e. 2.7.0
The image in the corresponding manifest is no longer available: https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/v2.7.0/manifests/vanilla/vsphere-csi-driver.yaml#L270
I know that the registry has moved to registry.k8s.io, but there's really no reference for that version.
The new driver registry path is:
I've tried various possible registry paths for version 2.7.0, but nothing works.
What you expected to happen:
Please update the manifests accordingly.
The text was updated successfully, but these errors were encountered: