Cannot pull registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.11.0 #415
Comments
|
Looking into this.. Atm, I don't see this tag in the artificatory, thus the image promotion also has not happened. |
|
/assign @humblec |
|
Microsoft has broken their base container images: microsoft/Windows-Containers#493 |
Below csi sidecars are updated with latest available versions csi-resizer: v1.11.1 csi-provisioner: v5.0.1 csi-attacher: v4.6.1 csi-snapshotter: v8.0.1 csi-node-driver-registrar: v2.10.1 (v2.11.0 is not yet available in registry due to kubernetes-csi/node-driver-registrar#415) Signed-off-by: Praveen M <[email protected]>
|
The underlying issue has still not been resolved so I understand that your build still will not be working. Since its been a month now is it worth pinning to a previous base image? I have seen several other projects doing this - for example https://github.com/jenkinsci/docker-ssh-agent/pull/433/files |
|
This seems to affect all OSes, not just Windows? Why not publish images for Linux? |
|
I can see from microsoft/Windows-Containers#493 that they fixed the issue, does this now mean the images can be released? :) |
|
@xing-yang do you know how to retrigger the image build for v2.11.0? or do we need another patch version(e.g. v2.11.1) to build image? liveness-probe:v2.13.0 has same image build issue. https://console.cloud.google.com/gcr/images/k8s-staging-sig-storage/global/csi-node-driver-registrar
|
|
Please pull |
|
similarly, a fixed livenessprobe is now available as |
|
@ThatsMrTalbot @andyzhangx @luhi-DT Can you please confirm that the new Windows images are working now? I have no way to test this. |
|
Sorry @jsafrane, I do not use the windows images. I just needed the linux ones to be pushed up. |
@jsafrane yes, the new windows images work well, I have a image version upgrade PR which triggers the windows e2e tests, test pass: kubernetes-csi/csi-driver-smb#796 |
When attempting to pull the image for the new v2.11.0 I get the following:
The text was updated successfully, but these errors were encountered: