Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

livenessprobe and csi-node-driver-registrar image versions invalid in gcr overlay for v1.32.0 #2090

Closed
AbhilashaSGupta opened this issue Jul 19, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@AbhilashaSGupta
Copy link

/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

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"

which corresponds to this note - https://github.com/kubernetes-csi/livenessprobe/releases/tag/v2.13.0

Note: Microsoft has broken their base container images: microsoft/Windows-Containers#493
Use v2.13.1.

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"

which corresponds to this note - https://github.com/kubernetes-csi/node-driver-registrar/releases/tag/v2.11.0

Note: Microsoft has broken their base container images: microsoft/Windows-Containers#493
Use v2.11.1.

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
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jul 19, 2024
@torredil
Copy link
Member

/close Addressed by #2091

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants