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
What happened?
I upgraded the aws-ebs-csi-driver to latest version i.e. v1.32.0 and a couple of containers went into err due to missing images
What you expected to happen?
All the pods to work as expected
How to reproduce it (as minimally and precisely as possible)?
gcr overlay defines the image tag for livenessprobe as v2.13.0 here
docker pull registry.k8s.io/sig-storage/livenessprobe:v2.13.0
Error response from daemon: manifest for registry.k8s.io/sig-storage/livenessprobe:v2.13.0 not found: manifest unknown: Failed to fetch "v2.13.0"
The image 2.13.1 is a valid image and can be pulled.
docker pull registry.k8s.io/sig-storage/livenessprobe:v2.13.1
v2.13.1: Pulling from sig-storage/livenessprobe
Digest: sha256:d2a9027a4876e039185e9bef7c61a0142c8ea14e7440860285c34ac73fee4ffb
Status: Image is up to date for registry.k8s.io/sig-storage/livenessprobe:v2.13.1
registry.k8s.io/sig-storage/livenessprobe:v2.13.1
Similarly, gcr overlay defines the image tag for csi-node-driver-registrar as v2.11.0
docker pull registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.11.0
Error response from daemon: manifest for registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.11.0 not found: manifest unknown: Failed to fetch "v2.11.0"
The image v2.11.1 is a valid image and can be pulled.
docker pull registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.11.1
v2.11.1: Pulling from sig-storage/csi-node-driver-registrar
Digest: sha256:e01facb9fb9cffaf52d0053bdb979fbd8c505c8e411939a6e026dd061a6b4fbe
Status: Image is up to date for registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.11.1
registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.11.1
Anything else we need to know?:
Environment
Kubernetes version (use kubectl version):
Driver version: v1.32.0
The text was updated successfully, but these errors were encountered:
/kind bug
What happened?
I upgraded the aws-ebs-csi-driver to latest version i.e. v1.32.0 and a couple of containers went into err due to missing images
What you expected to happen?
All the pods to work as expected
How to reproduce it (as minimally and precisely as possible)?
gcr overlay defines the image tag for livenessprobe as v2.13.0 here
which corresponds to this note - https://github.com/kubernetes-csi/livenessprobe/releases/tag/v2.13.0
The image 2.13.1 is a valid image and can be pulled.
Similarly, gcr overlay defines the image tag for csi-node-driver-registrar as v2.11.0
which corresponds to this note - https://github.com/kubernetes-csi/node-driver-registrar/releases/tag/v2.11.0
The image v2.11.1 is a valid image and can be pulled.
Anything else we need to know?:
Environment
kubectl version
):The text was updated successfully, but these errors were encountered: