-
Notifications
You must be signed in to change notification settings - Fork 93
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
DEVEXP-424: Leveraging node pull secrets during image stream import #64
DEVEXP-424: Leveraging node pull secrets during image stream import #64
Conversation
/assign @dmage @adambkaplan |
/assign @mfojtik |
/hold Need to come to an agreement on the mount location, then ensure we set it correctly in openshift/cluster-openshift-apiserver-operator#284 |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ricardomaraschini The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/unhold @adambkaplan once we came up with an agreement related to the path to use I am removing the hold on this one. openshift/enhancements#136 and openshift/cluster-openshift-apiserver-operator#284 were updated accordingly. |
/unhold |
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.
@ricardomaraschini if I read this PR correctly, we don't explicitly need the openshift-apiserver-operator PR to merge first. As-is this PR will simply not find the node pull secret.
Pretty much yes, you are correct. |
/retest |
/test e2e-cmd |
/retest |
/retitle DEVEXP-424: Leveraging node pull secrets during image stream import |
/hold As this missed the feature freeze cutoff, we'll need to sit on this PR until 4.5 opens up |
/unhold 4.5 is open |
/hold preparing another version of this one. |
A new refactor version of this PR has been opened at #83, closing this one. |
With this PR we start to use node's pull secrets during image stream import process as described on the enhancement proposal. We prioritize namespace secrets over node pull secrets.