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

Use multi-stage build for registry image. #439

Merged

Conversation

benluddy
Copy link
Contributor

The upstream-registry-builder image is bigger than it needs to be, and
about half of its size seems to be coming from unused build
artifacts. Putting all of that in a separate builder stage cuts the
size of the final image by about half.

Verified

This commit was signed with the committer’s verified signature.
benluddy Ben Luddy
The upstream-registry-builder image is bigger than it needs to be, and
about half of its size seems to be coming from unused build
artifacts. Putting all of that in a separate builder stage cuts the
size of the final image by about half.
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 10, 2020
@benluddy
Copy link
Contributor Author

/retest

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Co-authored-by: Joe Lanford <[email protected]>
@openshift-ci-robot
Copy link

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

Test name Commit Details Rerun command
ci/prow/e2e-aws 8619546 link /test e2e-aws

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.

@benluddy benluddy linked an issue Sep 11, 2020 that may be closed by this pull request
@kevinrizza
Copy link
Member

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 15, 2020
@kevinrizza kevinrizza merged commit 8025636 into operator-framework:master Sep 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.

upstream-registry-builder size seems too large
4 participants