-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Use imageutils instead of hardcoded image paths #81093
Use imageutils instead of hardcoded image paths #81093
Conversation
test/utils/image/manifest.go
Outdated
@@ -65,6 +67,7 @@ func initReg() RegistryList { | |||
registry := RegistryList{ | |||
GcAuthenticatedRegistry: "gcr.io/authenticated-image-pulling", | |||
DockerLibraryRegistry: "docker.io/library", | |||
DockerHumbleC: "docker.io/humblec", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@humblec can you point us to a public registry where we can pull the gluster provisioner image from?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msau42 @johnSchnake while developing the e2e I was trying to use gcr
or some other common repo where we host of our images, but somehow I didnt get the push access. Is there a common repo path where I can push this image ? If yes, please share it, so thatI can move or copy this container to that common path and update it via PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@spiffxp Could you comment on the issue above?
I'm not sure really where the image comes from, but I would assume he needs to put any code to build the image into test/images
then just ask someone in to bulid/push it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/hold
we cannot be adding personal repos!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@humblec why not say https://hub.docker.com/u/gluster ? (in other words, why should it be in the k8s gcr repo?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All the external-provisioners developed under kubernetes-incubator/external-storage are using quay.io/external-storage to store their images. I think that is the most obvious place to put the gluster image
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msau42 working with Jan and Brad on this , Hopefully this will be sorted out soon.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msau42 @johnSchnake @dims Discussed with @childsb and as per him, it is better to host it under gluster
org in docker hub. I have moved the image to gluster
org and updated the code by #82115.
/assign @humblec |
5c0444c
to
430e092
Compare
/retest |
I'm confused by the failure in the gce-csi run; it has failed multiple times in the same way so it seems like either the a 3rd party item isn't working, test-infra has an issue, or my change somehow caused the breakage. However, it shows that tests pass and then the scripts fail to move logs around and then
If anyone has an idea/lead on this I'd appreciate it. |
I have another PR for something completely different with the same error (for gce-csi) so I think it is a test-infra issue of some sort. Going to do some searching in slack and such to see if this is a known issue. |
/test pull-kubernetes-e2e-gce-csi-serial |
/retest |
430e092
to
ce88b4a
Compare
ce88b4a
to
e16940d
Compare
A number of tests were using hardcoded image paths instead of going through the imageutils package. The reason for centralizing the logic there is to keep an eye on what images we use and where they come from.
e16940d
to
2dab911
Compare
ping @dims @msau42 @johnSchnake |
@alejandrox1: Those labels are not set on the issue: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Just needs approved/lgtm now. Let me know if other changes are needed. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: johnSchnake, msau42 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Review the full test history for this PR. Silence the bot with an |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
A number of tests were using hardcoded image paths instead of
going through the imageutils package. The reason for centralizing
the logic there is to keep an eye on what images we use and where
they come from.
Which issue(s) this PR fixes:
Fixes #76617
Special notes for your reviewer:
Found one hardcoded variable here that was duplicating a registry that was already specified elsewhere. This would lead to 2 of the packages pulling from their own, hardcoded location instead of respecting the user overrides if provided.
In addition, there seemed to be one image being pulled from someone's ( @humblec ) private docker registry. This seems like an issue to me and should be remedied in its own PR; the point of this PR was just to centralize the image/registry lists.
@humblec maybe you can comment on why it is using that image instead of being integrated into the k8s registries?
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig testing
/priority important-soon
/area e2e-test-framework