Image Tag Mismatch between k8s.gcr.io/guestbook:v3 and registry.k8s.io/guestbook:v3
highb opened this issue · comments
When the image tag was switched over to the new registry.k8s.io container registry, it appears that the actual tags didn't get copied over quite right. When I deploy the registry.k8s.io/guestbook:v3 image to my cluster, the front-end fails because it attempts to look up redis-slave and gets no such host when the manifests are configured to set up the service as redis-replica. This leads me to believe that a new version of the go guestbook needs to be pushed and then the tags in the manifests need to be updated.
Related commit:
538d302
I checked the 2 images digest are identical.
➜ ~ docker pull k8s.gcr.io/guestbook:v3
v3: Pulling from guestbook
...
Digest: sha256:8f333d5b72677d216b4eb046d655aef7be9f1380e06ca1c63dfa9564034e7e26
Status: Downloaded newer image for k8s.gcr.io/guestbook:v3
k8s.gcr.io/guestbook:v3
➜ ~ registry.k8s.io/guestbook:v3
zsh: no such file or directory: registry.k8s.io/guestbook:v3
➜ ~ docker pull registry.k8s.io/guestbook:v3
v3: Pulling from guestbook
...
Digest: sha256:8f333d5b72677d216b4eb046d655aef7be9f1380e06ca1c63dfa9564034e7e26
Status: Downloaded newer image for registry.k8s.io/guestbook:v3
registry.k8s.io/guestbook:v3
I also verified and there is no issue present in this, both the image digests are same in below.
/triage needs-information