-
Notifications
You must be signed in to change notification settings - Fork 36
[WIP] Changing build and sign to use Buildah instead of Kaniko container #1177
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for kubernetes-sigs-kmm ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Hi @TomerNewman. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
/ok-to-test |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1177 +/- ##
==========================================
- Coverage 79.09% 73.39% -5.70%
==========================================
Files 51 66 +15
Lines 5109 5894 +785
==========================================
+ Hits 4041 4326 +285
- Misses 882 1400 +518
+ Partials 186 168 -18 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
b9ad744
to
ab20c33
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: TomerNewman, yevgeny-shnaidman 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 |
6febb63
to
6a384a0
Compare
fieldPath: metadata.namespace | ||
- name: RELATED_IMAGE_BUILD | ||
value: gcr.io/kaniko-project/executor:latest | ||
value: quay.io/buildah/stable:latest |
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.
Is this the official image that is being used by the u/s Shipwright project?
(I don't remember if when we tested it it was with the u/s version of Shipwright)
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.
they use in their samples quay.io/containers/buildah:v1.40.1
and bump it each time.
shipwright-io/build@10936ee
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.
in their official docs (buildah)
container images will be available at https://quay.io/repository/buildah/stable and https://quay.io/repository/containers/buildah.
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.
Ack. Then let's use the official one as you did. Is there a way to use a specific version instead of latest
? I think we should use v1.41.3
instead of latest
- we don't want things to start breaking under our legs.
What will all the rest of the kaniko refrences?
|
template.ParseFS(templateFS, "templates/Dockerfile.gotmpl"), | ||
) | ||
|
||
func formatBuildArgs(buildArgs []kmmv1beta1.BuildArg) string { |
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.
Should we put this method in the BuildArgOverrider
interface?
const ( | ||
Build BuildOperation = iota | ||
Sign | ||
) |
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.
Can we use the API's BuildOrSignAction
instead of defining a new "type"?
pushDescription = "signed image" | ||
} | ||
|
||
script := fmt.Sprintf(` |
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.
Any reason we are not using go templates? Like we did until now for signing?
I will look about the rest but regarding the CRD I thought that if we decide to change it, we can do it in a different PR. |
Because Kaniko is archived and thus not supported, it would be wise to change the build and sign feature to use buildah container instead of kaniko.
Because Kaniko is archived and thus not supported, it would be wise to change the build and sign feature to use Buildah container instead of Kaniko.
That way we can also match the build and sign d/s to behave the same.
/cc @ybettan @yevgeny-shnaidman