-
Notifications
You must be signed in to change notification settings - Fork 71
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
Replace Bazel image creation with Docker #323
Conversation
e70c352
to
88680c8
Compare
/assign @listx |
4fa5685
to
86c5599
Compare
/hold I'd like to reserve this hold. |
eb1571c
to
ad9f05e
Compare
/lgtm Thanks! @tylerferrara Remove hold when ready. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: listx, tylerferrara 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 |
/test pull-cip-image-cip |
/test pull-cip-image-cip |
/hold cancel |
1 similar comment
/hold cancel |
/lgtm |
Created test-push-cip.sh script
Created test-push-cip.sh script
Created test-push-cip.sh script
Created test-push-cip.sh script
What type of PR is this?
/kind cleanup
/kind deprecation
What this PR does / why we need it:
This change aims to remove the reliance on Bazel for image creation. This leed to the modification of the following make targets:
The two deprecated targets are not needed when migrating to docker. The
push-cip.sh
automates building, tagging, and pushing both CIP and Auditor images. This script ports the functionality of the existingpush-cip-auditor-test.sh
script, deprecating it in the process.Usage:
push-cip.sh [--audit | -a]
Partially satisfies #300
Part of the effort to reduce build maintenance.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
The Dockerfile now uses a multi-stage build process. When building, you must provide which build
variant
as a--build-arg
. Below is an example of building the cip variant.This way, we can rely on one Dockerfile to build two different container variants. The auditor variant only uses golang as a base, where the cip variant uses golang and gcloud base images.
Does this PR introduce a user-facing change?
cc: @listx @amwat @justaugustus @kubernetes-sigs/release-engineering