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

Add Dockerfile for proxy test image #2602

Merged
merged 1 commit into from Jun 19, 2021

Conversation

QiWang19
Copy link
Member

@QiWang19 QiWang19 commented Jun 4, 2021

This image will be added into the ocp-build-data(https://github.com/openshift/ocp-build-data)
repository. So product MCO(https://github.com/openshift/machine-config-operator) can
pull the image through a proxy that the customer configured to validate the proxy.

Ticket for the image build request: https://issues.redhat.com/browse/ART-2961

Signed-off-by: Qi Wang qiwan@redhat.com

- What I did

- How to verify it

- Description for the changelog

@kikisdeliveryservice
Copy link
Contributor

Is there any background for this? I have no real idea why this is being done.

cc: @rphillips do you have any details?

@@ -0,0 +1,2 @@
FROM registry.redhat.io/rhel7:latest
LABEL io.openshift.release.operator true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add a file into the image to say what this is being used for. This will also make the image hash unique.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a readme file under docs/, does this make sense?

@rphillips
Copy link
Contributor

@kikisdeliveryservice This is for the epic to test proxy access via the MCO. Qi will link the Jira for it.

@sinnykumari
Copy link
Contributor

LGTM, based on Jira card and README attached.
@QiWang19 By reading the card, it seems we need this PR in 4.9, is that correct?

@sinnykumari
Copy link
Contributor

/retest

@QiWang19
Copy link
Member Author

QiWang19 commented Jun 8, 2021

LGTM, based on Jira card and README attached.

@QiWang19 By reading the card, it seems we need this PR in 4.9, is that correct?

Yes, we need this for 4.9. This PR will be part of work to close Bug 1928581 https://bugzilla.redhat.com/show_bug.cgi?id=1928581

@sinnykumari sinnykumari added the 4.9 label Jun 8, 2021
@sinnykumari
Copy link
Contributor

/lgtm
Added 4.9 label, we can merge it once master opens for 4.9 until then putting hold.
/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 8, 2021
@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jun 8, 2021
@QiWang19
Copy link
Member Author

/retest

@@ -0,0 +1 @@
The Dockerfile.proxy builds the openshift-proxy-pull-test image. If the http proxy is set by controller config, [MCO](https://github.com/openshift/machine-config-operator) will validate the proxy by pulling this image through the proxy. The proxy is valid, if the image can be successfully pulled.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The Dockerfile.proxy builds the openshift-proxy-pull-test image. If the http proxy is set by controller config, [MCO](https://github.com/openshift/machine-config-operator) will validate the proxy by pulling this image through the proxy. The proxy is valid, if the image can be successfully pulled.
The Dockerfile.proxy builds the openshift-proxy-pull-test image. If the http proxy is set by controller config, [MCO](https://github.com/openshift/machine-config-operator) will validate the proxy by pulling this image through the proxy. The proxy is valid if the image can be successfully pulled.

@kikisdeliveryservice kikisdeliveryservice removed the lgtm Indicates that a PR is ready to be merged. label Jun 14, 2021
This image will be added into the ocp-build-data(https://github.com/openshift/ocp-build-data)
repository. So product MCO(https://github.com/openshift/machine-config-operator) can
pull the image through a proxy that the customer configured to validate the proxy.

Signed-off-by: Qi Wang <qiwan@redhat.com>
@sinnykumari
Copy link
Contributor

Since master is open for 4.9
/hold cancel

lgtm.
will let Kirsten do final review.

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 18, 2021
@QiWang19
Copy link
Member Author

@kikisdeliveryservice PTAL. I cleaned the review. Could you tag lgtm?

@kikisdeliveryservice
Copy link
Contributor

I'd like @rphillips to give the final once over and to verify that the doc is what he had in mind

/assign @rphillips

@QiWang19
Copy link
Member Author

/retest

@rphillips
Copy link
Contributor

yep. this works for me.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 18, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 18, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kikisdeliveryservice, QiWang19, rphillips, sinnykumari

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:
  • OWNERS [kikisdeliveryservice,sinnykumari]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

5 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 19, 2021

@QiWang19: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws-disruptive 12ab4a6 link /test e2e-aws-disruptive
ci/prow/e2e-metal-ipi 12ab4a6 link /test e2e-metal-ipi

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4.9 approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants