You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VEP48: Support architecture specific image import for registry datasource (#3753)
* importer: introduce registry datasource architecture option
This commit introduces preliminary support for a new optional field under the
DV registry source.
The field, platform, has an additional subfield: architecture which
when specified serves as an image index filter to extract a
disk.img only from layers which match it.
If there's a mismatch between requested architecture and
available architectures in the image index the import will fail.
If the requested image is a manifest and not an index the architecture
of the manifest will be compared to the requested architecture and if
they mismatch the import will fail.
API naming has been chosen to mimic the OCI image index spec[1].
[1] https://github.com/opencontainers/image-spec/blob/main/image-index.md#oci-image-index-specification
Signed-off-by: Adi Aloni <[email protected]>
* importer: pullMethod node architecture support
This commit adds support for specifying architecture for the registry
data source with pullMethod node. When configured, the importer Pod will
gain another NodeSelector for nodes that have the matching architecture
label.
In the event that the importer Pod is unschedulable due to the
pullMethod node's node selector, the condition will be propagated to the
DV's running condition until it becomes schedulable.
Signed-off-by: Adi Aloni <[email protected]>
* docs, image-from-registry: add multi-platform support
Adds a section in the docs about using the platform field for
multi-platform image pull.
Signed-off-by: Adi Aloni <[email protected]>
---------
Signed-off-by: Adi Aloni <[email protected]>
Copy file name to clipboardExpand all lines: doc/image-from-registry.md
+28Lines changed: 28 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -191,3 +191,31 @@ spec:
191
191
```
192
192
193
193
More information on image streams is available [here](https://docs.openshift.com/container-platform/4.8/openshift_images/image-streams-manage.html) and [here](https://www.tutorialworks.com/openshift-imagestreams).
194
+
195
+
# Import registry image by platform specification
196
+
197
+
When importing an image from a [OCI Image Index](https://specs.opencontainers.org/image-spec/image-index/), you can optionally specify a `platform` field to influence which image variant is selected from the multi-platform manifest.
198
+
Currently the `platform` field supports the following subfields for filtering:
199
+
- `architecture`- Specifies the image target CPU architecture (e.g., `amd64`, `arm64`, `s390x`)
200
+
201
+
Subfields defined by the OCI Image Index `platform` specification but not listed above will default to the values defined in the OCI specification.
> When `platform.architecture` is used together with `pullMethod: node`, a node selector will be added to the resulting importer Pod to ensure it schedules onto a node matching the specified architecture.
0 commit comments