-
Notifications
You must be signed in to change notification settings - Fork 580
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 platforms annotation to kaniko task #815
Conversation
Annotation about linux/amd64,linux/s390x,linux/ppc64le platforms was added to the latest versions of the kaniko task, as well as information which custom images to use for linux/s390x and linux/ppc64le platforms. JQ_IMAGE parameter is introduced with default value from the existing tas to be able to use custom image for non-Intel architecture. Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbwsg 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 |
## Platforms | ||
|
||
The Task can be run on `linux/amd64`, `linux/s390x` and `linux/ppc64le` platforms. | ||
|
||
For `linux/s390x` platform specify `BUILDER_IMAGE` parameter with `gcr.io/kaniko-project/executor:s390x-9ed158c1f63a059cde4fd5f8b95af51d452d9aa7` | ||
value and `JQ_IMAGE` parameter with `ibmcom/jq-s390x:latest` value in TaskRun or PipelineRun. | ||
|
||
For `linux/ppc64le` platform specify `JQ_IMAGE` parameter with `ibmcom/jq-ppc64le:latest` value in TaskRun or PipelineRun. |
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.
@barthy1 this information would not be available to user who would be installing the task via tkn hub cli
. Is there a way we can get an image which is a multi-arch build?
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.
For kaniko
image - at this moment there is no multi-arch image for all 3 platforms. I am working on it, but the problem is complex and will take some time to resolve.
For jq
image we can use multi-arch one - apteno/alpine-jq
, the default stedolan/jq
has only linux/amd64
support and community is not interested to build multi-arch version.
In general I agree that search via tkn hub
won't show platform specific information, however at least user can find it at hub UI, tkn hub
task details and catalog task description. At this moment I don't see any way to show something like that in standard cli search, except probably adding *
after platforms specification and suggesting check the task documentation before usage :(
Do you have any ideas?
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.
Thinking about it more, also remembered some ideas suggested in this area:
- Multi architecture support for catalog resources #661 (comment) to have separate tasks for separate operating systems (same probably can be implemented for different archs)
- tool to combine all necessary images for different platforms into one manifests, something like https://github.com/imjasonh/combine
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.
@vinamra28 would it be ok for you to resolve this issue step be step?
I mean first step would be just document the differences between platforms in documentation, next step to either somehow generate multi-arch image or define task differently.
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.
yeah will be good for first iteration 👍
/lgtm |
/test .* |
/test pull-catalog-catlin-lint |
1 similar comment
/test pull-catalog-catlin-lint |
🤔 |
/test .* |
Catlin Output
Catlin script lint Output
|
/lgtm |
Changes
Annotation about
linux/amd64
,linux/s390x
, andlinux/ppc64le
platforms was added to the latest versions of the kaniko task, as well as information which custom images to use forlinux/s390x
andlinux/ppc64le
platforms.JQ_IMAGE
parameter is introduced with default value from the existing task to be able to use custom image for non-Intel architecture.The changes were tested for
linux/amd64
,linux/s390x
, andlinux/ppc64le
platforms.Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
File path follows
<kind>/<name>/<version>/name.yaml
Has
README.md
at<kind>/<name>/<version>/README.md
Has mandatory
metadata.labels
-app.kubernetes.io/version
the same as the<version>
of the resourceHas mandatory
metadata.annotations
tekton.dev/pipelines.minVersion
mandatory
spec.description
follows the conventionSee the contribution guide
for more details.