e2e: Use fully qualified image name for images#1472
e2e: Use fully qualified image name for images#1472RamLavi wants to merge 3 commits intok8snetworkplumbingwg:masterfrom
Conversation
Summary of ChangesHello @RamLavi, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses a compatibility issue with newer Kubernetes environments running CRI-O 1.34+ by updating an image reference in an end-to-end test template. The modification ensures that images are pulled successfully by providing their fully qualified names, thereby preventing test failures related to CRI-O's stricter image name resolution policy. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request correctly resolves an image pull failure on newer Kubernetes clusters by using a fully qualified image name for Alpine. This is a necessary and well-executed change. I have one suggestion to further improve the stability of the e2e tests by pinning the Alpine image to a specific version, which is a recommended best practice to ensure reproducible builds.
| containers: | ||
| - name: install-cni-plugins | ||
| image: alpine | ||
| image: docker.io/library/alpine |
There was a problem hiding this comment.
For better reproducibility and to avoid unexpected changes, it's recommended to pin the Docker image to a specific version tag instead of relying on the implicit :latest tag. This ensures that the e2e tests always use the same version of the Alpine image, preventing potential failures due to upstream changes in the image.
image: docker.io/library/alpine:3.20
fdb3d73 to
1c4b0b7
Compare
CRI-O 1.34+ enforces short name mode by default, which refuses to pull images with unqualified names like 'alpine' because they are ambiguous. Use a full image docker.io/library/alpine Fixes k8snetworkplumbingwg#1471 Signed-off-by: Ram Lavi <ralavi@redhat.com>
CRI-O 1.34+ enforces short name mode by default, which refuses to pull images with unqualified names like 'centos:8' because they are ambiguous. Use the full image quay.io/centos/centos:8 Fixes k8snetworkplumbingwg#1471 Signed-off-by: Ram Lavi <ralavi@redhat.com>
CRI-O 1.34+ enforces short name mode by default, which refuses to pull images with unqualified names like 'ubuntu:22.04' because they are ambiguous. Use the full image docker.io/library/ubuntu:22.04 Fixes k8snetworkplumbingwg#1471 Signed-off-by: Ram Lavi <ralavi@redhat.com>
1c4b0b7 to
ed71f70
Compare
CRI-O 1.34+ enforces short name mode by default, which refuses to pull images with unqualified names like 'alpine/centos:8/ubuntu' because they are ambiguous.
This PR changes the use short name image to the fully qualified images, in order to fix image pull failures on Kubernetes 1.34+ clusters.
Fixes: #1471