-
Notifications
You must be signed in to change notification settings - Fork 111
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 build of dogfooding images in multi-arch form #629
Conversation
31636f8
to
2e94acd
Compare
cc @afrittoli |
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.
/cc @afrittoli
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.
Thanks for this!
I have a few comments, but they're not really blocking, more like my personal opinions - it would be nice to change the image not to use the mario
tag though, since that is only for testing and it may be overwritten.
tekton/resources/images/overlays/multi-arch/image-build-trigger-template.yaml
Outdated
Show resolved
Hide resolved
tekton/resources/images/overlays/multi-arch/image-build-trigger-template.yaml
Outdated
Show resolved
Hide resolved
@@ -0,0 +1,9 @@ | |||
nameReference: | |||
- kind: TriggerBinding |
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.
NIT: There's no need to use kustomize on bindings, you can specify multiple bindings in a trigger, so for me the way to go would be to have the common base binding and another platform binding which is only used on the multi-arch trigger.
8007a07
to
cf14dc6
Compare
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.
Thanks for all the updates!
One last thing and then it's ready to go.
Extend current cronjobs/triggers setup to build dogfooding images in multi-arch form when it's necessary: - use separate TriggerTemplates and TriggerBindings for single-arch and multi-arch cases - extend eventlistener to filter requests for single-arch and multi-arch builds - add PLATFORMS parameter to cronjobs to be able to specify for which platforms multi-arch image should be - extend several image cronjobs to use multi-arch build (`tkn`, `alpine-git-nonroot`, `skopeo`) Signed-off-by: Yulia Gaponenko <[email protected]>
cf14dc6
to
0657180
Compare
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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afrittoli, vdemeester 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 |
Changes
Extend current cronjobs/triggers setup to build dogfooding images in multi-arch form when it's necessary:
tkn
,alpine-git-nonroot
,skopeo
)buildx
in main container anddind
sidecar are usedNot every image can be built with this approach, so I suggest to use it only for images, which are required for the tests.
The build cronjobs were updated to those exact images.
/kind misc
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide
for more details.