Skip to content

Removed multiArch object to place platforms directly inside output#305

Merged
openshift-merge-bot[bot] merged 1 commit intoshipwright-io:mainfrom
SaschaSchwarze0:sascha-platforms
Apr 21, 2026
Merged

Removed multiArch object to place platforms directly inside output#305
openshift-merge-bot[bot] merged 1 commit intoshipwright-io:mainfrom
SaschaSchwarze0:sascha-platforms

Conversation

@SaschaSchwarze0
Copy link
Copy Markdown
Member

Changes

As discussed in Monday's community meeting, I am hereby proposing to remove the multiArch property in output in favor of putting platforms directly there. For this, I am seeing two reasons:

  1. I do not foresee other properties that would be also in multiArch
  2. multiArch implies multiple architecture. However, the concept can also be used to specify a platforms array with only one item with the goal to build exactly that platform within a Kubernetes cluster that has worker nodes with multiple platforms. This is more intuitive than asking such users to use the nodeSelector.

Related Issue

Fixes #

Type of PR

/kind feature

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Kind label has been set
  • Release notes block has been filled in, or marked NONE

Release Notes

NONE

Signed-off-by: Sascha Schwarze <schwarzs@de.ibm.com>
@openshift-ci openshift-ci Bot added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 17, 2026
@pull-request-size pull-request-size Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Apr 17, 2026
@openshift-ci openshift-ci Bot requested review from adambkaplan and qu1queee April 17, 2026 18:22
@ILpinto
Copy link
Copy Markdown

ILpinto commented Apr 21, 2026

lgtm

Copy link
Copy Markdown
Member

@adambkaplan adambkaplan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

/lgtm

Matches our discussion last week.

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 21, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 21, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adambkaplan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 21, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit c614801 into shipwright-io:main Apr 21, 2026
3 checks passed
@github-project-automation github-project-automation Bot moved this to Done in Issues Apr 21, 2026
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. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants